Repository navigation
feat(plugin): add a setup skill, and use the catalog's own category vocabulary - #38
Conversation
…ocabulary A fresh install has no credentials, so the first OpenTrace tool call fails until the user signs in — and the plugin had nothing to say about it. Add a setup skill (/opentrace:setup, also model-invoked when a call fails to authenticate) that reads the /mcp status, routes to browser sign-in or a pasted key, and verifies with a real tool call. It also names the failure that looks like a broken plugin but isn't: valid credentials against an account with nothing indexed. Anthropic's plugin submission docs mention a SETUP.md for this, but the string appears nowhere in the Claude Code binary and no reference page documents it, so this ships as a normal skill, which loads in the version users run today — verified as opentrace:setup via --plugin-dir. Also drop the invented category and tags from the marketplace entry: the community catalog uses `development`, and carries tags on exactly one of its 2,281 entries. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
![opentrace[bot]](https://avatars.githubusercontent.com/u/160156268?s=60&v=4){kind=small}
There was a problem hiding this comment.
✅ Approved
Clean PR. The setup skill is well-structured — the decision table, the explicit verification step, and the "empty list ≠ broken connector" distinction are all the right things to surface to users.
One thing worth confirming before this goes in: the tags array was dropped from marketplace.json alongside the category change. If the catalog uses tags for search or filtering, removing them reduces discoverability. If the new vocabulary makes tags redundant, that's fine — just worth a quick check that it was intentional rather than a side-effect of the edit.
💰 Agent economics50 agent sessions reported in the last 30 days, but none matched this PR's commits. A session matches on the author email it reports and a commit landing within ~2h of it — so check the agent's email matches the commit author, and that the work was committed in the same sitting. Sessions → Full economics → · by CodeHub |
Add guided setup skill and fix catalog category
🆕 New Feature · 🔧 Chore
Adds a
/opentrace:setupskill — a structured troubleshooting guide the model invokes automatically when tools are missing, auth fails, or the user asks how to connect. Also corrects the marketplace catalogcategoryfrom the non-standard"code-intelligence"to the catalog's own"development"vocabulary term, and removes the unsupportedtagsarray.Complexity
🟢 Low ·
5 files changed, 81 insertions(+), 5 deletions(-)One new Markdown file and metadata edits — no executable code changed. The skill is self-contained prose with no runtime dependencies.
Review focus
Pay particular attention to the following areas:
tagsremoval — the six marketplace tags are dropped entirely, not replaced; confirm the catalog schema genuinely doesn't support them, since removing them reduces discoverability if it does.description:front matter controls when the model auto-invokes this skill; verify the listed triggers (auth failure, missing tools, empty workspaces/repos) are complete and won't fire on unrelated prompts.workspaces_listthengraph_list_code_sourcesbefore declaring setup done; confirm the tool names and parameter names (environment_slug,workspace_slug) match what the server currently advertises.