MCP Server Builder
anthropics/skills
Guides the design and implementation of Model Context Protocol servers in TypeScript or Python, from tool naming and error messages to evaluation.
Compatibility assessment for items with the needs-api-compat-review trait.
Install API Compat Review
$ npx skills add jpicklyk/task-orchestrator --skill api-compat-review -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install jpicklyk/task-orchestrator api-compat-review --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/jpicklyk/task-orchestrator.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.claude/skills/api-compat-review .claude/skills/api-compat-review && 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 "api-compat-review" agent skill from https://github.com/jpicklyk/task-orchestrator/tree/main/.claude/skills/api-compat-review into .claude/skills/api-compat-review/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "api-compat-review", 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/jpicklyk/task-orchestrator/tree/main/.claude/skills/api-compat-reviewType 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 jpicklyk/task-orchestrator --skill api-compat-review -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install jpicklyk/task-orchestrator api-compat-review --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/jpicklyk/task-orchestrator.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.claude/skills/api-compat-review .agents/skills/api-compat-review && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "api-compat-review" agent skill from https://github.com/jpicklyk/task-orchestrator/tree/main/.claude/skills/api-compat-review into .agents/skills/api-compat-review/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "api-compat-review", 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 jpicklyk/task-orchestrator --skill api-compat-review -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install jpicklyk/task-orchestrator api-compat-review --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/jpicklyk/task-orchestrator.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.claude/skills/api-compat-review .cursor/skills/api-compat-review && 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 "api-compat-review" agent skill from https://github.com/jpicklyk/task-orchestrator/tree/main/.claude/skills/api-compat-review into .cursor/skills/api-compat-review/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "api-compat-review", 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/jpicklyk/task-orchestrator.git --path .claude/skills/api-compat-review--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 jpicklyk/task-orchestrator --skill api-compat-review -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install jpicklyk/task-orchestrator api-compat-review --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/jpicklyk/task-orchestrator.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.claude/skills/api-compat-review .gemini/skills/api-compat-review && 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 "api-compat-review" agent skill from https://github.com/jpicklyk/task-orchestrator/tree/main/.claude/skills/api-compat-review into .gemini/skills/api-compat-review/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "api-compat-review", 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 jpicklyk/task-orchestrator api-compat-reviewInstalls 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 jpicklyk/task-orchestrator --skill api-compat-review -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/jpicklyk/task-orchestrator.git skills-src && mkdir -p .github/skills && cp -r skills-src/.claude/skills/api-compat-review .github/skills/api-compat-review && 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 "api-compat-review" agent skill from https://github.com/jpicklyk/task-orchestrator/tree/main/.claude/skills/api-compat-review into .github/skills/api-compat-review/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "api-compat-review", 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 jpicklyk/task-orchestrator --skill api-compat-review -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install jpicklyk/task-orchestrator api-compat-review --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/jpicklyk/task-orchestrator.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.claude/skills/api-compat-review .opencode/skills/api-compat-review && 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 "api-compat-review" agent skill from https://github.com/jpicklyk/task-orchestrator/tree/main/.claude/skills/api-compat-review into .opencode/skills/api-compat-review/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "api-compat-review", 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.
Facts
- Skill name
api-compat-review- GitHub stars
- 207
- Token cost
- ~636 tokens
- SKILL.md length
- 294 words
- Files
- 1
- Skills in repo
- 28
- Repo updated
- First seen
- Licence
- MIT
At a glance
Compatibility assessment for items with the needs-api-compat-review trait.
- Works in 3 steps: Classify the Change → MCP Surface Assessment → REST Surface Assessment
- Tasks that involve MCP servers
- SKILL.md covers Step 1: Classify the Change, Step 2: MCP Surface Assessment, Step 3: REST Surface Assessment and Output
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
API Compat Review is an agent skill from jpicklyk/task-orchestrator. Compatibility assessment for items with the needs-api-compat-review trait. Evaluates the MCP tool surface and the REST surface separately, since their compatibility models differ. Invoked via skillPointer when filling api-compatibility notes.
Its SKILL.md is about 640 tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in Agent Workflows, covering MCP servers. It works with Model Context Protocol. The repository describes itself as: Server-enforced workflow discipline for AI agents. An MCP server providing persistent work items, dependency graphs, quality gates, and actor attribution. Schemas define what… The licence is MIT.
When your agent uses it
- Tasks that involve MCP servers
Example prompts
- “/api-compat-review”
Workflow steps
3 steps, taken from the step headings in SKILL.md.
What it can do on your machine
Read from SKILL.md and the folder at commit 3e83170. It shows what the files ask for, not the result of running them.
Tool permissions
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.
Runs code
No scripts in the folder and no shell commands in SKILL.md.
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
API Compat Review loads about 636 tokens when it runs. Until then it costs about 65 tokens; SKILL.md has 294 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.
Safety
Auto-check passed
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.
SKILL.md
The full file from jpicklyk/task-orchestrator at commit 3e83170, republished under its MIT licence (© jpicklyk). 294 words, ~636 tokens.
Download SKILL.mdSave it as
.claude/skills/api-compat-review/SKILL.md (or your agent's skills folder).- name
- api-compat-review
- description
- Compatibility assessment for items with the needs-api-compat-review trait. Evaluates the MCP tool surface and the REST surface separately, since their compatibility models differ. Invoked via skillPointer when filling api-compatibility notes.
- user-invocable
- false
API Compatibility Review Framework
Assess API changes by surface — the MCP tool surface (dynamically re-discovered by clients) and the REST surface (hardcoded clients) have different compatibility models. Do not apply REST-style breaking-change caution to MCP tools, and do not apply MCP's rename-friendliness to REST.
Step 1: Classify the Change
Determine which surface(s) the change touches:
- MCP tools —
application/tools/tool definitions,parameterSchema, tooldescriptionstrings - REST API —
interfaces/api/v1/routes/,interfaces/api/v1/dto/Dtos.kt,openapi.yaml
A single change (e.g., a domain model field rename) can touch both surfaces independently — assess each.
Step 2: MCP Surface Assessment
LLM clients re-read the tools/list schema every session — there is no persistent client binding to break. A pure parameter rename does NOT require keeping the old name working. Verify instead:
- Every changed param's
parameterSchemakey and its arg-parsing read site stay in sync — no schema-says-X/code-reads-Y drift - ALL first-party callers update in lockstep: plugin skills, hooks (including the
orchestration-contexthook's injected text), auto-memory references, andapi-reference.md. This doc coordination is the real cost of an MCP change, not client breakage. - The tool
descriptionstring accurately reflects the new behavior
Step 3: REST Surface Assessment
HTTP clients hardcode field and param names, so compatibility DOES matter here:
- Response-shape changes are additive (new fields only) where possible
- Renames or removals of existing fields/params have an explicit migration path or version bump — not a silent break
- Note when a surface has effectively zero consumers (e.g., a days-old endpoint) so the reviewer can right-size caution instead of over-indexing on hypothetical clients
-
openapi.yamlis updated for any REST-facing change -
api-rest.mdis updated for any REST-facing change
Output
Compose the api-compatibility note with findings from Step 2 and/or Step 3, scoped to whichever surface(s) the change actually touches. If a surface wasn't touched, say so explicitly rather than omitting it silently.
© jpicklyk, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
Just SKILL.md in .claude/skills/api-compat-review of jpicklyk/task-orchestrator.
Open the folder on GitHubat commit 3e83170
Compare with similar skills
API Compat Review 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 |
|---|---|---|---|---|---|---|
| API Compat Review this skilljpicklyk/task-orchestrator | 207 | — | ~636 | Automated safety check: Pass | MIT | |
| MCP Server Builderanthropics/skills | 180k | 64 repos | ~2.3k | Automated safety check: Pass | Apache-2.0 | |
| MCP Server BuildershareAI-lab/learn-claude-code | 78k | 5 repos | ~1.2k | Automated safety check: Pass | MIT | |
| MCP Integration for Pluginsanthropics/claude-plugins-official | 38k | 11 repos | ~3.1k | Automated safety check: Pass | Apache-2.0 | |
| Fastmcp Client CLIPrefectHQ/fastmcp | 28k | 1 repos | ~823 | Automated safety check: Pass | Apache-2.0 | |
| Crush Configurationcharmbracelet/crush | 29k | — | ~3.7k | Automated safety check: Pass | Custom licence |
Similar skills
- Official
MCP Server Builder
shareAI-lab/learn-claude-code
Walks through building MCP servers in Python or TypeScript that expose tools, resources and prompts to Claude, with templates, registration and testing.
- Official
MCP Integration for Plugins
anthropics/claude-plugins-official
Explains how to bundle Model Context Protocol servers in a Claude Code plugin, covering config files, stdio, SSE, HTTP and WebSocket server types, and authentication.
Fastmcp Client CLI
PrefectHQ/fastmcp
Query and invoke tools on MCP servers using fastmcp list and fastmcp call.
Crush Configuration
charmbracelet/crush
Explains how to configure the Crush coding agent with crushrc or crush.json, covering providers, models, LSPs, MCP servers, hooks, permissions and config precedence.
Context Mode Output Sandbox
mksglu/context-mode
Routes large command, file, API and browser output through context-mode tools so only the needed result enters the agent's context, instead of dumping it via Bash.
More from jpicklyk/task-orchestrator
All 28 skills in this repoTask Orchestrator Server Setup
jpicklyk/task-orchestrator
Walks through how to launch and reach the MCP Task Orchestrator server container: transport, REST API, port publishing, config mounts and config-sync.
Run Wave
jpicklyk/task-orchestrator
Resolves ready MCP work items into a run plan, shows it to you, then executes it through the Workflow tool or direct subagent dispatch, with post-run verification.
Adopt Project Scope Migration
jpicklyk/task-orchestrator
Migrates an existing unscoped Task Orchestrator database to the project-scoping convention in place, creating one project anchor root and re-parenting work trees under it after a mandatory dry run.
Bulk Task Completion
jpicklyk/task-orchestrator
Completes or cancels a whole feature subtree, a named list of items, or a batch of stale work items at once, previewing the impact and warning before force-completing anything active.
Task Orchestrator Item Creator
jpicklyk/task-orchestrator
Creates an MCP work item from conversation context, anchoring it under the right container, inferring type and priority and pre-filling the required notes.
Work Item Dependency Manager
jpicklyk/task-orchestrator
Views, creates, deletes and diagnoses BLOCKS, IS_BLOCKED_BY and RELATES_TO links between MCP work items, including why an item cannot start.
Related
Works with
Categories
Questions about API Compat Review
What does API Compat Review do?
Compatibility assessment for items with the needs-api-compat-review trait. API Compat Review is an agent skill from jpicklyk/task-orchestrator. Compatibility assessment for items with the needs-api-compat-review trait.
When should I use API Compat Review?
API Compat Review fits situations like: tasks that involve MCP servers.
How do I install API Compat Review in Claude Code?
Run `npx skills add jpicklyk/task-orchestrator --skill api-compat-review -a claude-code`. Or copy the skill folder (.claude/skills/api-compat-review in jpicklyk/task-orchestrator) into .claude/skills/api-compat-review in your project. Claude Code loads it when a task matches its description.
How do I install API Compat Review in Codex?
Run `npx skills add jpicklyk/task-orchestrator --skill api-compat-review -a codex`. Or copy the skill folder (.claude/skills/api-compat-review in jpicklyk/task-orchestrator) into .agents/skills/api-compat-review in your project. Codex loads it when a task matches its description.
Can I use API Compat Review in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add jpicklyk/task-orchestrator --skill api-compat-review -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/api-compat-review, .gemini/skills/api-compat-review, .github/skills/api-compat-review and .opencode/skills/api-compat-review in your project.
What does API Compat Review need to run?
SKILL.md names no scripts, command-line tools or credentials: API Compat Review is instructions for the agent only.
Does API Compat Review access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is API Compat Review safe to install?
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.
What licence does API Compat Review use?
API Compat Review is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does API Compat Review use?
About 636 tokens (SKILL.md is roughly 2.5k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to API Compat Review?
Skills that share tags, products or a category with API Compat Review: MCP Server Builder (anthropics/skills, 180k stars), MCP Server Builder (shareAI-lab/learn-claude-code, 78k stars), MCP Integration for Plugins (anthropics/claude-plugins-official, 38k stars) and Fastmcp Client CLI (PrefectHQ/fastmcp, 28k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains API Compat Review?
jpicklyk (a GitHub user) maintains it in jpicklyk/task-orchestrator, which has 207 GitHub stars. The repository holds 28 skills in this directory. The repository was last updated on October 8, 2026.
Source: jpicklyk/task-orchestrator on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.