api-documentation
Generate comprehensive API documentation from OpenAPI specs, code comments, and interactive examples.
Works with
0
total installs
0
this week
88
GitHub stars
0
upvotes
Install Skill
Run in your terminal
0
installs
0
this week
88
stars
What it does
Supports OpenAPI/Swagger specification generation with full schema definitions, request/response examples, and security schemes
Includes JSDoc and decorator-based documentation extraction from TypeScript/Express codebases for automatic spec generation
Provides Swagger UI integration for interactive API exploration with try-it-out functionality
Covers authentication patterns, pagin
Installation Guide
How to use api-documentation on Cursor
AI-first code editor with Composer
Prerequisites
Before installing skills in Cursor, ensure your development environment meets these requirements:
- ›Cursor installed and configured on your machine
- ›Node.js 16+ with npm — verify with
node --version - ›Active project directory where you want to add
api-documentation
Run the install command
Execute the skills CLI command in your project's root directory to begin installation:
Fetches api-documentation from supercent-io/skills-template and configures it for Cursor.
Select Cursor when prompted
The CLI shows a list of agents. Use arrow keys and space to select Cursor:
Verify installation
Confirm successful installation by checking the skill directory location:
Restart Cursor to activate api-documentation. Access via /api-documentation in your agent's command palette.
Security Notice
We perform automated surface-level scans (Gen AI Scanner, Socket, Snyk) during installation. These checks detect common vulnerabilities but do not guarantee complete security. Always review skill source code and verify the publisher's reputation before production use.
Skills execute code in your environment. Always review source, verify the publisher, and test in isolation before production.
Documentation
API Documentation
When to use this skill
- API Development: When adding new endpoints
- External Release: Public API launch
- Team Collaboration: Frontend-backend interface definition
Instructions
Step 1: OpenAPI (Swagger) Spec
openapi: 3.0.0
info:
title: User Management API
version: 1.0.0
description: API for managing users
contact:
email: [email protected]
servers:
- url: https://api.example.com/v1
description: Production
- url: https://staging-api.example.com/v1
description: Staging
paths:
/users:
get:
summary: List all users
description: Retrieve a paginated list of users
tags:
- Users
parameters:
- name: page
in: query
schema:
type: integer
default: 1
- name: limit
in: query
schema:
type: integer
default: 20
maximum: 100
responses:
'200':
description: Successful response
content:
application/json:
schema:
type: object
properties:
data:
type: array
items:
$ref: '#/components/schemas/User'
pagination:
$ref: '#/components/schemas/Pagination'
'401':
$ref: '#/components/responses/Unauthorized'
post:
summary: Create a new user
tags:
- Users
requestBody:
required: true
content:
application/json:
schema:
$ref: '#/components/schemas/CreateUserRequest'
responses:
'201':
description: User created
content:
application/json:
schema:
$ref: '#/components/schemas/User'
'400':
$ref: '#/components/responses/BadRequest'
components:
schemas:
User:
type: object
properties:
id:
type: string
format: uuid
email:
type: string
format: email
name:
type: string
createdAt:
type: string
format: date-time
required:
- id
- email
- name
CreateUserRequest:
type: object
properties:
email:
type: string
format: email
name:
type: string
minLength: 2
maxLength: 50
password:
type: string
minLength: 8
required:
- email
- name
- password
Pagination:
type: object
properties:
page:
type: integer
limit:
type: integer
total:
type: integer
responses:
Unauthorized:
description: Unauthorized
content:
application/json:
schema:
type: object
properties:
error:
type: string
example: "Authentication required"
BadRequest:
description: Bad Request
content:
application/json:
schema:
type: object
properties:
error:
type: string
example: "Invalid input"
securitySchemes:
bearerAuth:
type: http
scheme: bearer
bearerFormat: JWT
security:
- bearerAuth: []
Step 2: Generate Documentation from Code (JSDoc/Decorators)
Express + TypeScript:
/**
* @swagger
* /api/users:
* post:
* summary: Create a new user
* tags: [Users]
* requestBody:
* required: true
* content:
* application/json:
* schema:
* type: object
* required:
* - email
* - name
* - password
* properties:
* email:
* type: string
* format: email
* name:
* type: string
* password:
* type: string
* minLength: 8
* responses:
* 201:
* description: User created successfully
* 400:
* description: Invalid input
*/
router.post('/users', async (req, res) => {
const { email, name, password } = req.body;
const user = await userService.createUser({ email, name, password List & Monetize Your Skill
Submit your Claude Code skill and start earning
Get started →Use Cases
Task Automation & Efficiency
Automate repetitive workflows and reduce manual effort
Example
Generate reports, summarize documents, draft communications
Save 3-5 hours per week on routine tasks
Knowledge Enhancement
Learn new skills, understand complex topics, get expert guidance
Example
Explain concepts, provide examples, suggest learning resources
Accelerate learning and skill development by 2x
Quality Improvement
Enhance output quality through reviews, suggestions, and refinements
Example
Review drafts, suggest improvements, catch errors
Improve work quality by 30-40% with less effort
Implementation Guide
Prerequisites
- ›Claude Desktop or compatible AI client with skill support
- ›Clear understanding of task or problem to solve
- ›Willingness to iterate and refine outputs
Time Estimate
15-45 minutes depending on use case complexity
Steps
- 1Install skill using provided installation command
- 2Test with simple use case relevant to your work
- 3Evaluate output quality and relevance
- 4Iterate on prompts to improve results
- 5Integrate into regular workflow if valuable
Common Pitfalls
- ⚠Expecting perfect results without iteration
- ⚠Not providing enough context in prompts
- ⚠Using skill for tasks outside its intended scope
- ⚠Accepting outputs without review and validation
Best Practices
✓ Do
- +Start with clear, specific prompts
- +Provide relevant context and constraints
- +Review and refine all outputs before using
- +Iterate to improve output quality
- +Document successful prompt patterns
✗ Don't
- −Don't use without understanding skill limitations
- −Don't skip validation of outputs
- −Don't share sensitive information in prompts
- −Don't expect skill to replace human judgment
💡 Pro Tips
- ★Be specific about desired format and style
- ★Ask for multiple options to choose from
- ★Request explanations to understand reasoning
- ★Combine AI efficiency with human expertise
When to Use This
✓ Use when
Use when skill capabilities match your task, clear ROI on time saved, and you can validate outputs. Best for repetitive tasks, learning, and quality improvement.
✗ Avoid when
Avoid when task requires deep expertise you can't validate, involves sensitive decisions, or when learning process is more valuable than speed of completion.
Learning Path
- 1Familiarize yourself with skill capabilities and limitations
- 2Start with low-risk, non-critical tasks
- 3Progress to more complex and valuable use cases
- 4Build expertise through regular use and experimentation
Related Skills
web-accessibility
56supercent-io/skills-template
pptx-presentation-builder
27supercent-io/skills-template
remotion-video-production
9supercent-io/skills-template
code-refactoring
8supercent-io/skills-template
writing-documentation-with-diataxis
9sammcj/agentic-coding
rest-api-design
7aj-geddes/useful-ai-prompts
Reviews
- AArya Martin★★★★★Dec 20, 2024
api-documentation reduced setup friction for our internal harness; good balance of opinion and flexibility.
- XXiao Sethi★★★★★Dec 8, 2024
Useful defaults in api-documentation — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
- RRen Thomas★★★★★Nov 27, 2024
We added api-documentation from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
- XXiao Jain★★★★★Nov 7, 2024
I recommend api-documentation for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
- MMeera Bansal★★★★★Nov 3, 2024
api-documentation reduced setup friction for our internal harness; good balance of opinion and flexibility.
- XXiao Reddy★★★★★Oct 26, 2024
api-documentation reduced setup friction for our internal harness; good balance of opinion and flexibility.
- HHenry Mensah★★★★★Oct 22, 2024
I recommend api-documentation for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
- RRen Li★★★★★Oct 18, 2024
Solid pick for teams standardizing on skills: api-documentation is focused, and the summary matches what you get after install.
- YYash Thakker★★★★★Sep 9, 2024
api-documentation fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
- RRahul Santra★★★★★Sep 5, 2024
api-documentation reduced setup friction for our internal harness; good balance of opinion and flexibility.
showing 1-10 of 40
Discussion
Comments — not star reviews- No comments yet — start the thread.