Convex Add

Run /add inside an existing Convex project and it first checks a served capability catalog for a current, canonical procedure matching your request, such as billing, crons, auth, agents, or search. If it finds one, it follows that doc, so the instructions can update without a plugin re-release. If nothing matches or the catalog is unreachable, it falls back to the older path: /add hosting wires up @convex-dev/static-hosting, and anything else searches for and installs the best-matching @convex-dev component. The fallback is the part I'd trust most, since a catalog miss never hard-fails. The catch is that the catalog lookup needs network access, so sandboxed setups may need to be told to allow it.

skills.sh installs: 41.1K
GitHub stars: 69
last updated: Oct 26, 2026

View on GitHub

Install

$ npx -y skills add convex/agent-skills --skill convex-add --agent claude-code

Installs into .claude/skills of the current project.

Files

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/.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

Identify the capability the user wants (text after /add or $add).
Fetch https://basic-anteater-667.convex.site/capabilities.json (4s timeout). Match the request against title/summary/trigger.
If a match is found: fetch /capability/.md and follow its Procedure+Rules sections.
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.
Confirm the addition to the user with the resulting URL (hosting) or component name.