Firm up step 6 with confirmed settings.json shape + usage note - #5
Open
jystewart wants to merge 1 commit into
Open
Firm up step 6 with confirmed settings.json shape + usage note#5jystewart wants to merge 1 commit into
jystewart wants to merge 1 commit into
Conversation
Replace the "confirm this yourself, it's evolving" hedge with the actual, tested settings.json shape for enabling the plugin on web/ desktop/org-wide (enabledPlugins is an object keyed by "plugin@marketplace", not an array — easy to get wrong and the settings docs don't make it obvious). Also add a note that there's no /new-prototype slash command to run once installed — it's a skill, triggered by matching the description's trigger phrases, not a command. Someone just hit exactly this confusion after getting the plugin installed successfully. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01QUdzgJV9npgquKJpAZRP8U
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.
Summary
Follow-up from actually testing the
new-prototypeplugin install end toend. Step 6 previously just said "confirm the current steps in your admin
settings, this is evolving" — replaced that with the actual, tested path:
/pluginis terminal-CLI-only; it does not work in Claude Code on theweb or the desktop app.
.claude/settings.json(per-user/project) or managed settings (org-wide,via the admin console or a managed-settings.json file). Documented the
confirmed-working shape —
enabledPluginsis an object keyed by"plugin-name@marketplace-name", not an array, which isn't obvious fromthe settings docs and was the actual cause of a schema validation error
hit while testing this.
/new-prototypeslash command onceinstalled — it's a skill, triggered automatically when a request matches
the trigger phrases in
SKILL.md'sdescription, not a command to type.Someone hit exactly this confusion right after a successful install.
Test plan
enabledPlugins-as-object shape resolves the schemaerror that the array shape produced.
commands/*.mdfiles register a literal/name.🤖 Generated with Claude Code
https://claude.ai/code/session_01QUdzgJV9npgquKJpAZRP8U
Generated by Claude Code