Agent skill · data analytics · yonatangross
audit-activation
Audits sub-agent activation from telemetry: attempted, started, completed, unattributed spawns, and zero-start agents. Use when agents feel under-used or before pruning the catalog.
Why this skill is useful
Adds a script for auditing agent activation that computes the generic-vs-specialist spawn split and identifies dormant agents, which the AI wouldn't reliably generate on its own.
What it needs
Requires bash installed locally. About 5k tokens when loaded. Last updated 2026-08-06. 215 stars on the source repository.
What this skill does
audit-activation Reports whether OrchestKit's specialized sub-agents are actually being activated, from real spawn telemetry — not vibes. Scope is agent activation, not skill quality. It answers: "Do my specialized agents get spawned, or does the model default to generic Explore/general-purpose?" Read-only — it never edits agents. Why this exists: a 2026-06 audit found only ~14% of agent spawns hit the 36-agent catalog vs ~74% generic, with 17/36 agents dormant — and that agents fire ~1:1 with how often a high-traffic skill names them via subagenttype=. Description rewrites ("use proactively") were A/B-tested and gave Δ0, so this skill measures wiring + usage, not description prose. See docs/feat--activation-audit/. Quick Reference Category File Impact When to Use ---------- ------ -------- ------------- Activation Checks rules/activation-checks.md HIGH What to compute per agent Classification rules/activation-status.md HIGH fires / mis-triggered / niche / dead buckets Output Format references/output-format.md MEDIUM Report layout + the spawn-split summary CRITICAL: Task Management is MANDATORY (CC 2.1.16) Workflow 1. Run the script FIRST — every audit starts by running (or, when execution is impossible, explicitly referencing) the deterministic collector: It resolves the catalog beside its source or installed script, while every consumer telemetry root is explicit. It reports attempts, starts, and stop-feed completions separately. Never eyeball JSONL by hand when the script exists. 2. Inventory — let the script resolve its own source or installed agents/ catalog. Do not point it at a consumer project's agent directory. 3. Read telemetry — .claude/logs/subagent-spawns.jsonl carries pretool intent and start events. Triangulate it with the restored global ~/.claude/analytics/agent-usage.jsonl stop feed when available. The streams have no stable common event ID, so never add them together or infer unique spawns. 4. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills yonatangross/audit-activation