get-convex/agent-skills

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 built-in hosting or @convex-dev component search.

All-time #1016 Trending #526 Hot #5876 First seen Aug 1, 2026
8-week activity · all time api

Installation

$ npx skills add get-convex/agent-skills --skill convex-add

Summary

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

Similar popular skills

Related neighbors and high-traction skills in the same topics — useful to compare before installing.

Also in this package

Other skills from get-convex/agent-skills · top by installs.

npx skills add get-convex/agent-skills

Browse all from get-convex/agent-skills

More details

Agent compatibility

Declared targets from SKILL.md / docs. Unmarked agents are not listed — the skill may still install via the CLI.

Claude Code Not declared
Cursor Not declared
Codex Not declared
GitHub Copilot Not declared
Windsurf Not declared
Gemini CLI Not declared
Cline Not declared
OpenCode Not declared

Repository health

Stars 53
License LICENSE
Default branch main
Open issues 2
Status Active

Package contents

Files included with this skill beyond the listing page.

  • skill md SKILL.md 2,099 B
  • docs SUMMARY.md 368 B

History

  1. First seen on skills.sh
  2. First recorded snapshot · 18,646 installs

SKILL.md

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