agentsclimarketplace

Delegation audit

Skill hoangsonww/Claude-Code-Agent-Monitor/plugins/ccam-workflows/skills/delegation-audit

Audit model delegation and subagent effectiveness for a session — which models handled which subagent types, per-type success rates and average durations, and wasted delegations (heavy models on trivial work or types that consistently fail) — using the Agent Monitor workflow intelligence API. Use when reviewing how a session delegated work across models and subagents.From its SKILL.md

Install
npx -y skills add hoangsonww/Claude-Code-Agent-Monitor --skill delegation-audit

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

SKILL.md

2.6 KB, 530 tokens by cl100k_base, as published. Nobody here has run it

Delegation Audit

Audit how a Claude Code session delegated work: model-to-subagent mapping and whether each delegation paid off.

Input

The user provides: $ARGUMENTS

A session ID. If empty, fetch GET /api/sessions?limit=1 and audit the most recent session, stating which one.

Data Sources

EndpointReturns
GET /api/workflows/{sessionId}The modelDelegation dataset (which models are delegated which subagent types) and the effectiveness dataset (per-type completion/success rate, avg duration, task success)
GET /api/agentsRaw subagent records (type, model, status, depth, parent) to corroborate counts and statuses

Report Sections

1. Delegation Matrix

From modelDelegation: a model × subagent-type table of how many agents of each type each model ran.

Modelexplorecode-reviewdebugger...Total

2. Effectiveness by Subagent Type

From effectiveness: per type, the success rate and average duration.

Subagent typeCountSuccess rateAvg durationVerdict
Mark types below ~70% success as low-yield.

3. Wasted Delegations

Flag, with evidence:

  • A heavy model (e.g. Opus) assigned to a simple/low-stakes subagent type that a cheaper model handled successfully elsewhere — candidate for rebalancing.
  • Subagent types with low success rates (effort spent, task not completed).
  • Duplicate delegations: the same type spawned repeatedly with poor success (retry churn).

4. Rebalancing Suggestions

Concrete model reassignments grounded in the matrix and effectiveness data. State the type, the model used, the success rate, and the suggested model — only where the data supports it.

Output

  • Markdown tables for the matrix and effectiveness.
  • Success rates as percentages; durations in human units (e.g. 1m 12s).
  • Use ▲/▼ when comparing a type's success rate against the session-wide average.
  • Cite only numbers returned by the API; do not infer success rates that the effectiveness dataset does not provide.
  • If the dashboard is unreachable, tell the user to start it with npm start from the repo root.

What ships with it

Read from the repository

Just SKILL.md. No reference files, no scripts.

Keep looking

Skills are one crate of 325,949. 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.