audit-activation

Installation
SKILL.md

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 subagent_type=. 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 ${CLAUDE_SKILL_DIR}/rules/activation-checks.md HIGH What to compute per agent
Classification ${CLAUDE_SKILL_DIR}/rules/activation-status.md HIGH fires / mis-triggered / niche / dead buckets
Output Format ${CLAUDE_SKILL_DIR}/references/output-format.md MEDIUM Report layout + the spawn-split summary

CRITICAL: Task Management is MANDATORY (CC 2.1.16)

Installs
7
GitHub Stars
212
First Seen
Jun 30, 2026
audit-activation — yonatangross/orchestkit