From solvapay-skills
Router and disambiguation entry point for the SolvaPay skill family. Use when the user asks "add solvapay to my project", "where do I start with solvapay", "what can solvapay do", or any ambiguous request that spans multiple SolvaPay surfaces. Owns the shared documentation-discovery preference and cross-skill guardrails; routes the agent to one of the four sibling SolvaPay skills based on intent.
How this skill is triggered — by the user, by Claude, or both
Slash command
/solvapay-skills:solvapayThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Disambiguate vague SolvaPay intent and route to the surface skill that owns the work. This skill exists to catch top-level prompts ("add solvapay to my app") and to host the shared docs-discovery preference and cross-skill guardrails so the surface skills don't duplicate them.
Disambiguate vague SolvaPay intent and route to the surface skill that owns the work. This skill exists to catch top-level prompts ("add solvapay to my app") and to host the shared docs-discovery preference and cross-skill guardrails so the surface skills don't duplicate them.
SKILL.md to completion.Installed only this router? The
../<sibling>/...links will not resolve. Install all five skills together withnpx skills add solvapay/skills --all -y(recommended) or pull just the one you need with--skill <name>.
All surface skills use this preference order:
If the MCP server is unavailable, suggest it as a friendly optional improvement. Continue without blocking.
SOLVAPAY_SECRET_KEY to client code or public env vars.llms.txt), not hard-coded doc paths.--skill solvapay) breaks ../sibling/... links — use npx skills add solvapay/skills --all -y.sdk-integration, not create-mcp-app.create-mcp-app, not sdk-integration.create-mcp-app.| User intent | Trigger examples | Route to |
|---|---|---|
| Create / scaffold a paid MCP app | "create mcp app", "scaffold mcp", "new mcp server", "greenfield mcp", "openapi to mcp", "wrap rest api as mcp", "generate mcp from swagger", "build mcp app", "npm create solvapay", "from scratch mcp worker", "cloudflare workers mcp from scratch", "paid mcp", "monetize mcp", "paywall mcp", "mcp with payments", "mcp billing", "intent-driven mcp", "data mcp server", "intelligence mcp" | ../create-mcp-app/SKILL.md |
| Add paywall to an existing MCP server | "add solvapay to my mcp", "integrate into existing mcp", "integrate solvapay into existing mcp", "paywall my mcp tools", "monetize my mcp tools" (no scaffold / greenfield intent) | ../create-mcp-app/references/existing-server.md or ../sdk-integration/references/mcp-server.md depending on whether they need the full worker template |
| SDK integration | "integrate sdk", "protect api", "paywall", "usage events", "webhooks", "express", "MCP Server code integration", "nextjs sdk", "npx solvapay init", "cli", "init project", "cancel renewal", "reactivate", "activate plan", "switch plan", "supabase edge functions", "deno", "edge runtime backend", "lovable backend" | ../sdk-integration/SKILL.md |
| MCP server on edge runtime (existing server) | "createSolvaPayMcpFetch", "fetch-first mcp", "@solvapay/mcp/fetch", "mcp on the edge", "wrangler mcp", "supabase edge mcp", "deno mcp server" — when the user already has a server and wants SDK wiring only | ../sdk-integration/references/mcp-server.md |
| New MCP server on edge runtime (greenfield) | "cloudflare workers mcp", "new cloudflare workers mcp", "scaffold cloudflare mcp worker" — when they want a new Workers project from scratch | ../create-mcp-app/SKILL.md |
| MCP checkout app / embedded MCP UI | "mcp checkout app", "mcp app", "CurrentPlanCard", "LaunchCustomerPortalButton", "usePaymentMethod", "createMcpAppAdapter", "embedded checkout in mcp host", "basic-host checkout", "ChatGPT mcp app" | ../sdk-integration/references/mcp-server.md (server) + ../sdk-integration/references/react.md (client) |
| Account management UI | "customer portal button", "current plan card", "update card", "cancel plan", "payment method preview", "render mirrored card", "self-serve billing ui" | ../sdk-integration/references/react.md |
| Web app checkout | "add checkout to website", "hosted checkout", "customer portal", "nextjs checkout" | ../website-checkout/SKILL.md |
| Lovable checkout (preview) | "lovable", "vite checkout", "shadcn checkout", "supabase edge checkout", "solvapay in lovable", "paste this into lovable", "@preview" | ../lovable-checkout/SKILL.md |
../create-mcp-app/SKILL.md per the vocabulary rule.../sdk-integration/, NOT ../create-mcp-app/. Paywalled MCP and paywalled REST/web are different surfaces.../create-mcp-app/, NOT ../sdk-integration/.Use this if needed:
"Do you want to (1) build a paid MCP server (from OpenAPI spec or hand-written tools), (2) integrate the TypeScript SDK into a non-MCP app, or (3) set up hosted checkout for a web app?"
Default if still ambiguous after one question:
../create-mcp-app/SKILL.md.../create-mcp-app/SKILL.md (the umbrella asks input-mode follow-up).../sdk-integration/SKILL.md.If — and only if — the user explicitly says they're testing this skill against the SolvaPay dev backend, append --dev to every published-CLI invocation:
npm create solvapay@latest <name> -- --type mcp --devnpx -y solvapay@latest init --devThe flag writes SOLVAPAY_API_BASE_URL=https://api-dev.solvapay.com into .env and routes browser-auth, wrangler dev, the deploy preflight, and the deployed worker to the dev backend in one pass. Never enable --dev for end users — production secret keys are rejected by api-dev.
Creates, edits, and optimizes skills for Claude Code, including drafting, evaluating with test prompts, iterating on performance, and improving skill descriptions for better triggering accuracy.
npx claudepluginhub solvapay/skills --plugin solvapay-skills