Convex Add

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…

1 minute · 267 words · 3 sections

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 (opens in a new tab) (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.

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.

Install this repository

$ npx skills add get-convex/agent-skills

Skills install per repository, not per chapter — the CLI has no documented per-skill form, so we do not print one.

About this skill

Trigger

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.

The verbatim description from this skill’s front matter — the string an agent matches on to decide whether to load it.

Colophon for this issue

Colophon

How this issue was made

Source

github.com/get-convex/agent-skills, branch main, last pushed 4 August 2026.

Licence

Discovery

33 chapters found by walking the repository tree for SKILL.md, not by matching a directory convention. One layout observed: skills/*/SKILL.md.

Issue colours

Resolved from a deterministic hash of the owner name. Two accent tones are generated per issue and each is proven against its own ground before it ships: a single accent that passes AA on both light and dark paper is arithmetically impossible.

Heading repairs

1 repair applied to this chapter so the document has one h1 and no skipped levels:

Shifted “3 headings” from h1 to h2 so the chapter title is the only h1.

Spec compliance

Every chapter satisfies the Agent Skills specification’s frontmatter rules.

Images

Images inside a chapter come from the upstream repository. Where the author gave no alternative text we mark the image decorative rather than inventing a description — a plausible caption we made up is worse than none for the reader who depends on it.

Signal

Install counts come from skills.sh. They measure downloads, not quality, and an unranked repository is not an unread one.

Agent surfaces

The whole issue is available as one markdown document at /get-convex/agent-skills.md, and each chapter at its own .md URL.

Publication

Set by Skills Docs from the source repository. Body text is Literata at the reader’s chosen size and measure; code is Geist Mono. Nothing on this page was written by us except this paragraph.