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.
Assessment of plugin skill and hook changes needed after MCP or config changes.
Install Plugin Impact Review
$ npx skills add jpicklyk/task-orchestrator --skill plugin-impact-review -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install jpicklyk/task-orchestrator plugin-impact-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/plugin-impact-review .claude/skills/plugin-impact-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 "plugin-impact-review" agent skill from https://github.com/jpicklyk/task-orchestrator/tree/main/.claude/skills/plugin-impact-review into .claude/skills/plugin-impact-review/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "plugin-impact-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/plugin-impact-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 plugin-impact-review -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install jpicklyk/task-orchestrator plugin-impact-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/plugin-impact-review .agents/skills/plugin-impact-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 "plugin-impact-review" agent skill from https://github.com/jpicklyk/task-orchestrator/tree/main/.claude/skills/plugin-impact-review into .agents/skills/plugin-impact-review/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "plugin-impact-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 plugin-impact-review -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install jpicklyk/task-orchestrator plugin-impact-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/plugin-impact-review .cursor/skills/plugin-impact-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 "plugin-impact-review" agent skill from https://github.com/jpicklyk/task-orchestrator/tree/main/.claude/skills/plugin-impact-review into .cursor/skills/plugin-impact-review/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "plugin-impact-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/plugin-impact-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 plugin-impact-review -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install jpicklyk/task-orchestrator plugin-impact-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/plugin-impact-review .gemini/skills/plugin-impact-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 "plugin-impact-review" agent skill from https://github.com/jpicklyk/task-orchestrator/tree/main/.claude/skills/plugin-impact-review into .gemini/skills/plugin-impact-review/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "plugin-impact-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 plugin-impact-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 plugin-impact-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/plugin-impact-review .github/skills/plugin-impact-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 "plugin-impact-review" agent skill from https://github.com/jpicklyk/task-orchestrator/tree/main/.claude/skills/plugin-impact-review into .github/skills/plugin-impact-review/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "plugin-impact-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 plugin-impact-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 plugin-impact-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/plugin-impact-review .opencode/skills/plugin-impact-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 "plugin-impact-review" agent skill from https://github.com/jpicklyk/task-orchestrator/tree/main/.claude/skills/plugin-impact-review into .opencode/skills/plugin-impact-review/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "plugin-impact-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
plugin-impact-review- GitHub stars
- 207
- Token cost
- ~685 tokens
- SKILL.md length
- 278 words
- Files
- 1
- Skills in repo
- 28
- Repo updated
- First seen
- Licence
- MIT
At a glance
Assessment of plugin skill and hook changes needed after MCP or config changes.
- Works in 5 steps: Skill Impact → Hook Impact → Config Format Documentation → …
- Tasks that involve MCP servers
- SKILL.md covers Step 1: Skill Impact, Step 2: Hook Impact, Step 3: Config Format… and Step 4: Orchestration Context…, plus 2 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Plugin Impact Review is an agent skill from jpicklyk/task-orchestrator. Assessment of plugin skill and hook changes needed after MCP or config changes. Evaluates skill references, hook context, config-format docs, and orchestration context references. Invoked via skillPointer when filling plugin-impact notes.
Its SKILL.md is about 690 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
- “/plugin-impact-review”
Workflow steps
5 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 b688ea0. 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
Plugin Impact Review loads about 685 tokens when it runs. Until then it costs about 65 tokens; SKILL.md has 278 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 b688ea0, republished under its MIT licence (© jpicklyk). 278 words, ~685 tokens.
Download SKILL.mdSave it as
.claude/skills/plugin-impact-review/SKILL.md (or your agent's skills folder).- name
- plugin-impact-review
- description
- Assessment of plugin skill and hook changes needed after MCP or config changes. Evaluates skill references, hook context, config-format docs, and orchestration context references. Invoked via skillPointer when filling plugin-impact notes.
- user-invocable
- false
Plugin Impact Review Framework
Evaluate which plugin components need updating after changes to MCP tools, config format, or response shapes.
Step 1: Skill Impact
Search all skill files for references to the changed behavior:
grep -r "<tool-name>\|<config-key>\|<changed-concept>" claude-plugins/task-orchestrator/skills/For each match:
- Does the skill reference the old behavior, field name, or response shape?
- Does the skill need updated instructions or examples?
- Are trigger phrases still accurate?
Step 2: Hook Impact
Search hook scripts for references:
grep -r "<tool-name>\|<changed-concept>" claude-plugins/task-orchestrator/hooks/For each match:
- Does the hook inject context that references the old behavior?
- Does the hook read tool input/output fields that changed?
- Does the hook matcher still target the correct tool name?
Step 3: Config Format Documentation
Check claude-plugins/task-orchestrator/skills/manage-schemas/references/config-format.md:
- YAML structure example reflects current format
- Field reference table has all current fields
- Descriptions match current behavior
Step 4: Orchestration Context References
Check the orchestration context for stale references:
-
hooks/orchestration-context.mjs— any references to changed tools, fields, or workflows in the injected core (both theworkflowandschemavariants) -
skills/orchestrate/SKILL.md— tier table, delegation table, and phase-owner dispatch rules
Step 5: Plugin Caching
- Are hook scripts changed? If yes,
/plugin marketplace remove+ re-add required (content cached) - Are skill files changed?
/reload-pluginssufficient (read at invocation) - Is the orchestration-context hook content changed? Needs a session restart (or the forced cache refresh in
claude-plugins/CLAUDE.md), not/reload-plugins; theorchestrateskill is read at invocation
Output
Compose the plugin-impact note listing specific files and sections that need changes. Note /mcp reconnect requirements.
Before asserting any skill/hook/doc file is missing, verify with a direct existence check
(Read the exact expected path, or an exact-path Glob) — skills live in BOTH
claude-plugins/task-orchestrator/skills/ and project-level .claude/skills/; checking
only one directory has produced a false "missing skill" finding before.
© 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/plugin-impact-review of jpicklyk/task-orchestrator.
Open the folder on GitHubat commit b688ea0
Compare with similar skills
Plugin Impact 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 |
|---|---|---|---|---|---|---|
| Plugin Impact Review this skilljpicklyk/task-orchestrator | 207 | — | ~685 | Automated safety check: Pass | MIT | |
| MCP Server Builderanthropics/skills | 180k | 62 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 | 37k | 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 Plugin Impact Review
What does Plugin Impact Review do?
Assessment of plugin skill and hook changes needed after MCP or config changes. Plugin Impact Review is an agent skill from jpicklyk/task-orchestrator. Assessment of plugin skill and hook changes needed after MCP or config changes.
When should I use Plugin Impact Review?
Plugin Impact Review fits situations like: tasks that involve MCP servers.
How do I install Plugin Impact Review in Claude Code?
Run `npx skills add jpicklyk/task-orchestrator --skill plugin-impact-review -a claude-code`. Or copy the skill folder (.claude/skills/plugin-impact-review in jpicklyk/task-orchestrator) into .claude/skills/plugin-impact-review in your project. Claude Code loads it when a task matches its description.
How do I install Plugin Impact Review in Codex?
Run `npx skills add jpicklyk/task-orchestrator --skill plugin-impact-review -a codex`. Or copy the skill folder (.claude/skills/plugin-impact-review in jpicklyk/task-orchestrator) into .agents/skills/plugin-impact-review in your project. Codex loads it when a task matches its description.
Can I use Plugin Impact 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 plugin-impact-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/plugin-impact-review, .gemini/skills/plugin-impact-review, .github/skills/plugin-impact-review and .opencode/skills/plugin-impact-review in your project.
What does Plugin Impact Review need to run?
SKILL.md names no scripts, command-line tools or credentials: Plugin Impact Review is instructions for the agent only.
Does Plugin Impact 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 Plugin Impact 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 Plugin Impact Review use?
Plugin Impact 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 Plugin Impact Review use?
About 685 tokens (SKILL.md is roughly 2.7k 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 Plugin Impact Review?
Skills that share tags, products or a category with Plugin Impact 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, 37k 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 Plugin Impact 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 6, 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.