agentleFS
amanning3390amanning3390/hermeshub/skills/api-builder/SKILL.md

api-builder

Skill48 starsChanged 5 months agoMITView on GitHub

Design, scaffold, and document REST/GraphQL APIs with OpenAPI specs. Use when the user wants to build an API, create endpoints, generate docs, or scaffold a backend service.

2 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

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈6

    Distinctive · estimate

    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:

    Add error handling and middleware

    line 30
  2. Distinctive:

    DELETE /resources/:id — delete one

    line 44
  3. Distinctive:

    Don't expose internal IDs in public APIs

    line 55
  4. Distinctive:

    Always validate request bodies

    line 56
  5. Distinctive:

    Don't return sensitive data in error messages

    line 58
  6. Distinctive:

    All endpoints respond with correct status codes

    line 61

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “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 Builder

End-to-end API design, scaffolding, and documentation.

When to Use

  • User wants to create a new API
  • User needs endpoints for a specific domain
  • User wants OpenAPI/Swagger documentation
  • User asks for API scaffolding or boilerplate

Procedure

  1. Gather requirements: resources, operations, auth model
  2. Design the API schema (resources, relationships, endpoints)
  3. Generate OpenAPI 3.0 spec
  4. Scaffold route handlers with validation
  5. Add error handling and middleware
  6. Generate documentation
  7. Create test fixtures

Supported Frameworks

  • Express (Node.js): express + zod + swagger-jsdoc
  • FastAPI (Python): automatic OpenAPI generation
  • Flask (Python): flask-restx or flask-smorest

REST Conventions

  • GET /resources — list all
  • POST /resources — create one
  • GET /resources/:id — get one
  • PATCH /resources/:id — update one
  • DELETE /resources/:id — delete one

Best Practices

  • Consistent error response format
  • Pagination for list endpoints
  • Rate limiting middleware
  • Request validation on all inputs
  • CORS configuration
  • Authentication middleware

Pitfalls

  • Don't expose internal IDs in public APIs
  • Always validate request bodies
  • Version your API (v1, v2) from the start
  • Don't return sensitive data in error messages

Verification

  • All endpoints respond with correct status codes
  • Validation rejects malformed input
  • Documentation renders correctly
  • Auth middleware blocks unauthorized requests

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.