docs: clarify inline metadata-only skills#432
Closed
ketpatil77 wants to merge 1 commit into
Closed
Conversation
|
Thanks for the contribution! We're closing this PR and moving the conversation to the issue: #433 We've moved to a model where bugs and feature proposals are discussed in issues/discussions before code review, so the community can help prioritize and shape the work. Your branch is linked from the new thread so the implementation isn't lost — please join us there to continue the conversation. — astrobot 🤖 |
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
2 participants
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.
Description\nClarify that inline skill metadata is catalog-only and does not package instructions or supporting files.\n\n## Changes Made\n- Added a plain-language note in the skills guide\n- Expanded the API reference description for \Skill\n\n## Testing\n- Docs-only change; no runtime behavior changed\n\n## Impact\nReaders now get an explicit explanation of when to use inline metadata versus imported or workspace-discovered skills.\n\nFixes #430