refactor(skills): rename setup-plugin to verify-setup, drop install branch#49
Open
refactor(skills): rename setup-plugin to verify-setup, drop install branch#49
Conversation
…ranch The skill ships *inside* the plugin, so its install instructions are unreachable in practice — if an agent can read the skill, the plugin is already installed. Refocus the skill on what it can actually do: verify connectivity, diagnose MCP / auth failures, check local deps. - Rename `skills/setup-plugin/` → `skills/verify-setup/` and rewrite SKILL.md around verification + diagnosis. Install instructions point at https://subtext.fullstory.com/install/ (already linked from README). - Drop platform-specific install slash commands; diagnostics now describe the failure mode rather than prescribing platform-specific UI. - Drop the misleading `platform: claude-code` frontmatter — the skill is cross-platform now. - Update references in onboard, using-subtext, skills/README.md, authoring.md. - Bump all platform manifests 0.2.x → 0.2.2. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
nrodd
reviewed
May 4, 2026
|
|
||
| # Verify Setup | ||
|
|
||
| Confirm Subtext is wired up correctly and diagnose failures. This skill assumes the plugin/extension is already installed — you wouldn't be reading it otherwise. For first-time install, point users at https://subtext.fullstory.com/install/. |
Collaborator
There was a problem hiding this comment.
Suggested change
| Confirm Subtext is wired up correctly and diagnose failures. This skill assumes the plugin/extension is already installed — you wouldn't be reading it otherwise. For first-time install, point users at https://subtext.fullstory.com/install/. | |
| Confirm Subtext is wired up correctly and diagnose failures. This skill assumes the plugin/extension is already installed — you wouldn't be reading it otherwise. | |
| `` |
Collaborator
There was a problem hiding this comment.
Not sure how the last part would actually get triggered since they already have the plugin at this point. Maybe Im missing a flow that you're envisioning here 🤔. Also how will the agent know if its their first time installing?
nrodd
reviewed
May 4, 2026
| - **401 / 403 / "auth required"** → MCP server is reachable but unauthenticated. Tell the user to complete the OAuth flow (typically opens a browser on first tool use), or to configure an API key per their platform's MCP server settings. Detailed install/auth steps live at https://subtext.fullstory.com/install/. | ||
| - **Network error / 5xx / timeout** → MCP server is unreachable. Suggest checking network and retrying. If persistent, escalate to subtext@fullstory.com. | ||
|
|
||
| ## Step 2: Verify local dependencies |
Collaborator
There was a problem hiding this comment.
Do we want to move this into the sightmap skill in a separate PR?
2 tasks
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
The `setup-plugin` skill ships inside the plugin, so its install instructions are unreachable in practice — if an agent can read the skill, the plugin is already installed. The skill conflated three jobs: verify (real), diagnose (real), and install (impossible from this position). This PR refocuses it on what it can actually do.
Coordination with PR #47
PR #47 (gemini-extension) bumps versions to `0.2.3`. Whichever PR merges second will need a rebase + bump to `0.2.4` to stay ahead of main.
Why this matters
Each agent platform has its own install UX. Maintaining N platform branches inside a SKILL.md will drift the moment any one changes. Verification is naturally portable ("call any MCP tool, see if it responds") — that's the part that belongs in a skill. Install instructions belong on the website.
Test plan
🤖 Generated with Claude Code