docs: use short-form skill commands in README examples - #1
Merged
Conversation
Short-form invocation (/council, /ship) is the real daily UX — verified empirically that bare names resolve to plugin skills when unambiguous. The fully-qualified forms stay documented as the disambiguation fallback.
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.
Summary
The README documented plugin skills by their fully-qualified names (
/council:council), which look redundant and aren't what users actually type. This PR switches all command examples to the short forms (/council,/ship,/coderabbit-triage) and adds one line explaining when the qualified form is needed.Context
Claude Code namespaces plugin skills as
plugin:skill, and every bro-code plugin ships a single skill named after itself, producing doubled display names. Testing against a local marketplace install confirmed that bare short-form commands resolve to the plugin skill whenever no other skill claims the name — including with no local skills-dir shadow present. The qualified form remains valid everywhere and handles collisions, so it stays documented as the fallback.Test plan
claude plugin validate --stricton the marketplace manifest and all four pluginsgrepfor machine-specific facts inplugins/) — cleanmarkdownlint-cli2 "**/*.md"— 0 issues/councilresolves to the installed plugin skill with the local skill absent; unknown commands error as control