跳到正文
cccskills
免费在 GitHub 公开

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.

中文简介正在准备中。当前显示原文说明。

实测评分 未实测

查看安装方法

包含的文件(2)

  • SKILL.md2.6 KB
  • agents/openai.yaml268 B

SKILL.md(原文)

安装前可以查看交给 AI 代理的指令内容。

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.

评价

还没有评价。欢迎分享你的使用感受。

评论

无需登录即可发表。欢迎分享使用感受、提问,或说明在哪些环境下无法运行。

还没有评论。来写第一条吧。

提交后会立即公开。请勿填写邮箱、电话等个人信息。URL 最多 2 个。

0 / 1000 字

此表单受 reCAPTCHA 保护,适用 Google 的隐私权政策和服务条款。

同一仓库的技能

Inspect fired CCAM alerts and manage alert rules for token thresholds, event patterns, inactivity, and status duration. Use when acknowledging alerts, creating or editing a rule, checking cooldowns, or connecting alert rules to webhook targets.

中文简介正在准备中。当前显示原文说明。

hoangsonww/Claude-Code-Agent-Monitor11122026年10月24日 更新

Identify anomalous sessions using Agent Monitor data — cost outliers from the pricing engine, token anomalies (cache miss spikes, compaction baseline surges), unusual event type ratios (PreToolUse/PostToolUse gaps, APIError clusters), behavioral deviations from workflow intelligence (complexity score outliers, error propagation anomalies), and sessions with abnormal metadata (extreme turn_count, high thinking_blocks, zero turn_duration).

中文简介正在准备中。当前显示原文说明。

hoangsonww/Claude-Code-Agent-Monitor11122026年10月24日 更新

Produce a detailed report on APIError events from Agent Monitor data — counts over time, which sessions and models are affected, and the likely root cause (rate limits, overload/529, or context-window pressure) inferred from each event's summary and data payload. Use when API errors spike or when you need to explain why requests are failing.

中文简介正在准备中。当前显示原文说明。

hoangsonww/Claude-Code-Agent-Monitor11122026年10月24日 更新

benchmark

免费

Benchmark one session (or a small recent set) against the rolling average using Agent Monitor data — cost, total tokens, tool count, and workflow complexity score — and report where each metric lands as a percentile of the population. Tells you whether a session was normal, cheap, or an outlier. Use when judging whether a session was typical or out of band.

中文简介正在准备中。当前显示原文说明。

hoangsonww/Claude-Code-Agent-Monitor11122026年10月24日 更新

Define a spend budget for Claude Code and, optionally, create a cost alert rule that fires when usage crosses the limit, via POST /api/alerts/rules on the Agent Monitor dashboard. Reads current spend from /api/pricing/cost to size the budget sensibly and explains every rule field before writing. Use when setting a spend limit or wiring up a budget guardrail.

中文简介正在准备中。当前显示原文说明。

hoangsonww/Claude-Code-Agent-Monitor11122026年10月24日 更新

Analyze prompt-cache effectiveness for Claude Code usage from the Agent Monitor dashboard — cache hit rate (total_cache_read / (total_cache_read + total_input)), cache_write vs cache_read reuse, cache-read vs cache-write spend, and the sessions with the poorest reuse. Pulls token totals from /api/analytics, per-session detail from /api/sessions, and dollar splits from /api/pricing/cost. Use when diagnosing cache spend or deciding whether prompt caching is paying off.

中文简介正在准备中。当前显示原文说明。

hoangsonww/Claude-Code-Agent-Monitor11122026年10月24日 更新

查看 hoangsonww 的全部技能

报告此技能的问题