/integrations
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
$ npx -y skills add kostja94/marketing-skills --skill integrations --agent claude-codeHow it fires
How this skill gets triggered: by you, by Claude, or both.
- Fires itselfAuto-invocation. Claude auto-loads it when your prompt matches the work.Auto-invocation is when the right skill fires by itself at the right moment, driven by a FLOW.md router and a hook, instead of you invoking it by name. It is the difference between a skill being installed and a skill actually getting used.Read the full definition →
- You can call itInvoke it directly when you want it.
- Slash command
/integrations
Context preview
The summary Claude sees to decide when to auto-load this skill.
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
SKILL.md
integrations.SKILL.mdname: 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
Read more
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
Markdown skill library for AI agents - SEO, content, pages, paid ads, channels, strategies. Add project context + skills; your agent delivers tailored, production-ready output. Works with Cursor, Claude Code, OpenClaw, Lovable, and any AI that reads markdown.
Repo: kostja94/marketing-skills
Other skills on kostja94-marketing-skills.
- /google-search-console
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,"
Open skill - /seo-monitoring
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,"
Open skill - /ai-traffic
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
Open skill - /traffic
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
Open skill - /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
Open skill - /community-forum
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,"
Open skill