docs: clarify legacy vs config path resolution and bundled fallback - #289
Merged
Merged
Conversation
README, usage guides, cli.md, vision, introduction, and trust model now state that bundled skills stay available without a local skills/ tree, and document legacy vs config tier order.
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.
Description
Docs-only follow-up after #246/#247: state clearly that bundled registry skills stay available when there is no local
skills/tree, and split legacy vs config tier order so README and usage guides no longer implyexternal → project → bundledin all cases.Updated:
README.md,docs/usage/README.md,docs/usage/cli.md,docs/vision.md,docs/introduction.md,docs/security/skill-trust-model.mdType of Change
Checklist (all PRs)
examples/README.md— N/Atest_registry_docs.py— N/ANew or updated skill
N/A — skip.
Related Issues
Refs #246, #247 (config path resolution UX). No code change.