PluginBench
Skill
Review
Audit score 70

convex-add

get-convex/agent-skills

Add backend capabilities (billing, auth, search, crons) to your Convex app with always-current procedures.

What is convex-add?

Extends an existing Convex app with new backend features by consulting a live capability catalog. Use this when you need to add hosting, authentication, search, billing, crons, agents, or other Convex services to your project.

  • Fetches the served Convex capability catalog for current, always-up-to-date procedures
  • Matches user requests against available capabilities (billing, crons, auth, agent, search, hosting)
  • Falls back to component search and installation if catalog is unavailable or no match found
  • Automatically wires matched components per their documented procedures
  • Confirms capability addition with resulting URLs or component names

How to install convex-add

npx skills add https://github.com/get-convex/agent-skills --skill convex-add
Prerequisites
  • An existing Convex app (initialized with `npx convex dev`)
  • Network access to fetch the capability catalog (convex.site)
  • Optional: auto-approval or sandbox network permissions for component installation
Claude Code
Cursor
Windsurf
Cline

How to use convex-add

  1. 1.Run `/add <capability-name>` or ask to add a feature (e.g., 'add hosting', 'add auth')
  2. 2.The skill fetches the live capability catalog and matches your request
  3. 3.If a match is found, it follows the capability's documented procedure
  4. 4.If no match or catalog is unreachable, it falls back to component search and installs the best match
  5. 5.Confirm the addition—you'll see the resulting URL (for hosting) or component name

Use cases

Good for
  • Adding static hosting to an existing Convex backend
  • Enabling authentication (auth) on a live Convex app
  • Installing search functionality without manual component lookup
  • Setting up billing or cron job capabilities on demand
  • Discovering and installing the latest @convex-dev components by capability name
Who it's for
  • Convex app developers extending existing projects
  • Backend engineers adding new features to production apps
  • Teams managing multiple Convex capabilities across services

convex-add FAQ

What happens if the capability catalog is unreachable?

The skill falls back to the legacy /add-component search script, which searches @convex-dev components and installs the best match for your request.

Can I add any Convex capability with this skill?

Yes—the skill supports billing, crons, auth, agents, search, hosting, and any other capability listed in the served catalog. If it's not in the catalog, the fallback component search will try to find a matching @convex-dev component.

Do I need to manually wire components after installation?

No—the skill automatically wires components per their documented procedures. You'll see confirmation with the resulting URL or component name.

What if my sandbox blocks network access?

Re-run the command with network access enabled or auto-approve the request so the skill can fetch the catalog and install components.

How often is the capability catalog updated?

The catalog is served live, so procedures are always current—no plugin re-release needed when Convex adds new capabilities.

Full instructions (SKILL.md)

Source of truth, from get-convex/agent-skills.


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.