toolify
When you want to integrate an external tool, API, MCP server, or service into a project — the wizard walks you through auth, config, env vars, client wrapper code, example usage, and (optionally) a smoke-test. Scoped to Next.js and Rails projects (the two primary stacks). Interactive Q&A pattern — starts with the tool name, asks structured questions until the integration is fully specified, then scaffolds files. Examples of tools to toolify — Stripe, Kit, Sanity, Notion, Neon, Supabase, Fathom, Rewardful, SavvyCal, Riverside, ScrapeCreators, Anthropic, OpenAI, Gemini, Twilio, Resend, Postmark,
npx skills add coreyhaines31/makerskills --skill toolify --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# /toolify — Wire up an integration or MCP server Interactive wizard for adding an external tool / API / MCP into a project. Ends with working code + env vars set + a verification path. ## Scope - **Primary stacks**: Next.js (App Router + TypeScript) and Rails. Reason: those are the two stacks the user actually ships in; supporting every stack bloats the wizard. - **What toolify handles**: auth pattern (API key, OAuth, JWT, session cookie), env var setup, official SDK vs raw fetch, client wrapper location, example usage, webhook handling (if applicable), MCP `.mcp.json` wiring (if MCP server). - **What toolify does NOT handle**: writing business logic on top of the integration (that's for the human). It scaffolds the *plumbing*, not the *feature*. ## Step 0 — Get the tool name Ask if not provided: *"Which tool are we integrating?"* Detect category from name: | Category | Examples | Extra steps | |---|---|---| | **Payments** | Stripe, LemonSqueezy, Paddle | Webhook signature verification, customer model, event handlers | | **Auth** | NextAuth/Auth.js, Clerk, Supabase Auth, Devise | Session management, protected routes, callbacks | | **Email** | Resend, Postmark, SendGrid, Kit | From
- Scope
- Step 0 — Get the tool name
- Step 1 — Structural interview
- Step 2 — Fetch official setup docs
- Step 3 — Scaffold files
- Step 4 — Auth pattern implementation
- Step 5 — Env var setup
- Step 6 — Smoke test
- Step 7 — Report + follow-ups
- Reference — integration recipes
- Composes with
- Notes on quality
Prefer context7 if available (fresher docs than training data)
Fallback to WebFetch
WebFetch <official-quickstart-url>
vercel env add NEXT_PUBLIC_APP_URL production --value "<url>" --no-sensitive --yes
vercel env add STRIPE_SECRET_KEY production --value "<key>" --sensitive --yes
vercel env add STRIPE_WEBHOOK_SECRET production --value "<secret>" --sensitive --yes
Example for a REST API:
curl -H "Authorization: Bearer $STRIPE_SECRET_KEY" https://api.stripe.com/v1/customers?limit=1
Example for an SDK:
node -e "const s = require('./src/lib/stripe.ts').default; s.customers.list({limit:1}).then(console.log)"What does the toolify skill do?
When you want to integrate an external tool, API, MCP server, or service into a project — the wizard walks you through auth, config, env vars, client wrapper code, example usage, and (optionally) a smoke-test. Scoped to Next.js and Rails projects (the two primary stacks). Interactive Q&A pattern — starts with the tool name, asks structured questions until the integration is fully specified, then scaffolds files. Examples of tools to toolify — Stripe, Kit, Sanity, Notion, Neon, Supabase, Fathom, Rewardful, SavvyCal, Riverside, ScrapeCreators, Anthropic, OpenAI, Gemini, Twilio, Resend, Postmark,
How do I install it?
Run `npx skills add coreyhaines31/makerskills --skill toolify --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From coreyhaines31/makerskills, a repository with 500 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.