Api endpoint

Skill syniol/llm-software-project/.agent/skills/api-endpoint

AI Ready Software Template for Enterprise Multi-Model AI Context Architecture

Install

npx -y skills add syniol/llm-software-project --skill api-endpoint

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

2 things to look at

17 days oldThe repository was created 17 days ago. New is not bad, but a brand new repository carrying a familiar-sounding name is the shape a typosquat arrives in, and there has been no time for anyone else to find a problem with it.
0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

Instructions for creating REST API endpoints following conventions, validation, and documentation standards.

SKILL.md

2.0 KB, as published. Nobody here has run it

API Endpoint Creation Skill

When creating a new API endpoint, follow this procedure exactly:

1. REST Conventions

Action	HTTP Verb	Route Pattern	Success Code
List resources	`GET`	`/api/v1/resources`	`200`
Get single	`GET`	`/api/v1/resources/:id`	`200`
Create resource	`POST`	`/api/v1/resources`	`201`
Update resource	`PATCH`	`/api/v1/resources/:id`	`200`
Replace resource	`PUT`	`/api/v1/resources/:id`	`200`
Delete resource	`DELETE`	`/api/v1/resources/:id`	`204`

2. Request/Response Validation

Define Zod schemas for both request body and response body.
Validate at the middleware layer, before the handler executes.

const CreateUserSchema = z.object({
  email: z.string().email(),
  name: z.string().min(1).max(100),
  role: z.enum(['admin', 'member', 'viewer']),
});

3. Standardised Error Response

All errors must return this shape:

{
  "error": {
    "code": "VALIDATION_ERROR",
    "message": "Email format is invalid.",
    "details": [{ "field": "email", "issue": "Invalid email format" }]
  }
}

4. Middleware Chain

Every endpoint must pass through this middleware chain in order:

authenticate — Verify JWT, attach req.user.
authorize — Check RBAC permissions for the route.
validate — Run Zod schema validation on req.body / req.query.
handler — Execute business logic.
errorHandler — Catch and format any thrown errors.

5. OpenAPI Documentation

Annotate every endpoint with JSDoc or decorators that generate OpenAPI 3.0 specs.
Include request body schema, response schema, error codes, and authentication requirements.

Gives 0 of the 12 instructions most apis services skills give

Counted across 424 of the 426 authors here whose files we hold, read 2026-08-06

use plural nouns for resource namesin 41 of 424, across 32 files
use cursor-based pagination for large datasetsin 35 of 424, across 20 files
include rate limit headers in responsesin 25 of 424, across 13 files
Use kebab-case for multi-word resourcesin 23 of 424, across 13 files
version APIs in the URL pathin 19 of 424, across 9 files
use semantic HTTP status codesin 18 of 424, across 8 files
verify webhook signaturesin 18 of 424, across 11 files
use query parameters for filteringin 17 of 424, across 6 files
use async database operationsin 14 of 424, across 7 files
wrap successful responses in a data fieldin 13 of 424, across 3 files
prefix sorting parameters with a hyphen for descending orderin 13 of 424, across 3 files
set appropriate HTTP status codesin 13 of 424, across 6 files

Said here and by no other author read

use REST conventions for verbs, routes and success codes
define Zod schemas for request and response bodies
validate at the middleware layer before the handler
apply the middleware chain in the specified order
authenticate requests and attach the user object
authorize requests using RBAC permissions

Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once.