From marketplace-dev
Remove an agent from the system — deletes the agent file, cleans up all registry entries, removes cross-references, and updates documentation. Use when the user says "remove the X agent", "delete X-review", "retire the X role", or "we no longer need X". Handles both team agents and review agents. Always confirms before deleting.
How this skill is triggered — by the user, by Claude, or both
Slash command
/marketplace-dev:agent-remove <agent-name> [--plugin <dir>] [--dry]<agent-name> [--plugin <dir>] [--dry]This skill is limited to the following tools:
The summary Claude sees in its skill listing — used to decide when to auto-load this skill
Role: implementation. This skill removes an agent and all its references
Role: implementation. This skill removes an agent and all its references from the system — it does not modify agent behavior or content.
You have been invoked with the /agent-remove skill. Fully remove a named
agent and update all required documentation.
Model tier:) and
team agents (declare persona sections) require different cleanup paths.Arguments: $ARGUMENTS
Required: agent name ($0) — the filename stem without .md
(e.g., js-fp-review, security-engineer)
Optional:
--plugin <dir>: target plugin directory. Resolved as: this flag if given;
else single plugins/*/; else cwd ancestor with .claude-plugin/plugin.json;
else ask. Stored as $PLUGIN.--dry: Show what would be removed without making changesDetermine $PLUGIN using the convention above. Read
$PLUGIN/.claude-plugin/plugin.json and extract name as $NAME.
Verify $PLUGIN/agents/<name>.md exists. If not, list all agent files
and report that the named agent was not found.
Read $PLUGIN/agents/<name>.md:
Model tier: → review agentDisplay a confirmation prompt listing every action that will be taken:
Remove agent: <name> (<type>) from $PLUGIN
Files to delete:
- $PLUGIN/agents/<name>.md
[review agents only — if eval fixtures exist at repo root]
- evals/$NAME/fixtures/<name>-* (if any)
- evals/$NAME/expected/<name>-* (if any)
Registry entries to remove:
- $PLUGIN/knowledge/agent-registry.md: <table row> (if file exists)
- $PLUGIN/CLAUDE.md: Quick Reference list entry (if section exists)
[team agents only — if plugin maintains team-structure docs]
- $PLUGIN/docs/team-structure.md: <diagram node and edges> (if file exists)
Documentation to update:
- $PLUGIN/docs/agent_info.md: remove table row (if file exists)
[team agents only]
- $PLUGIN/agents/orchestrator.md: Tier guidance bullet (if listed)
- Other agent files in $PLUGIN/agents/ referencing <name>
Proceed? (yes to continue)
If --dry was passed, display the plan and stop without waiting for
confirmation.
git rm $PLUGIN/agents/<name>.md
If not in a git repository, use rm.
Search for and remove matching eval fixtures and expected files at the repo
root under evals/$NAME/:
ls evals/$NAME/fixtures/ | grep <name>
ls evals/$NAME/expected/ | grep <name>
Remove each matching file with git rm (or rm if not in git). If the
evals/$NAME/ directory does not exist, skip this step silently.
If $PLUGIN/knowledge/agent-registry.md exists, remove the agent's row
from the appropriate table (Team Agents or Review Agents). If the file
does not exist, skip this step.
If $PLUGIN/CLAUDE.md exists:
If the file does not exist, skip this step.
If $PLUGIN/agents/orchestrator.md exists:
If the file does not exist, skip this step.
Search for references to the removed agent:
grep -r "<name>" $PLUGIN/agents/ --include="*.md" -l
For each file found, remove or update:
If $PLUGIN/docs/agent_info.md exists:
If the file does not exist, skip this step.
If $PLUGIN/docs/team-structure.md exists, remove the agent node and all
its edges from any Mermaid diagrams in that file. If the file does not
exist, skip this step.
Review all modified documentation files for accuracy and consistency before reporting completion. Specifically check:
Agent removed: <name> (<type>) from $PLUGIN
Deleted:
- $PLUGIN/agents/<name>.md
[+ eval files if any]
Updated:
- $PLUGIN/knowledge/agent-registry.md [or: skipped — file not found]
- $PLUGIN/CLAUDE.md [or: skipped — file not found]
[+ orchestrator.md, team-structure.md, cross-references as applicable]
Documentation is consistent.
npx claudepluginhub p/bdfinst-marketplace-dev-plugins-marketplace-devGuides completion of development work by verifying tests, detecting environment, and presenting structured options for merge, PR, or cleanup.
Enforces test-driven development: write failing test first, then minimal code to pass. Use when implementing features or bugfixes.
Guides creation and editing of skills using test-driven development with pressure scenarios and subagents to verify agent compliance.