docs(agent-platform-skill-registry): add verify-revision-state recipe#196
Open
gonzoblasco wants to merge 1 commit into
Open
docs(agent-platform-skill-registry): add verify-revision-state recipe#196gonzoblasco wants to merge 1 commit into
gonzoblasco wants to merge 1 commit into
Conversation
|
Thanks for your pull request! It looks like this may be your first contribution to a Google open source project. Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA). View this failed invocation of the CLA check for more information. For the most up to date status, view the checks section at the bottom of the pull request. |
Author
|
Re-triggering CLA check |
Adds a new reference document that provides an end-to-end recipe for verifying the relationship between registry default revisions and runtime-loaded revisions in the Skill Registry. The recipe explicitly documents that registry default state is not runtime consumption evidence, addressing the ambiguity reported in issue google#183. Closes google#183
gonzoblasco
force-pushed
the
fix/issue-183-verify-revision-state
branch
from
July 23, 2026 21:08
1569e79 to
34e6fb5
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Closes #183
Problem
The Skill Registry docs correctly distinguish a mutable Skill from immutable Skill revision resources, but there is no end-to-end verification recipe that makes explicit that registry default state is not runtime consumption evidence. A long-lived or offline agent may still have an older revision cached even after the registry default changes.
Solution
Adds a new reference document
references/verify-revision-state.mdwith:runtime_loaded_revision: "unknown"fieldThe SKILL.md is updated to link the new reference in the Operations section.
Verification
skill_registry_ops.pycommandsunknownwhen the consuming agent does not supply runtime evidence