Agent Skills
Install and use WaitKit agent skills to add waitlist signup flows to any web project.
WaitKit provides agent skills that let you add waitlist signup flows to any web project — collect emails, track subscriber counts, use the React hook, and set up source tracking.
Installation
npx skills add ubeyidah/waitkit-skillsThis installs the WaitKit skill into your agent's configuration. The install command is the same regardless of which agent you use — any agent that supports skills can run it.
After installation, restart your agent session for the skill to load.
What the skill does
The WaitKit skill enables your agent to help you integrate waitlist functionality into your project. It covers three integration paths:
- SDK — Use the
waitkitnpm package for typedsubscribers.create()andsubscribers.count()calls - React Hook — Use the
useWaitlisthook for a drop-in form component with loading and error states - Raw API — Call the WaitKit REST API directly with
fetchfor non-JS projects or static sites
Configuration
The skill produces code that reads two environment variables at runtime. Set these in your project's .env with the appropriate prefix for your framework:
VITE_WAITKIT_API_KEY(Vite),NEXT_PUBLIC_WAITKIT_API_KEY(Next.js), etc. — Your WaitKit API key (wk_...)VITE_WAITKIT_PROJECT_SLUG(Vite),NEXT_PUBLIC_WAITKIT_PROJECT_SLUG(Next.js), etc. — Your project slug from the WaitKit dashboard
Example prompts
| Prompt | What happens |
|---|---|
| "Add a waitlist signup form to my project" | Generates an email collection form using the SDK or React hook |
| "Show me how many subscribers I have" | Calls subscribers.count() and displays the count |
| "Track where signups come from" | Sets up source tracking with URL params |
| "I need a waitlist for my launch page" | Builds a complete waitlist integration with confirmation email |
Source tracking
Signups can be tracked with four-resolution ordering: per-call override > URL query param (?source= or ?s=) > instance default > fallback "landing-page".
Error handling
| Error | Meaning |
|---|---|
| 401 | Bad API key |
| 404 | Project slug not found |
| 409 | Duplicate email (already subscribed) |
| 403 | Plan limit reached |
| 422 | Validation error (invalid email) |
Important: browser-only
WaitKit's API is browser-only. The SDK and API calls must run client-side — do not use them in Server Components, server routes, or edge functions. The API keys are project-scoped and public-facing by design.
Verification
After installation, confirm the skill is loaded by asking your agent:
What skills do you have available?Troubleshooting
- Skill not showing up — Restart your agent after installing. Make sure you've restarted your terminal session.
- Permission errors — Run
npx skills add ubeyidah/waitkit-skillsfrom your project directory. - Outdated skill — Re-run the install command to get the latest version.
Related
- WaitKit SDK — JavaScript SDK for programmatic access
- REST API — Direct API access
Troubleshooting
Troubleshoot common WaitKit integration issues. Fix API key errors, project slug not found (404), duplicate email conflicts (409), rate limits (429), CORS errors, and Node.js fetch compatibility.
Installation & Configuration
Install the waitkit npm package and configure the JavaScript SDK for your project. Connect to the WaitKit waitlist API with your API key and project slug.
