agentleFS
z-waterkingz-waterking/claude-skills/api-documenter/SKILL.md

api-documenter

Skill0 starsChanged 7 months agoMITView on GitHub

Generate OpenAPI specs and documentation from Flask/FastAPI/Express route definitions

7 other projects use a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

3 rules. 0 are common, 3 are distinctive, and 0 are very specific to this project.

  • 0

    Common

    Most of the 6 edited versions we read keep these.

  • 3

    Distinctive

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Identify the framework: Use Grep to detect the framework (Flask, FastAPI, Express) by looking for imports.

    line 18
  2. Distinctive:

    Extract routes: Run the generator:

    line 20
  3. Distinctive:

    Review and enhance: Add descriptions, examples, and authentication details that couldn't be auto-extracted.

    line 36

“Common” is measured: kept by at least 6 in 10 of the 6 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

API Documenter Skill

You are an API documentation specialist. When the user asks to document an API, follow this workflow:

Workflow

  1. Identify the framework: Use Grep to detect the framework (Flask, FastAPI, Express) by looking for imports.
  2. Extract routes: Run the generator:
    python3 {skill_path}/scripts/generator.py <app_file> --framework <flask|fastapi|express>
    Extracts endpoints, HTTP methods, parameters, request/response schemas.
  3. Parse existing specs (if any):
    python3 {skill_path}/scripts/spec_parser.py <openapi_file>
  4. Generate HTML documentation:
    python3 {skill_path}/scripts/html_renderer.py <openapi_spec> --output <output.html>
  5. Review and enhance: Add descriptions, examples, and authentication details that couldn't be auto-extracted.
  6. Present to user: Show the generated documentation and offer to refine.

Supported Frameworks

  • Flask (route decorators)
  • FastAPI (path operation decorators)
  • Express.js (router methods — basic parsing)

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.