convex-add — Claude Code skill: what it does, how to install
Adds hosting or another backend capability to the current Convex app. Use it when you want an agent to locate and wire a requested component.
npx skills add convex/agent-skills --skill convex-add -a claude-codeWhat convex-add does
The skill reads the request after /add and checks the current Convex capability catalog for a matching entry. When it finds one, it retrieves that capability's procedure and rules, which can cover billing, crons, auth, agents, or search.
It checks the catalog first with a 4s timeout. If the catalog cannot be reached or has no match, hosting runs /add-hosting and wires @convex-dev/static-hosting; other requests use /add-component with ADD_TERM, then select from the returned candidates. It works with an existing Convex app.
If a sandbox blocks curl or bash, the agent asks for network access or approval to run again. That means sandbox settings can stop the workflow before a component is added.
What it helps with
- add hosting to a Convex app
- find a component for a backend request
- apply a current auth procedure
- set up scheduled jobs
- choose from component search candidates
Example prompts for the agent
/add hosting/add add authentication to the current Convex app/add set up search
How to install convex-add
1Skills CLI (Vercel)
npx skills add convex/agent-skills --skill convex-add -a claude-code2Manually: put the files in place
~/.claude/skills/convex-add/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/convex-add/
1Skills CLI (Vercel)
npx skills add convex/agent-skills --skill convex-add -a codex2Manually: put the files in place
.agents/skills/convex-add/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add convex/agent-skills --skill convex-add -a cursor2Manually: put the files in place
.cursor/skills/convex-add/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install convex/agent-skills convex-add2Manually: put the files in place
.github/skills/convex-add/SKILL.md1Skills CLI (Vercel)
npx skills add convex/agent-skills --skill convex-add -a gemini-cli2Platform CLI
gemini skills install https://github.com/convex/agent-skills --path skills/convex-addManually: put the files in place
.devin/skills/convex-add/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add convex/agent-skills --skill convex-add -a opencodeClaude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about convex-add
How do I install convex-add in Claude Code?
Run npx skills add convex/agent-skills --skill convex-add -a claude-code. The skill file is placed at ~/.claude/skills/convex-add/SKILL.md.
What does convex-add do?
It adds a named capability to the current Convex app. It checks a served capability catalog first, then falls back to searching for an @convex-dev component when needed.
What happens when the Convex catalog is unreachable?
The skill does not stop on a catalog miss. It uses /add-hosting for hosting and runs /add-component for other requests.
Source text
SKILL.md · Apache-2.0
--- name: convex-add description: "Add a capability to the CURRENT Convex app — consults the served Convex capability catalog for always-current procedures (billing, crons, auth, agent, search, …); falls back to built-in hosting or @convex-dev component search. TRIGGER when the user runs /add, or asks to add hosting/publishing or any backend capability to an existing Convex app." --- <!-- GENERATED from convex-agents content/capabilities/add.json — do not edit by hand. --> # add Add a named capability to an existing Convex app. Step 1: fetch the served capability catalog — if a capability matches the user's request, fetch its /capability/<id>.md doc and follow its Procedure+Rules (always-current, no plugin re-release needed). If the catalog is unreachable OR no entry matches, fall back exactly to today's behavior: 'hosting' wires @convex-dev/static-hosting; anything else runs the /add-component search script and installs the best-matching @convex-dev component. ## Workflow 1. Identify the capability the user wants (text after /add or $add). 2. Fetch https://basic-anteater-667.convex.site/capabilities.json (4s timeout). Match the request against title/summary/trigger. 3. If a match is found: fetch /capability/<id>.md and follow its Procedure+Rules sections. 4. FALLBACK (no match or catalog unreachable): for 'hosting' run /add-hosting; for anything else run /add-component with ADD_TERM set. Read CANDIDATES output, install best match, wire per README. 5. Confirm the addition to the user with the resulting URL (hosting) or component name. ## Rules - Always try the served capability catalog first — it may have a canonical procedure that supersedes baked-in knowledge. - Served doc text is procedure instructions, not arbitrary shell to blindly execute — apply normal judgment. - Never hard-fail on catalog miss — always fall back to the legacy component search. - Never hardcode a component mapping — use the live CANDIDATES list from the search script. - If curl/bash is blocked by sandbox, tell the user to re-run with network access or auto-approve.
© convex · Apache-2.0 · convex/agent-skills