Claude-skill-registry http-api-openapi

Keep HTTP handlers and OpenAPI (openapi.yaml) in sync. Use when adding/changing endpoints, request/response schemas, auth requirements, or error shapes.

install

source · Clone the upstream repo

git clone https://github.com/majiayu000/claude-skill-registry

Claude Code · Install into ~/.claude/skills/

T=$(mktemp -d) && git clone --depth=1 https://github.com/majiayu000/claude-skill-registry "$T" && mkdir -p ~/.claude/skills && cp -r "$T/skills/data/http-api-openapi" ~/.claude/skills/majiayu000-claude-skill-registry-http-api-openapi && rm -rf "$T"

manifest: skills/data/http-api-openapi/SKILL.md

Tooling assumptions

Use a terminal runner with bash and git available.
Prefer
```
make
```
targets when available; fall back to direct CLI commands when needed.

Source of truth

OpenAPI spec:
```
openapi.yaml
```
at the repo root.

Typical workflow

Update
```
openapi.yaml
```
(paths, schemas, auth).
Validate the spec:

make validate-openapi

swagger-cli

isn’t installed:

npm install -g @apidevtools/swagger-cli

Implement the handler changes in Go (and keep auth consistent with the spec).
Run tests:

make test

Project-specific notes

Authenticated endpoints use Bearer token auth (see README’s Auth section).
Be explicit about error responses and status codes in the spec when behavior changes.