convex-add

작성자: get-convex

현재 Convex 앱에 기능을 추가합니다 — 항상 최신 절차(결제, 크론, 인증, 에이전트, 검색 등)를 위해 제공되는 Convex 기능 카탈로그를 참조합니다. 내장 호스팅 또는 @convex-dev 구성 요소 검색으로 대체합니다. 사용자가 /add를 실행하거나 기존 Convex 앱에 호스팅/게시 또는 백엔드 기능 추가를 요청할 때 트리거됩니다.

npx skills add https://github.com/get-convex/agent-skills --skill convex-add

ZIP 다운로드 GitHub

이 스킬 사용해 보기스폰서

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.