Convex Add

by get-convex2cfe645c87f9No license63 starsListed Oct 8, 2026Updated Oct 8, 2026Repository updated 6 days ago

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.

Instructions onlySoftware Development

AI-generated overview

Adds a named backend capability to an existing Convex app by consulting a served capability catalog, with component-search fallback.

What it does: This skill adds a requested capability to an existing Convex app. It first fetches a served capability catalog, matches the request against titles, summaries and triggers, and follows the matched capability document's procedure and rules. If the catalog is unreachable or nothing matches, it falls back to wiring static hosting or running a component search and installing the best-matching component.
When to use it: Use it when the user runs /add or asks to add hosting, publishing or another backend capability to an existing Convex app. It is intended for incremental additions to an app that already exists.
Requirements: Requires an existing Convex app, network access to fetch the capability catalog, and the fallback hosting or component-search scripts and @convex-dev components. No credentials are specified; the skill ships no scripts of its own.

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

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

Source and attribution

Source:get-convex/agent-skillsinskills/convex-addat commit2cfe645

License: No license

Content belongs to its original authors. SourceWeft indexes it from a public repository.

Report or request removal

Convex Add

add

Workflow

Rules

Source and attribution

More from get-convex/agent-skills

Convex Verify

Convex Test

Convex Suggest

Convex Sentinel

Convex Self Heal

Convex Seed

More in Software Development

Playground

M5 Onboard

Cardputer Buddy

Dpop Adoption

Gemini Live Api

Gemini Api