How do I install the Convex Add skill?

Run npx skillmds@latest add openclaw/convex-add in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Convex Add safe to use?

This skill has not completed SkillMD's automated safety review yet. Independent scanners report: SkillSpector: PASS, Skill Scanner: PASS. Capability flags: makes network calls. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Convex Add?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Convex Add free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Convex Add?

OpenClaw (@openclaw) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Convex Add by openclaw — Agent Skill

Name: Convex Add
Rating: 4.666666666666667 (3 reviews)
Author: OpenClaw

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. TRIGGER when the user runs /add, or asks to add hosting/publishing or any backend capability to an existing Convex app.

OpenClaw Updated Sep 9, 2026 9.1k repo stars

File contents

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

---name: convex-adddescription: 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.---  # 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.

Frequently asked questions