solvapay-skills

SolvaPay Skills

Agent skills for adding SolvaPay to any project: paid MCP servers, TypeScript SDK integration, hosted checkout, and Lovable paste-in checkout.

Skills

Skill	Purpose
solvapay	Router — disambiguates vague intent and points at the right surface skill
create-mcp-app	Create or scaffold a paid MCP server on Cloudflare Workers (from OpenAPI or hand-written)
sdk-integration	TypeScript SDK paywall, checkout, usage, webhooks for Next.js / React / Express / MCP / Supabase Edge
website-checkout	Hosted checkout and customer portal for web apps
lovable-checkout	Paste-in preview-only checkout for Lovable (Vite + shadcn/ui + Supabase Edge)

What can it do?

• "Scaffold a paid MCP server from this OpenAPI spec" → create-mcp-app
• "Add SolvaPay paywall to my Express API" → sdk-integration
• "Add usage metering to my MCP server" → sdk-integration
• "Add hosted checkout to my Next.js site" → website-checkout
• "Paste SolvaPay checkout into my Lovable app" → lovable-checkout
• "I just want to add SolvaPay" (vague) → solvapay asks one disambiguation question, then routes

Installation

Pick the variant that matches the context.

Context	Command	Notes
Top-of-funnel (README hero, marketing)	npx skills add solvapay/skills	Opens a multi-select prompt across all 5 skills. Best for human discovery.
Quickstart / "install everything" (recommended default)	npx skills add solvapay/skills --all -y	Installs all 5 to every detected agent, no prompts. Safest because the router skill cross-links to its siblings.
Surface-specific (e.g. a docs page for one product)	npx skills add solvapay/skills --skill create-mcp-app -y	Install just one skill. Swap create-mcp-app for sdk-integration, website-checkout, lovable-checkout, or solvapay.
Power user / CI	npx skills add solvapay/skills --all -g -y	Non-interactive global install.

If you install only the router (--skill solvapay), its relative links into sibling skills will not resolve. Pair it with --all -y or install the surface skill you need directly.

Documentation source priority

Every skill in this family uses the same retrieval chain:

1. SolvaPay Docs MCP server: https://docs.solvapay.com/mcp
2. Fallback docs index: https://docs.solvapay.com/llms.txt
3. Direct docs.solvapay.com page fetch

If MCP is unavailable, the skill continues with fallbacks. MCP setup is a recommended optional improvement.

Local development and testing

1. Edit skill files in this repository.
2. Install/update locally with npx skills add . --skill <name> (or --all -y to mount everything).
3. Run 2–3 prompt checks per skill: routing intent, happy-path implementation, failure-path / troubleshooting.
4. Verify outputs follow each skill's guardrails and the shared docs source priority.

To list all discoverable skills before pushing:

npx skills add . --list

To validate every skill against the agentskills.io spec:

npm run validate

This runs npx skills-reference validate against each skill directory. The validator catches drift in SKILL.md frontmatter (name length, description length, missing required fields) and basic structural issues. Note: both skills-reference (npm) and skills-ref (Python) self-describe as "for demonstration purposes only" — treat as a drift-catcher, not a hard production gate.

AGENTS.md symlinks

Each skill directory ships an AGENTS.md -> SKILL.md symlink. This is a compatibility shim for AGENTS.md-aware clients (Claude Code, OpenAI Codex, OpenHands) that look for AGENTS.md at the root of a project or skill. The agentskills.io spec only requires SKILL.md; the symlink is purely additive so the same directory works in both ecosystems.

Skill quality expectations

A skill is considered complete when:

• it has clear when-to-use scope and "Use when" trigger keywords in its frontmatter
• it has guardrails with explicit "Never" / "Always" rules
• it has a step-by-step implementation flow
• it has verification and troubleshooting guidance
• it uses docs-only, topic-based references resilient to docs URL changes

Architecture