api
starsforks
How to install api?
kostja94/marketing-skills/api
$npx -y skills add kostja94/marketing-skills --skill apiWhen 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 refe
SKILL.md
| 1 | # Pages: API Introduction |
| 2 | |
| 3 | Guides the API introduction page →typically at `/api` →that overviews the API, use cases, and links to documentation. API documentation (endpoint reference, code examples) lives on separate pages. |
| 4 | |
| 5 | **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. |
| 6 | |
| 7 | ## Initial Assessment |
| 8 | |
| 9 | **Check for project context first:** If `.claude/project-context.md` or `.cursor/project-context.md` exists, read it for product and developer use cases. |
| 10 | |
| 11 | Identify: |
| 12 | 1. **API type**: REST, GraphQL, etc. |
| 13 | 2. **Audience**: Developers (integration) vs. decision makers (evaluation) |
| 14 | 3. **Docs location**: Where API documentation lives (e.g. `/docs`, `/api/reference`, external) |
| 15 | |
| 16 | ## Page Role |
| 17 | |
| 18 | - **API page** (`/api`): Introduction, overview, value prop, CTA to docs or signup |
| 19 | - **API documentation**: Lives in docs (docs.*) → API Reference section with endpoint reference, auth, examples |
| 20 | |
| 21 | ## Best Practices |
| 22 | |
| 23 | ### Overview and Structure |
| 24 | |
| 25 | - **What the API does**: Clear value proposition, key capabilities |
| 26 | - **Use cases**: Who uses it, common scenarios |
| 27 | - **Getting started**: Quick path to first call or docs |
| 28 | - **Link to docs**: Prominent CTA to API documentation |
| 29 | |
| 30 | ### Content |
| 31 | |
| 32 | - **Key concepts**: High-level, not endpoint-level detail |
| 33 | - **Auth overview**: How auth works; link to docs for details |
| 34 | - **Pricing/limits**: If relevant for evaluation |
| 35 | - **SDKs and tools**: If available; link to docs |
| 36 | |
| 37 | ### SEO and Discovery |
| 38 | |
| 39 | - **Developer search**: Target "API" + product/category terms |
| 40 | - **Metadata**: Title, description for developer intent |
| 41 | - **Internal links**: From homepage, features, resources |
| 42 | |
| 43 | ## Output Format |
| 44 | |
| 45 | - **Structure** outline (sections) |
| 46 | - **Value proposition** and key messages |
| 47 | - **CTA** to documentation or signup |
| 48 | - **SEO** metadata for developer search |
| 49 | |
| 50 | ## Related Skills |
| 51 | |
| 52 | - **homepage-generator**: Link to API page for developers |
| 53 | - **schema-markup**: WebPage or SoftwareApplication schema |
| 54 | - **title-tag, meta-description, page-metadata**: API page metadata |
People who liked this also viewed
6 picksType
- find-skillsHelps users discover and install agent skills when they ask questions like "how do I do X", "find a skill for X", "is there a skill that can...", or express interest in extending capabilities. This skSkillsJul 2026
- grill-meA relentless interview to sharpen a plan or design.SkillsJul 2026
- vercel-react-best-practicesVercel's official collection of agent skillsSkillsJul 2026
- improve-codebase-architectureScan a codebase for deepening opportunities, present them as a visual HTML report, then grill through whichever one you pick.SkillsJul 2026
- setup-matt-pocock-skillsConfigure this repo for the engineering skills — set up its issue tracker, triage label vocabulary, and domain doc layout. Run once before first use of the other engineering skills.SkillsJul 2026
- triageMove issues and external PRs through a state machine of triage roles — categorise, verify, grill if needed, and write agent-ready briefs.SkillsJul 2026
