integrations-page-generator
The integrations-page-generator skill creates and optimizes pages showcasing how a product connects with external platforms like Slack, Zapier, or Figma. Use it when designing integrations, plugins, or extensions pages, or when users request marketplace listings, API connections, or "connect with" features. The skill provides structure for organizing integrations by category, writing per-integration descriptions, and establishing clear calls-to-action for users to install or connect services.
git clone --depth 1 https://github.com/kostja94/marketing-skills /tmp/integrations-page-generator && cp -r /tmp/integrations-page-generator/skills/pages/marketing/integrations ~/.claude/skills/integrations-page-generatorSKILL.md
# Pages: Integrations / Plugins Guides integrations, plugins, and extensions pages. Shows how the product connects with Canva, Slack, Zapier, and other platforms. Common for SaaS, tools, and developer products. **When invoking**: On **first use**, if helpful, open with 1–2 sentences on what this skill covers and why it matters, then provide the main output. On **subsequent use** or when the user asks to skip, go directly to the main output. ## Initial Assessment **Check for project context first:** If `.claude/project-context.md` or `.cursor/project-context.md` exists, read it for product, integrations, and target platforms. Identify: 1. **Type**: Native integrations, plugins, extensions, API, webhooks 2. **Platforms**: Which to feature (Slack, Notion, Figma, etc.) 3. **Format**: Single page vs. per-integration pages 4. **Primary goal**: Install, connect, sign up ## Page Structure | Section | Purpose | |---------|---------| | **Headline** | "Integrate with [Platforms]" or "Connect [Product] to Your Stack" | | **Value** | Why integrations matter; workflow benefits | | **Catalog** | Grid or list: logo, name, short description, "Connect" or "Install" | | **Categories** | By use case (Productivity, Design, Dev) or platform type | | **API** | Link to api-page or docs if developer-focused | | **CTA** | Browse all, request integration, build your own | ## Best Practices ### Organization - **By category**: Productivity, Design, Marketing, Dev tools - **By platform**: Slack, Notion, Figma, Zapier - **Search/filter**: For 20+ integrations - **Featured**: Highlight top 5–10; rest in catalog ### Content - **Per integration**: Logo, 1–2 sentence benefit, "Connect" CTA - **Use cases**: "Use with Slack to get notifications" - **Screenshots**: Show connected workflow when possible ### SEO - **Intent**: Informational + commercial; "X integration," "X plugin" - **Title**: "Integrations | Connect [Product] to [Platforms]" or "[Product] + Slack" - **Internal links**: API, docs, features, pricing ## Output Format - **Headline** and value proposition - **Catalog structure** (categories, layout) - **Per-integration** copy (name, benefit, CTA) - **Internal links** (API, docs) - **SEO** metadata ## Related Skills - **card**: Integration card structure; logo, name, description, CTA; catalog grid - **grid, list**: Catalog layout; grid or list format - **api-page-generator**: API overview; link for developer integrations - **docs-page-generator**: Integration setup guides in docs - **category-page-generator**: Catalog layout for many integrations - **landing-page-generator**: Integration-specific landing pages
When the user wants to create, optimize, or audit About page content. Also use when the user mentions "about page," "about us," "company story," "our team," "about section," "company overview," "brand story," "team page," or "who we are." For sitewide page planning, use website-structure.
When the user wants to plan, implement, or optimize affiliate marketing strategy. Also use when the user mentions "affiliate marketing," "affiliate program strategy," "CPS model," "affiliate recruitment," "commission structure," "affiliate partners," "affiliate network," "affiliate tracking," "affiliate commission," or "partner marketing." For affiliate page, use affiliate-page-generator.
When the user wants to create, optimize, or audit affiliate program page content. Also use when the user mentions "affiliate program," "affiliate page," "partner program," "referral program page," "affiliate landing," "partner landing," "commission page," or "affiliate signup." For affiliate program strategy, use affiliate-marketing.
When the user wants to track AI search traffic in GA4 or GSC. Also use when the user mentions "AI traffic," "ChatGPT referral," "Perplexity traffic," "AI Overviews," "GA4 AI sources," "AI search analytics," "track AI referrals," "AI search traffic," "Claude traffic," or "how to track AI traffic." For AI SEO strategy, use generative-engine-optimization.
When the user wants to create, optimize, or audit alternatives or comparison content (page or blog article). Also use when the user mentions "alternatives page," "alternatives listicle," "X alternatives," "competitor comparison," "vs page," "compare page," "best alternatives to X," "switch from X," "competitor brand traffic," "brand keyword ads," or "intercept competitor search." For competitor research, use competitor-research.
When the user wants to set up, audit, or optimize analytics tracking (GA4, events, conversions). Also use when the user mentions "Google Analytics," "GA4," "event tracking," "conversions," "attribution model," "gtag," "data layer," "GA4 setup," "conversion tracking," "event setup," "User ID tracking," or "CTA attribution." For traffic insights, use traffic-analysis.
When the user wants to create, optimize, or audit the API introduction/overview page. Also use when the user mentions "API page," "API landing page," "/api page," "API overview," "developer landing," "API marketing," or "API for developers." Note: API documentation (endpoint reference) lives in docs; use docs-page-generator.
When the user wants to write, generate, or create article body content—blog post body, long-form content, how-to guide, listicle. Also use when the user mentions "write article," "article content," "blog post content," "article body," "long-form content creation," "generate article," "article draft," "how-to guide content," "listicle content," "information gain," or "content density." For single post page structure, schema, and SEO metadata, use article-page-generator. For blog index/listing page, use blog-page-generator. For short ad, landing, or email copy, use copywriting.