30f9b9a729
* feat: v2.0 skill renames and CRO consolidation BREAKING CHANGE: Users must reinstall skills after this update. ## Skill Renames (16) - ab-test-setup → ab-testing - analytics-tracking → analytics - aso-audit → aso - competitor-alternatives → competitors - email-sequence → emails - free-tool-strategy → free-tools - launch-strategy → launch - onboarding-cro → onboarding - paywall-upgrade-cro → paywalls - popup-cro → popups - pricing-strategy → pricing - product-marketing-context → product-marketing - referral-program → referrals - schema-markup → schema - signup-flow-cro → signup - social-content → social ## Consolidations (1) - page-cro + form-cro → cro (form content in references/form.md) ## Why 2.0? - Shorter, cleaner skill names - Consistent naming (no -strategy, -setup, -cro suffixes) - All cross-references updated across 100+ files Total skills: 40 Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com> * fix(v2.0): update evals for renamed skills, fix validate script, clear warnings - Update 32 evals.json files to reference new skill names (page-cro → cro, product-marketing-context → product-marketing, etc.) — these were missed in the initial v2.0 rename pass since only SKILL.md and marketplace.json were updated. - Fix validate-skills.sh: replace GNU-only `head -n -1` with portable awk so frontmatter extraction works on macOS. - Move Copy Editing Checklist (56 lines) to references/checklist.md to bring copy-editing SKILL.md under the 500-line limit (508 → 457). - Add "see X" pointers to marketing-psychology description for skill discovery (cro, pricing, copywriting). - Update skill-request.yml issue template placeholder (page-cro → cro). All 40 skills now pass validation with zero warnings. * fix(v2.0): add evals for 8 missing skills, strip stale frontmatter from cro/form.md Adds 48 new eval cases (6 per skill) for skills that previously had no evals: aso, co-marketing, community-marketing, competitor-profiling, directory-submissions, image, lead-magnets, video. All 40 skills now have eval coverage (251 total cases). Strips leftover frontmatter from skills/cro/references/form.md — it was inherited from the old form-cro SKILL.md before consolidation. Reference files don't need frontmatter. Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com> * fix(v2.0): rename paid-ads → ads One more v2.0 simplification — drops the redundant 'paid-' qualifier. Updates the skill directory, SKILL.md frontmatter, evals.json, README skill table, the v2.0 rename table in VERSIONS.md (now 17 renames), and all cross-references in related skills (ad-creative, aso, competitor-profiling, customer-research, lead-magnets, marketing-ideas) plus the tools/integrations guides. Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com> * fix(v2.0): bump SKILL.md frontmatter version to 2.0.0 for all 40 skills VERSIONS.md was already updated to 2.0.0 but the metadata.version field inside each SKILL.md was still on 1.x. That mismatch would have caused the update-check flow to perpetually report 'update available' since it compares VERSIONS.md against local SKILL.md metadata versions. Caught by codex review (P1). Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com> * fix(v2.0): add legacy product-marketing-context.md filename fallback Before this fix, users upgrading from v1.x who had a `product-marketing-context.md` file would lose automatic context loading — every skill only checked the new `product-marketing.md` filename. Now all 40 skills also accept the legacy filename (in either `.agents/` or `.claude/`), and the README migration command covers both legacy and current filenames. Caught by codex review (P1 + P2). Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com> * fix(v2.0): re-sort README skills table alphabetically, fix ads box width The skills table had a few entries out of alphabetical order from the renames (co-marketing was after cold-email, ads was at the renamed position). Re-sorted alphabetically per sync-skills.js. Also padded the 'ads' cell in the ASCII flow diagram to keep the box width consistent. Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com> * fix(v2.0): document folder cleanup on upgrade, stop sync-skills from re-adding skills array README upgrade guide now includes: - A clear cleanup step for stale v1.x skill folders (renamed + consolidated) so users don't end up with both old and new folders side-by-side after upgrading - The full v1 to v2 rename map for reference - Existing product-marketing-context.md migration steps (preserved) sync-skills.js no longer (re-)introduces a `skills` array on marketplace.json -- Claude Code's plugin schema discovers skills via the `skills/` directory, and the explicit array was failing validation. The script now refreshes the description count and strips the stale array if present. Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com> --------- Co-authored-by: Claude Opus 4.5 <noreply@anthropic.com>
5.6 KiB
5.6 KiB
Zapier
Workflow automation platform connecting 8,000+ apps. The Zapier SDK gives AI agents direct access to any app's actions without building OAuth flows or reverse-engineering APIs.
Capabilities
| Integration | Available | Notes |
|---|---|---|
| API | ✓ | REST API for Zaps, tasks, and webhooks |
| MCP | ✓ | Available via Zapier MCP server |
| CLI | ✓ | @zapier/zapier-sdk-cli for app discovery and type generation |
| SDK | ✓ | @zapier/zapier-sdk — TypeScript SDK for 8,000+ app integrations |
Authentication
Legacy API (Zaps management)
- Type: API Key
- Header:
X-API-Key: {api_key} - Get key: Settings > API in Zapier account
SDK Authentication
Browser-based login (development):
npx zapier-sdk login
Server-side (production):
- Client Credentials — store as environment variables
- Direct token — set
ZAPIER_CREDENTIALSenv var
Browser-based login only works locally. Use Client Credentials for any server-side deployment.
SDK Quick Start
Install
npm install @zapier/zapier-sdk
npm install -D @zapier/zapier-sdk-cli @types/node typescript
npm pkg set type=module
Initialize
import { createZapierSdk } from "@zapier/zapier-sdk";
const zapier = createZapierSdk();
CLI Commands
| Command | Purpose |
|---|---|
npx zapier-sdk login |
Authenticate (dev only) |
npx zapier-sdk list-apps --search "query" |
Search available apps |
npx zapier-sdk list-actions APP_KEY |
List actions for an app |
npx zapier-sdk add [app-key] |
Generate TypeScript types |
SDK Methods
| Method | Purpose |
|---|---|
zapier.listConnections() |
List authenticated app connections |
zapier.findFirstConnection() |
Find a specific connection |
zapier.runAction() |
Execute an action on a connected app |
zapier.apps.slack() |
App proxy pattern for clean syntax |
zapier.fetch() |
Custom authenticated API calls |
Example: Send a Slack Message
import { createZapierSdk } from "@zapier/zapier-sdk";
const zapier = createZapierSdk();
const slack = await zapier.apps.slack();
await slack.sendChannelMessage({
channel: "#marketing",
message: "Campaign launched!"
});
Example: Create a HubSpot Contact
const hubspot = await zapier.apps.hubspot();
await hubspot.createContact({
email: "lead@example.com",
firstName: "Jane",
lastName: "Doe"
});
Pagination
Use .items() for large datasets:
const contacts = await hubspot.listContacts({ maxItems: 100 });
for await (const contact of contacts.items()) {
console.log(contact.email);
}
Governance Note
Direct API calls via zapier.fetch() are not subject to org app/action restriction policies. Use pre-built actions where possible if your org has governance requirements.
Zaps API (Legacy)
List Zaps
GET https://api.zapier.com/v1/zaps
Get Zap details
GET https://api.zapier.com/v1/zaps/{zap_id}
Turn Zap on/off
POST https://api.zapier.com/v1/zaps/{zap_id}/on
POST https://api.zapier.com/v1/zaps/{zap_id}/off
Get task history
GET https://api.zapier.com/v1/zaps/{zap_id}/tasks
Get profile info
GET https://api.zapier.com/v1/profiles/me
Webhooks (Triggers)
Catch Hook (receive data)
Create a "Webhooks by Zapier" trigger to receive data:
POST https://hooks.zapier.com/hooks/catch/{webhook_id}/
{
"event": "user.created",
"user_id": "123",
"email": "user@example.com"
}
Send data to Zapier
Most common: trigger a Zap from your app:
POST https://hooks.zapier.com/hooks/catch/{account_id}/{hook_id}/
{
"name": "John Doe",
"email": "john@example.com",
"plan": "pro"
}
Common Marketing Automations
With SDK (recommended for agents)
// Lead capture to CRM
const hubspot = await zapier.apps.hubspot();
await hubspot.createContact({ email, firstName, lastName });
// New customer notification
const slack = await zapier.apps.slack();
await slack.sendChannelMessage({ channel: "#revenue", message: `New customer: ${email}` });
// Add to email sequence
const customerio = await zapier.apps.customerio();
await customerio.createOrUpdatePerson({ email, plan: "pro" });
With Zaps (no-code)
- Typeform → Zapier → HubSpot (lead capture)
- Stripe → Zapier → Slack (new customer alerts)
- Form submission → Zapier → Customer.io (email sequences)
- New review → Zapier → Slack (social proof)
- New referral → Zapier → Spreadsheet + Slack (referral tracking)
Webhook Payload Structure
When sending to Zapier, structure data as flat JSON:
{
"customer_name": "John Doe",
"customer_email": "john@example.com",
"plan_name": "Pro",
"plan_price": 99,
"signup_date": "2024-01-15"
}
Key Concepts
- Zap - Automated workflow (no-code)
- SDK - Programmatic access to 8,000+ app integrations
- Trigger - Event that starts a Zap
- Action - Task performed by Zap or SDK
- Task - Single action execution
- Connection - Authenticated link to an app (shared between Zaps and SDK)
When to Use
- SDK: When an AI agent needs to interact with any app directly — send messages, create records, sync data
- Zaps: When you need always-on automation without code
- Webhooks: When triggering workflows from your own app
- API: When managing Zaps programmatically
Rate Limits
- API: 100 requests per minute
- SDK: Rate limits per connected app
- Task limits by plan tier
Relevant Skills
- emails
- analytics
- referrals
- revops