Integrations Page Generator
Generate structure and copy for an integrations or plugins landing page that lists Slack, Zapier, and other connectors for a SaaS or dev tool.
Overview
Integrations-page-generator is an agent skill most often used in Launch (also Validate, Grow) that plans and drafts integrations, plugins, and extensions pages for SEO and conversion.
Install
npx skills add https://github.com/kostja94/marketing-skills --skill integrations-page-generatorWhat is this skill?
- Section blueprint: headline, value prop, integration catalog grid, and primary CTA (install, connect, sign up)
- Supports native integrations, plugins, extensions, API, and webhooks with single-page or per-integration URL strategies
- Reads `.claude/project-context.md` or `.cursor/project-context.md` for product and platform targets
- Pairs with website-structure skill for sitewide page planning when scope exceeds one integrations URL
- 6-section page structure table (headline through catalog)
- metadata version 1.0.1
Adoption & trust: 733 installs on skills.sh; 586 GitHub stars; 3/3 security scanners passed (skills.sh audits).
What problem does it solve?
You have real product connectors but no structured integrations page that explains value, lists partners, and drives connect or sign-up.
Who is it for?
Indie SaaS or API products shipping connector stories for Slack, Notion, Zapier, or a marketplace-style integration catalog.
Skip if: Teams that only need sitewide IA or nav without a dedicated integrations URL—use website-structure instead.
When should I use this skill?
User wants to create, optimize, or audit integrations, plugins, extensions, add-ons, API integrations, connect-with-X, or marketplace pages.
What do I get? / Deliverables
You get a sectioned integrations page outline with catalog layout and CTAs aligned to your platforms—then broaden sitewide planning with website-structure if needed.
- Integrations page section outline
- Catalog grid/list specification
- Headline and value-prop copy direction
Recommended Skills
Journey fit
Spans multiple journey phases - primary shelf plus alternate fits below.
Integrations pages are primarily organic-discovery assets that explain how the product fits into a buyer’s stack, which maps to launch SEO and distribution. SEO subphase covers indexable product pages built to rank for “X integrations” and marketplace-style connector queries.
Where it fits
Draft a prototype landing section that shows three key integrations before you commit to full site build.
Publish an indexable “Connect to your stack” page targeting long-tail integration search terms.
Align partner logos and one-liners for a product Hunt or directory listing that links to your integrations hub.
Expand the integration grid and internal links when you ship new connectors each release.
How it compares
Use this generator for one high-intent integrations landing page, not programmatic-seo for hundreds of templated URLs.
Common Questions / FAQ
Who is integrations-page-generator for?
Solo builders and small teams launching or growing B2B tools, dev products, or SaaS that need a credible integrations or plugins page for search and sales.
When should I use integrations-page-generator?
Use it during Validate when scoping a landing that proves stack fit, at Launch when publishing SEO pages for “integrations” queries, and in Grow when refreshing connector catalogs for content and distribution.
Is integrations-page-generator safe to install?
It is editorial page guidance with optional reads of local project-context files; review the Security Audits panel on this Prism page before enabling the skill in your agent.
Workflow Chain
Then invoke: website structure
SKILL.md
READMESKILL.md - Integrations Page Generator
# 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