api-endpoint-scaffolder
Skill378 starsChanged 52 days agoMITView on GitHub
Generate REST API endpoints with proper structure, validation, error handling, and types. Use when creating new API routes, endpoints, or backend services.
In this repository229 other files it gives its agents.
- accessibility-auditorSkill
- agent-armySkill
- agent-eval-harnessSkill
- agent-swarm-deployerSkill
- agent-team-builderSkill
- agent-to-agentSkill
- ai-coding-guardrailsSkill
- ai-readiness-assessmentSkill
- animateSkill
- api-documentation-writerSkill
- api-load-testerSkill
- athlete-social-media-managerSkill
- before-you-buildSkill
- bi-measure-builderSkill
- board-deck-generatorSkill
- bookkeeping-closeSkill
- bracket-predictorSkill
- brand-consistency-checkerSkill
- brand-voice-analyzerSkill
- browser-test-loopSkill
- budget-optimizerSkill
- cash-flow-forecasterSkill
- champion-identifierSkill
- churn-autopsySkill
- claude-design-criticSkill
- claude-design-system-architectSkill
- claude-landing-composerSkill
- claude-md-writerSkill
- client-health-dashboardSkill
- client-proposal-generatorSkill
- code-review-proSkill
- cold-email-sequence-generatorSkill
- color-palette-extractorSkill
- commercial-lease-analyzerSkill
- company-announcement-writerSkill
- competitor-content-analyzerSkill
- competitor-intel-agentSkill
- competitor-price-trackerSkill
- compliance-checkerSkill
- contact-hunterSkill
- content-repurposerSkill
- context-budgetSkill
- contract-analyzerSkill
- contract-redlinerSkill
- conversation-archaeologistSkill
- cowork-calendar-defragSkill
- cowork-contract-renewal-radarSkill
- cowork-data-room-builderSkill
- cowork-deal-roomSkill
- cowork-expense-auditSkill
- cowork-folder-organizerSkill
- cowork-hiring-screenerSkill
- cowork-home-inventorySkill
- cowork-inbox-triageSkill
- cowork-invoice-chaserSkill
- cowork-medical-bill-auditorSkill
- cowork-qbr-builderSkill
- cowork-rfp-responseSkill
- cowork-sop-writerSkill
- cowork-tax-prep-organizerSkill
- The first 60 shown.
The file
We split this skill into the rules it gives an agent
2 rules. About 0 are common, 2 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈2
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
- Distinctive: line 10
When creating a new API endpoint:
- Distinctive: line 104
Document with OpenAPI/Swagger: when possible
≈ “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.
Files
API Endpoint Scaffolder
Instructions
When creating a new API endpoint:
- Identify the framework (Express, Next.js, FastAPI, etc.)
- Determine HTTP method (GET, POST, PUT, PATCH, DELETE)
- Define request/response types
- Implement with best practices
Templates
Next.js App Router (TypeScript)
// app/api/[resource]/route.ts
import { NextRequest, NextResponse } from 'next/server';
import { z } from 'zod';
const RequestSchema = z.object({
// Define your schema
});
export async function GET(request: NextRequest) {
try {
const { searchParams } = new URL(request.url);
// Implementation
return NextResponse.json({ data }, { status: 200 });
} catch (error) {
console.error('[API] Error:', error);
return NextResponse.json(
{ error: 'Internal server error' },
{ status: 500 }
);
}
}
export async function POST(request: NextRequest) {
try {
const body = await request.json();
const validated = RequestSchema.parse(body);
// Implementation
return NextResponse.json({ data }, { status: 201 });
} catch (error) {
if (error instanceof z.ZodError) {
return NextResponse.json(
{ error: 'Validation failed', details: error.errors },
{ status: 400 }
);
}
return NextResponse.json(
{ error: 'Internal server error' },
{ status: 500 }
);
}
}Express (TypeScript)
import { Router, Request, Response, NextFunction } from 'express';
import { z } from 'zod';
const router = Router();
const CreateSchema = z.object({
// Define schema
});
router.post('/', async (req: Request, res: Response, next: NextFunction) => {
try {
const data = CreateSchema.parse(req.body);
// Implementation
res.status(201).json({ success: true, data });
} catch (error) {
next(error);
}
});
export default router;Best Practices
- Always validate input using Zod, Yup, or similar
- Use proper HTTP status codes:
- 200: Success
- 201: Created
- 400: Bad Request
- 401: Unauthorized
- 403: Forbidden
- 404: Not Found
- 500: Server Error
- Log errors but don't expose internals to clients
- Use consistent response format
- Add rate limiting for public endpoints
- Document with OpenAPI/Swagger when possible
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
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.

