Skill Token Overhead Review

Core Workflow

1. Identify the skill or bundle, trigger path, host, loaded files, tools/scripts used, repeated-run pattern, and target artifact.
2. Estimate overhead from added metadata, instructions, references, tool calls, turns, command output, MCP tools, or setup steps. Use exact token counts only when measured.
3. Compare overhead against output improvement from scenario or before/after evidence.
4. Flag broad triggers, duplicate guidance, stale references, unnecessary scripts, oversized command output, and host-specific setup leakage.
5. Recommend keep, trim, split, merge, lazy-load, compose through a skillset or orchestrator, move to references/scripts, isolate in a host adapter, or defer.
6. Preserve essential safety and validation instructions even when trimming.

Measurement Protocol