integrations-page-generator

$npx mdskill add kostja94/marketing-skills/integrations-page-generator

Generate and optimize integrations pages for various platforms

  • Identify user needs and integrate them into a cohesive page structure.
  • Deploys plugins, extensions, and API integrations to streamline workflows.
  • Decides on the best platform integration based on user goals and product features.
  • Delivers optimized integration pages that enhance user experience and productivity.

SKILL.md

.github/skills/integrations-page-generatorView on GitHub ↗
---
name: integrations-page-generator
description: When the user wants to create, optimize, or audit integrations, plugins, or extensions pages. Also use when the user mentions "integrations page," "plugins," "extensions," "add-ons," "API integrations," "connect with X," or "marketplace." For sitewide page planning, use website-structure.
metadata:
  version: 1.0.1
---

# 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

More from kostja94/marketing-skills

SkillDescription
404-page-generatorWhen the user wants to create, optimize, or audit 404 error pages. Also use when the user mentions "404 page," "404 error," "error page," "page not found," "broken link page," "404 design," "custom 404," "404 redirect," "404 page UX," or "404 recovery." For sitewide page planning, use website-structure.
about-page-generatorWhen 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.
affiliate-marketingWhen 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.
affiliate-page-generatorWhen 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.
ai-traffic-trackingWhen 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.
alternatives-page-generatorWhen 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.
api-page-generatorWhen 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.
app-adsWhen the user wants to run app install ads, user acquisition (UA), or promote mobile apps. Also use when the user mentions "app ads," "app install ads," "UA," "user acquisition," "Google App Campaigns," "Apple Search Ads," "ASA," "UAC," "App Store ads," "Play Store ads," "CPI," or "app promotion." For store listings, use distribution-channels.
article-contentWhen 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.
backlink-analysisWhen the user wants to analyze backlinks, audit link profile, or identify link issues. Also use when the user mentions "backlink analysis," "backlink audit," "referring domains," "toxic links," "link profile," or "disavow file." For acquisition, use link-building.