Agent skill · Backend & API

api-endpoint-create

Standard procedure for creating robust API endpoints

majiayu000github.com/majiayu000GitHub ↗
claude-codeMIT
Install
npx skills add majiayu000/claude-skill-registry --skill api-endpoint-create-cpa03-blueprintify-2 --agent claude-code

Same command for any agent — swap --agent for codex, cursor, copilot.

Facts
Files in the skill folder: 2
SKILL.md size: 0 KB
Bundled scripts: none
Path: skills/api/api-endpoint-create-cpa03-blueprintify-2/SKILL.md
Open the folder on GitHub →
Where it comes from
Stars: 534
Language: HTML

Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.

From the SKILL.md

## Procedure 1. Define the Request/Response schema (Zod/OpenAPI). 2. Create the route handler/controller. 3. Implement business logic in a service layer. 4. Add authentication/authorization middleware. 5. Write an integration test for the endpoint.

What's inside
Steps it walks through
  1. Procedure
Ships with 1 file
  • metadata.json
More from claude-skill-registry
All skills →
About this skill
What does the api-endpoint-create skill do?

Standard procedure for creating robust API endpoints

How do I install it?

Run `npx skills add majiayu000/claude-skill-registry --skill api-endpoint-create-cpa03-blueprintify-2 --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.

Where does this skill come from?

From majiayu000/claude-skill-registry, a repository with 534 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.

Is a popular skill a good skill?

Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.

Keep going