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 analyze Google Search Console data, use the GSC API, or interpret search performance. Also use when the user mentions "GSC," "Search Console," "indexing report," "Core Web Vitals," "Enhancements," "Insights report," "search performance," "search queries," "search performance report," "URL inspection," "impressions," "CTR," "average position," "index coverage," "GSC data analysis," "Search Console API," or "searchanalytics.query." When the user wants to rewrite title tags (not only report on them), use title-tag. For meta description rewrites, use meta-description.
When the user wants to build an SEO data analysis system, monitor indexing/traffic/keywords/backlinks, or set up benchmarks. Also use when the user mentions "SEO data analysis," "SEO monitoring," "article database," "traffic benchmark," "penalty recovery," "SEO work document," "SEO dashboard," "keyword tracking," "ranking monitoring," "indexing report," or "backlink monitoring." For GSC API, use google-search-console.
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 analyze website traffic sources, attribution, or dark traffic. Also use when the user mentions "traffic sources," "dark traffic," "direct traffic," "UTM parameters," "traffic attribution," "channel attribution," "attribution optimization," "channel analysis," "traffic analysis," "traffic diversification," "natural traffic benchmark," or "organic vs paid traffic." For GA4 setup, use analytics-tracking.
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 promote via forums, communities, or invite users to join a community. Also use when the user mentions "forum promotion," "Indie Hacker," "Hacker News," "community growth," "Discord promotion," "vertical community," "brand encyclopedia," "Wikipedia," "Quora," "Reddit community," "community building," "forum marketing," or "community invite." For Reddit copy, use reddit-posts. For strategy, use integrated-marketing.
When the user wants to submit a product or app to directories, curated lists, launch platforms, or app stores—and needs ready-to-paste copy per platform. Reads project-context.md when present. Also use when the user mentions "directory submission," "get listed," "app store listing," "submit to directories," "curated list," "best tools list," "Taaft," "Product Hunt," "directory ads," "newsletter feature," "directory campaign," "tailor description per platform," "Shopify App Store," "Chrome Web Store," "navigation site," or "product directory." For Product Hunt launch day tactics (hunter, first comment, timing), use product-hunt-launch. For full 0→1 channel planning, use cold-start-strategy.
When the user wants to launch on Product Hunt, prepare a PH submission, or plan launch day (hunter, first comment, timing, upvotes). Also use when the user mentions "Product Hunt," "launch on Product Hunt," "PH launch," "Product Hunt submission," "hunter," "Product of the Day," "upvotes," or "Product Hunt first comment." For multi-platform directory listings and paste-ready copy beyond PH, use directory-submission.