mcpbeat Sign in

API Page Generator Agent Skill

When 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 reference) lives in docs; use docs-page-generator.

639 tokens
context cost
the whole folder, loaded on every use
1
files
instructions only
0
copies elsewhere
how many repositories repackaged it
836
stars on the repo
on the repository, not the skill itself

Install

one command, takes just this skill from the repository
npx skills add https://github.com/kostja94/marketing-skills --skill api-page-generator

The instruction itself

9 sections, as written by the author

Pages: API Introduction

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.

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 and developer use cases.

Identify:

  • API type: REST, GraphQL, etc.
  • Audience: Developers (integration) vs. decision makers (evaluation)
  • Docs location: Where API documentation lives (e.g. /docs, /api/reference, external)

Page Role

  • API page (/api): Introduction, overview, value prop, CTA to docs or signup
  • API documentation: Lives in docs (docs.*) → API Reference section with endpoint reference, auth, examples

Best Practices

Overview and Structure

  • What the API does: Clear value proposition, key capabilities
  • Use cases: Who uses it, common scenarios
  • Getting started: Quick path to first call or docs
  • Link to docs: Prominent CTA to API documentation

Content

  • Key concepts: High-level, not endpoint-level detail
  • Auth overview: How auth works; link to docs for details
  • Pricing/limits: If relevant for evaluation
  • SDKs and tools: If available; link to docs

SEO and Discovery

  • Developer search: Target "API" + product/category terms
  • Metadata: Title, description for developer intent
  • Internal links: From homepage, features, resources

Output Format

  • Structure outline (sections)
  • Value proposition and key messages
  • CTA to documentation or signup
  • SEO metadata for developer search
  • homepage-generator: Link to API page for developers
  • schema-markup: WebPage or SoftwareApplication schema
  • title-tag, meta-description, page-metadata: API page metadata

Other skills for the same job

different authors, same section of the catalogue
Mobile Developer
by ComeOnOliver
×2

Develop React Native, Flutter, or native mobile apps with modern architecture patterns. Masters cross-platform development, native integrations, offline sync, and app store optimization. Use PROACTIVELY for mobile features, cross-platform code, or app optimization.

4k tokens
Apple Appstore Reviewer
by github
vendor ×1

Serves as a reviewer of the codebase with instructions on looking for Apple App Store optimizations or rejection reasons.

2k tokens
Uncertainty And Units
by K-Dense-AI
×1

Track physical units and propagate measurement uncertainty in scientific calculations using pint and uncertainties. Use for unit conversion and dimensional checking, GUM uncertainty budgets, Type A and Type B evaluation, coverage factors and expanded uncertainty, Monte Carlo propagation, significant-figure and plus-minus reporting, error propagation through curve fits, CODATA constants, auditing Python code for stripped units or broken uncertainty propagation, and order-of-magnitude plausibility checks using dimensionless groups (Reynolds, Peclet, Damkohler, Knudsen, Biot, Womersley), characteristic scales such as diffusion time or Debye length, and observed magnitude ranges. Trigger on "is this number physically reasonable", "sanity check these units", "what regime is this flow in", or a result that looks off by orders of magnitude.

52k tokens scripts
Angular Migration
by lingxling
×1

Master AngularJS to Angular migration, including hybrid apps, component conversion, dependency injection changes, and routing migration.

3k tokens
Libsbml Network Modeling
by BioTender-max
×1

Build, read, validate, modify SBML biological network models via the libSBML Python API. SBML Levels 1–3, reactions/kinetic laws, species, rules, FBC extension for flux balance, conversion. Interoperates with COBRApy, Tellurium/RoadRunner, COPASI. Use when programmatically constructing ODE or constraint-based metabolic/signaling models in SBML.

9k tokens
Binary Re Dynamic Analysis
by ComeOnOliver
×1

Use when you need to run a binary, trace execution, or observe runtime behavior. Runtime analysis via QEMU emulation, GDB debugging, and Frida hooking - syscall tracing (strace), breakpoints, memory inspection, function interception. Keywords - "run binary", "execute", "debug", "trace syscalls", "set breakpoint", "qemu", "gdb", "frida", "strace", "watch memory

7k tokens
Binary Re Tool Setup
by ComeOnOliver
×1

Use when reverse engineering tools are missing, not working, or need configuration. Installation guides for radare2 (r2), Ghidra, GDB, QEMU, Frida, binutils, and cross-compilation toolchains. Keywords - "install radare2", "setup ghidra", "r2 not found", "qemu missing", "tool not installed", "configure gdb", "cross-compiler

9k tokens
Binary Re Triage
by ComeOnOliver
×1

Use when first encountering an unknown binary, ELF file, executable, or firmware blob. Fast fingerprinting via rabin2 - architecture detection (ARM, x86, MIPS), ABI identification, dependency mapping, string extraction. Keywords - "what is this binary", "identify architecture", "check file type", "rabin2", "file analysis", "quick scan

5k tokens

How to use it

Copy the folder

Take kostja94/api-page-generator from the repository into ~/.claude/skills for personal use, or into .claude/skills inside a project.

Check the name does not clash

The agent identifies a skill by the name field in its header. Two skills with the same name cannot sit side by side — one of them will be ignored.