API Designer
Jeffallan/claude-skills
Designs REST and GraphQL APIs from resource modeling to an OpenAPI 3.1 contract, with versioning, pagination and RFC 7807 error handling.
Write and update OpenAPI 3.0 specification files from REST API code.
$ npx skills add BlueAndi/Pixelix --skill openapi-spec -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install BlueAndi/Pixelix openapi-spec --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/BlueAndi/Pixelix.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.github/skills/openapi-spec .claude/skills/openapi-spec && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "openapi-spec" agent skill from https://github.com/BlueAndi/Pixelix/tree/master/.github/skills/openapi-spec into .claude/skills/openapi-spec/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "openapi-spec", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/BlueAndi/Pixelix/tree/master/.github/skills/openapi-specType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add BlueAndi/Pixelix --skill openapi-spec -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install BlueAndi/Pixelix openapi-spec --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/BlueAndi/Pixelix.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.github/skills/openapi-spec .agents/skills/openapi-spec && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "openapi-spec" agent skill from https://github.com/BlueAndi/Pixelix/tree/master/.github/skills/openapi-spec into .agents/skills/openapi-spec/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "openapi-spec", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add BlueAndi/Pixelix --skill openapi-spec -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install BlueAndi/Pixelix openapi-spec --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/BlueAndi/Pixelix.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.github/skills/openapi-spec .cursor/skills/openapi-spec && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "openapi-spec" agent skill from https://github.com/BlueAndi/Pixelix/tree/master/.github/skills/openapi-spec into .cursor/skills/openapi-spec/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "openapi-spec", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/BlueAndi/Pixelix.git --path .github/skills/openapi-spec--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add BlueAndi/Pixelix --skill openapi-spec -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install BlueAndi/Pixelix openapi-spec --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/BlueAndi/Pixelix.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.github/skills/openapi-spec .gemini/skills/openapi-spec && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "openapi-spec" agent skill from https://github.com/BlueAndi/Pixelix/tree/master/.github/skills/openapi-spec into .gemini/skills/openapi-spec/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "openapi-spec", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install BlueAndi/Pixelix openapi-specInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add BlueAndi/Pixelix --skill openapi-spec -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/BlueAndi/Pixelix.git skills-src && mkdir -p .github/skills && cp -r skills-src/.github/skills/openapi-spec .github/skills/openapi-spec && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "openapi-spec" agent skill from https://github.com/BlueAndi/Pixelix/tree/master/.github/skills/openapi-spec into .github/skills/openapi-spec/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "openapi-spec", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add BlueAndi/Pixelix --skill openapi-spec -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install BlueAndi/Pixelix openapi-spec --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/BlueAndi/Pixelix.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.github/skills/openapi-spec .opencode/skills/openapi-spec && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "openapi-spec" agent skill from https://github.com/BlueAndi/Pixelix/tree/master/.github/skills/openapi-spec into .opencode/skills/openapi-spec/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "openapi-spec", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
openapi-specWrite and update OpenAPI 3.0 specification files from REST API code.
Openapi Spec is an agent skill from BlueAndi/Pixelix. Write and update OpenAPI 3.0 specification files from REST API code. Use when: documenting REST endpoints, creating API specs, generating swagger.yaml, updating API documentation from implementation.
Its SKILL.md is about 3.2k tokens, which your agent loads only when the skill is triggered. The skill folder holds 2 other files, including reference files (for example `references/openapi-template.yaml`).
It sits in Backend & APIs, covering OpenAPI specifications and REST APIs. It works with OpenAPI and ESP32. The repository describes itself as: Full RGB LED matrix, based on an ESP32 and WS2812B LEDs or emulated LEDs on TFT. The licence is MIT.
7 steps, taken from the step headings in SKILL.md.
Read from SKILL.md and the folder at commit 10209e7. It shows what the files ask for, not the result of running them.
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
No scripts in the folder and no shell commands in SKILL.md (its code samples are yaml, cpp and bash).
From the folder's file list and the shell code blocks in SKILL.md.
Hosts in commands or code, which the agent is likely to contact:
swagger.ioAlso links to:
editor.swagger.ioFrom URLs in SKILL.md, links to its own repository left out.
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Openapi Spec loads about 3.2k tokens when it runs, and up to ~3.9k if it reads all its reference files. Until then it costs about 53 tokens; SKILL.md has 903 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
The full file from BlueAndi/Pixelix at commit 10209e7, republished under its MIT licence (© BlueAndi). 903 words, ~3,214 tokens.
.claude/skills/openapi-spec/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.Load this skill when asked to:
openapi.yaml or swagger.yaml fileSearch for and identify:
server.on(), route arrays):id, {id}, wildcards)request->getParam() or equivalentSome REST APIs use plugin or service architectures where endpoints are registered dynamically:
Common patterns to search for:
getTopics() or registerTopics() methods in plugins/servicesTOPIC_CONFIG, TOPIC_STATUS)Topic-based endpoint patterns:
/api/v1/display/uid/{uid}/{topic} or /display/alias/{alias}/{topic}/api/v1/{entityId}/{topic}/api/v1/{topic} (empty entityId)/api/v1/{entityId}/{index}/{topic}How to find dynamic endpoints:
getTopics() implementations - these list available topicsgetTopic() and setTopic() methods - these handle GET/POST requestsTopicHandlerService or similar dynamic registration systemsExample (C++):
// Plugin defines topics
const char* TOPIC_CONFIG = "config";
const char* TOPIC_STATUS = "status";
void Plugin::getTopics(JsonArray& topics) const
{
topics.add(TOPIC_CONFIG); // Creates GET/POST /display/uid/{uid}/config
topics.add(TOPIC_STATUS); // Creates GET/POST /display/uid/{uid}/status
}
bool Plugin::getTopic(const String& topic, JsonObject& value) const
{
if (topic.equals(TOPIC_CONFIG)) {
// Handle GET request
}
}
bool Plugin::setTopic(const String& topic, const JsonObjectConst& value)
{
if (topic.equals(TOPIC_CONFIG)) {
// Handle POST request
}
}Critical: Don't assume you've found all endpoints after discovering static routes.
Complete discovery workflow:
getTopics() implementationsSearch patterns:
# Find topic definitions
grep -r "TOPIC_" --include="*.cpp" --include="*.h"
# Find getTopics implementations
grep -r "getTopics" --include="*.cpp"
# Find topic handlers
grep -r "getTopic\|setTopic" --include="*.cpp"
# Find topic registration
grep -r "registerTopic" --include="*.cpp"Start with the base template:
openapi: 3.0.3
info:
title: [API Name]
version: [Version from VERSION constant or git tag]
description: [Brief API description]
contact:
name: [From LICENSE or README]
email: [If available]
servers:
- url: http://{host}/rest/api/v1
description: REST API base path
variables:
host:
default: localhost
description: Device hostname or IP
paths:
# Endpoints go here
components:
schemas:
# Reusable schemas
responses:
# Common responses
securitySchemes:
# Auth schemesFor each route/handler found:
/path/{param}:
get:
summary: [One-line description from code comments]
description: [Detailed behavior from docstrings/comments]
operationId: [camelCase unique identifier]
tags:
- [Logical grouping]
parameters:
- name: param
in: path
required: true
schema:
type: string
description: [From parameter docs]
- name: query
in: query
required: false
schema:
type: integer
description: [From code inspection]
responses:
'200':
description: Success
content:
application/json:
schema:
$ref: '#/components/schemas/SuccessResponse'
example:
status: "ok"
data: {}
'400':
$ref: '#/components/responses/BadRequest'
'404':
$ref: '#/components/responses/NotFound'From JSON response building code, create reusable schemas:
components:
schemas:
SuccessResponse:
type: object
required:
- status
- data
properties:
status:
type: string
enum: [ok]
data:
type: object
description: Endpoint-specific response data
ErrorResponse:
type: object
required:
- status
- msg
properties:
status:
type: string
enum: [error]
msg:
type: string
description: Human-readable error messageIf authentication is present:
components:
securitySchemes:
basicAuth:
type: http
scheme: basic
description: HTTP Basic Authentication
# Then apply to protected endpoints:
paths:
/protected:
get:
security:
- basicAuth: []/$ref references existtagsSave the specification as:
docs/openapi.yaml or docs/swagger.yaml (YAML preferred)docs/api-spec.yaml (alternative naming)Include a comment header:
# OpenAPI 3.0.3 Specification
# Generated from: [source files]
# Last updated: [date]
# See: https://swagger.io/docs/specification/v3_0//items:
get:
summary: List all items
responses:
'200':
description: Array of items
post:
summary: Create new item
requestBody:
required: true
content:
application/json:
schema:
$ref: '#/components/schemas/ItemCreate'
responses:
'201':
description: Item created
/items/{id}:
get:
summary: Get single item
put:
summary: Update item
delete:
summary: Delete itemparameters:
- name: limit
in: query
schema:
type: integer
minimum: 1
maximum: 100
default: 20
- name: offset
in: query
schema:
type: integer
minimum: 0
default: 0requestBody:
content:
multipart/form-data:
schema:
type: object
properties:
file:
type: string
format: binary
path:
type: stringIssue: APIs may use numeric IDs internally instead of file paths.
Example:
# WRONG - assumes API uses file paths
parameters:
- name: iconPath
schema:
type: string
example: "/images/icon.bmp"
# CORRECT - API uses numeric file IDs
parameters:
- name: iconFileId
schema:
type: number
example: 1234How to identify: Check the actual implementation - look for FileId types, ID resolution methods like getFileFullPathById(), or file manager services that map IDs to paths.
Issue: Forgetting to document endpoints that are registered dynamically via plugin/service systems.
Solution:
getTopics(), registerTopics(), or similar methodsExample: In Pixelix, sensor endpoints (/sensors/{index}/{channelName}) are created dynamically by SensorDataProvider registering topics via TopicHandlerService, not found in static route arrays.
Issue: API paths may have multiple formats depending on registration method.
Check for:
/{serviceId}/{topic}/display/uid/{uid}/{topic}/display/alias/{alias}/{topic}/{entityId}/{index}/{topic}/{topic} (no prefix)Issue: Documentation doesn't match actual parameter types used in code.
Verify:
getTopic()/setTopic() implementationsIssue: Some topics serve dual purposes.
Pattern:
action parameterExample:
# Command topic - action-based
/display/uid/{uid}/playCtrl:
post:
parameters:
- name: action
schema:
type: string
enum: [next, previous, pause, continue]$ref for reusability: Common responses and schemas should be defined once in componentsoperationId for code generation toolsinfo.version matching your API versioning schemeAfter generating the spec, validate it using:
swagger-cli validate openapi.yaml - CLI validation© BlueAndi, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
SKILL.md and 1 other file (references) in .github/skills/openapi-spec of BlueAndi/Pixelix.
Open the folder on GitHubat commit 10209e7
Openapi Spec next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Openapi Spec this skillBlueAndi/Pixelix | 443 | — | ~3.2k | Automated safety check: Pass | MIT | |
| API DesignerJeffallan/claude-skills | 12k | 2 repos | ~2k | Automated safety check: Pass | MIT | |
| OpenAPI to MCP Servermcp-use/mcp-use | 11k | — | ~5.2k | Automated safety check: Pass | Apache-2.0 | |
| Use Yaakmountain-loop/yaak | 19k | — | ~1.9k | Automated safety check: Pass | MIT | |
| Old Coder API DesignAmazingAng/old-coder | 749 | 1 repos | ~3.4k | Automated safety check: Pass | MIT | |
| API CallerNVIDIA/SkillEvaluator | 544 | 1 repos | ~1.1k | Automated safety check: Pass | Apache-2.0 |
Jeffallan/claude-skills
Designs REST and GraphQL APIs from resource modeling to an OpenAPI 3.1 contract, with versioning, pagination and RFC 7807 error handling.
mcp-use/mcp-use
Turns an OpenAPI or Swagger spec into an MCP server with the mcp-use TypeScript SDK, mapping each operation to a tool, wiring auth, testing and deploying.
mountain-loop/yaak
A skill your agent uses when the user mentions Yaak, a Yaak workspace, or the yaak command, or asks to call, hit, or smoke test HTTP/REST endpoints, save or organize API requests for reuse or manual…
AmazingAng/old-coder
Reviews or designs an HTTP/JSON API's endpoints, auth, pagination, versioning and deprecations, guarding against inventing a bespoke interface or silently breaking consumers.
NVIDIA/SkillEvaluator
Call any REST API dynamically. An agent skill from NVIDIA/SkillEvaluator.
huangjia2019/claude-code-engineering
Generate API endpoint code and documentation from specifications.
BlueAndi/Pixelix
Create and edit OpenSCAD (.scad) files for 3D-printable mechanical parts and housings.
BlueAndi/Pixelix
Model, create, update, and embed PlantUML diagrams (.wsd files).
BlueAndi/Pixelix
A skill your agent uses when building or reviewing UI with Bootstrap 5.3 — setting up the CDN/npm, using the grid & breakpoints, utility classes (spacing/color/flex/display), components (navbar…
BlueAndi/Pixelix
Write and refactor embedded C/C++14 code with MISRA-oriented rules, defensive programming, Yoda conditions, pathfinder rule, mandatory Doxygen, and clang-format compliance.
BlueAndi/Pixelix
A skill your agent uses when authoring, reviewing, or validating HTML markup — choosing the right element, deciding what may nest inside what, writing forms/inputs, adding accessible semantics, or…
BlueAndi/Pixelix
A skill your agent uses when writing, reviewing, or debugging JavaScript — reasoning about type coercion, equality, this, closures, scope/hoisting, prototypes, async/promises, iterators, modules, or…
Categories
Write and update OpenAPI 3.0 specification files from REST API code. Openapi Spec is an agent skill from BlueAndi/Pixelix.0 specification files from REST API code.
Openapi Spec fits situations like: : documenting REST endpoints; creating API specs; generating swagger.yaml; updating API documentation from implementation.
Run `npx skills add BlueAndi/Pixelix --skill openapi-spec -a claude-code`. Or copy the skill folder (.github/skills/openapi-spec in BlueAndi/Pixelix) into .claude/skills/openapi-spec in your project. Claude Code loads it when a task matches its description.
Run `npx skills add BlueAndi/Pixelix --skill openapi-spec -a codex`. Or copy the skill folder (.github/skills/openapi-spec in BlueAndi/Pixelix) into .agents/skills/openapi-spec in your project. Codex loads it when a task matches its description.
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add BlueAndi/Pixelix --skill openapi-spec -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/openapi-spec, .gemini/skills/openapi-spec, .github/skills/openapi-spec and .opencode/skills/openapi-spec in your project.
SKILL.md names no scripts, command-line tools or credentials: Openapi Spec is instructions for the agent only.
SKILL.md names 2 domains. In commands or code: swagger.io; the agent is likely to contact it when it follows the instructions. As links in the text: editor.swagger.io. This is read from the text; nothing was executed.
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
Openapi Spec is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
About 3.2k tokens (SKILL.md is roughly 13k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 722 tokens, read only when the agent opens those files.
Skills that share tags, products or a category with Openapi Spec: API Designer (Jeffallan/claude-skills, 12k stars), OpenAPI to MCP Server (mcp-use/mcp-use, 11k stars), Use Yaak (mountain-loop/yaak, 19k stars) and Old Coder API Design (AmazingAng/old-coder, 749 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
BlueAndi (a GitHub user) maintains it in BlueAndi/Pixelix, which has 443 GitHub stars. The repository holds 7 skills in this directory. The repository was last updated on October 6, 2026.
Source: BlueAndi/Pixelix on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.