Agent Skills
› sediman-agent/OpenSkynet
› integrations-page-generator
integrations-page-generator
GitHub指导创建、优化或审计集成、插件及扩展页面。涵盖SaaS产品的平台连接展示，提供从初始评估、页面结构（标题、目录、CTA）、最佳实践到SEO优化的完整指南，旨在提升用户连接与安装转化。
Trigger Scenarios
用户想要创建或优化集成/插件页面
提及 'integrations page', 'plugins', 'extensions', 'add-ons'
涉及 'API integrations' 或 'connect with X'
讨论 'marketplace' 相关页面规划
Install
npx skills add sediman-agent/OpenSkynet --skill integrations-page-generator -g -y
SKILL.md
Frontmatter
{
"name": "integrations-page-generator",
"metadata": {
"version": "1.0.1"
},
"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."
}
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
Version History
- c9d8953 Current 2026-07-05 20:00
