kostja94/integrations-page-generator
skills/pages/marketing/integrations/SKILL.md
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.
$ install --global
skillsauthnpx skillsauth add kostja94/marketing-skills integrations-page-generatorInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: Apr 24, 2026, 6:46 PM176.5s1 file scanned
SKILL.md
- 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.
- 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:
- Type: Native integrations, plugins, extensions, API, webhooks
- Platforms: Which to feature (Slack, Notion, Figma, etc.)
- Format: Single page vs. per-integration pages
- 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
Related Skills
kostja94/xml-sitemap
testing
VerifiedTrustedCommunity
When the user wants to create, audit, or optimize sitemap.xml. Also use when the user mentions "sitemap," "sitemap.xml," "sitemap index," "lastmod," "changefreq," "priority," "URL discovery," "URL discovery for search engines," "single source of truth," "URL config," "unify sitemap IndexNow," or "reduce duplicate maintenance." For IndexNow, use indexnow.
588SKILL.mdUpdated Apr 24, 2026
kostja94/robots-txt
development
VerifiedTrustedCommunity
When the user wants to configure, audit, or optimize robots.txt. Also use when the user mentions "robots.txt," "crawler rules," "block crawlers," "AI crawlers," "GPTBot," "allow/disallow," "disallow path," "crawl directives," "user-agent," "block Googlebot," "fix robots.txt," "robots.txt blocking," or "search engine crawling." For indexing, use indexing.
588SKILL.mdUpdated Apr 24, 2026
kostja94/programmatic-seo
testing
VerifiedTrustedCommunity
When the user wants to create SEO pages at scale using templates and data—including AI-assisted, grounded copy for per-URL differentiation (vs rigid mail-merge templates). Also use when the user mentions "programmatic SEO," "programmatic SEO pages," "template pages," "scale content," "location pages," "city pages," "comparison pages at scale," "X vs Y pages," "integration pages," "pages from data," "automated landing pages," or "programmatic landing pages." Uses a playbook matrix aligned to skills under skills/pages. For user-facing template galleries or marketplaces (browse → use), use template-page-generator.
588SKILL.mdUpdated Apr 24, 2026
kostja94/twitter-cards
data-ai
VerifiedTrustedCommunity
When the user wants to add or optimize Twitter Card metadata for X (Twitter) link previews. Also use when the user mentions "Twitter Card," "twitter:card," "twitter:image," "twitter:title," "X preview," or "tweet preview." For Facebook/LinkedIn previews, use open-graph.
571SKILL.mdUpdated Apr 24, 2026