mcpField
C
convex-add

convex-add

github.com/convexDevelopment6937.0k installsUpdated 1d ago
Repository

About convex-add

convex-add is a skill for adding named capabilities to an existing Convex app. It checks a live catalog first, then falls back to component search and installation when no catalog entry is available.

Key features

  1. 01Checks live capability catalog
  2. 02Follows matched capability procedures
  3. 03Falls back to component search
  4. 04Installs and wires selected components
  5. 05Confirms hosting URL or component

Use cases

  1. 01Adding a capability to a Convex app
  2. 02Setting up hosting when catalog lookup misses

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/convex/agent-skills --skill convex-add

After installing, type/convex-addin Claude Code to confirm it loaded.

Details

From the project README

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

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

Comments

Markdown supported