agentsclimarketplace
Sign in

Plugin impact review

Skill jpicklyk/task-orchestrator/.claude/skills/plugin-impact-review

Assessment of plugin skill and hook changes needed after MCP or config changes. Evaluates skill references, hook context, config-format docs, and output style references. Invoked via skillPointer when filling plugin-impact notes.From its SKILL.md

Install
npx -y skills add jpicklyk/task-orchestrator --skill plugin-impact-review

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

SKILL.md

2.4 KB, as published. Nobody here has run it

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: Output Style References

Check output styles for stale references:

  • workflow-orchestrator.md — any references to changed tools, fields, or workflows
  • Zone 1 (shared core) vs Zone 2/3 (extensions) — changes in Zone 1 must be synced to workflow-analyst.md

Step 5: Plugin Caching

  • Are hook scripts changed? If yes, /plugin marketplace remove + re-add required (content cached)
  • Are skill files changed? /reload-plugins sufficient (read at invocation)
  • Are output styles changed? /reload-plugins sufficient

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.

Keep looking

Skills are one crate of 626,474. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.