菜单
Become a REST client and QA a live API against its spec. Spawns subagents to hit the server with real requests, finds gaps where the spec lies, and compiles feedback. Use when auditing or hammering an existing API implementation against its OpenAPI/Swagger contract.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Use this skill when the user wants to set up a new TypeScript project or add standard tooling to an existing one. Triggers on phrases like "set up this repo", "initialize the project", "add linting", "scaffold this", "set up tooling", "configure typescript", or "sow".
Audit an API, CLI, or config surface for what it makes easy (affordances) and what it makes easy to get wrong (anti-affordances, footguns). Finds the pit-of-success versus the footgun, and the smell where the primary use is smooth but the secondary use is awkward. The principle: good design you act through without noticing; bad design makes you fight it. Use when designing or reviewing a public interface, library, SDK, or command surface. Triggers on "API ergonomics", "is this easy to misuse", "footgun", "pit of success", "review this interface", "review this CLI", "ergonomics".
Guidelines for authoring reusable UI components. Use when asked to create new frontend features, components, or design-adjacent tasks.
Always use when user asks to create, generate, draw, or design a diagram, flowchart, architecture diagram, ER diagram, sequence diagram, class diagram, network diagram, mockup, wireframe, or UI sketch, or mentions draw.io, drawio, drawoi, .drawio files, or diagram export to PNG/SVG/PDF.
A code-review lens that flags cleverness for its own sake, fashion-driven choices, premature abstraction, and indirection that serves the author instead of the reader. Asks one question of every choice: who does this serve? Empathy over ego: ego-driven work never produces something humane. Use when reviewing a diff or PR, especially a clever or trendy one. Triggers on "review this", "is this over-engineered", "too clever", "code review", "is this abstraction worth it".
Export the current Pi or Claude Code conversation transcript to a standalone HTML file. Use whenever the user invokes this skill, says /export, asks to export/share/save the current agent session, or wants a transcript HTML without manually finding a JSONL path or installing devlog.
| name | become-rest-client |
| description | Become a REST client and QA a live API against its spec. Spawns subagents to hit the server with real requests, finds gaps where the spec lies, and compiles feedback. Use when auditing or hammering an existing API implementation against its OpenAPI/Swagger contract. |
| arguments | ["spec","server","details"] |
| argument-hint | <spec> <server> <details> |
| metadata | {"author":"Mark Anthony Cianfrani","version":"0.2.0"} |
Audit $server against spec $spec using only the spec as your map. $details may narrow scope.
Pick a kebab-case $NAME from the spec's info.title, then:
./scripts/ensure-restish.sh
./scripts/init-api.sh --name "$NAME" --spec "$spec" --base "$server"
# init refuses if "$NAME" already exists; switch to update-api.sh if so
restish $NAME --help now lists every operation grouped by tag.
Group operations by tag. In one message, spawn a parallel Agent per tag. Each subagent gets the API name, its operation list, auth (existing profile or a bearer via -H authorization:...), and this checklist:
restish <name> <op> --help — required flags match the spec?<op> — expected — actual — severity. Structured, ~300 words max.Group findings as spec lies (server contradicts spec), spec gaps (server returns undocumented things), server bugs (violates own spec), ambiguities (spec silent). Link each to the operation. The user files tickets from this.