orchestrator-discipline
Orchestrator context window discipline enforcement. Prevents the orchestrator from reading source files it will not edit, running diagnostic commands that waste context, and rationalizing delegation bypasses. Use when setting up orchestrator guardrails, reviewing delegation discipline, or diagnosing context window waste in multi-agent workflows. Activates PreToolUse hooks that surface decision points before source file reads and diagnostic command execution.
93
Quality
92%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Passed
No known issues
Quality
Discovery
100%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This is a well-crafted skill description that excels across all dimensions. It provides specific concrete actions, includes domain-appropriate trigger terms, explicitly states both what the skill does and when to use it, and occupies a clear niche that won't conflict with other skills. The technical terminology is appropriate for the target audience of multi-agent workflow practitioners.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'prevents the orchestrator from reading source files it will not edit', 'running diagnostic commands that waste context', 'rationalizing delegation bypasses', and 'Activates PreToolUse hooks that surface decision points'. | 3 / 3 |
Completeness | Clearly answers both what (prevents orchestrator from reading unneeded files, running wasteful commands, bypassing delegation) AND when ('Use when setting up orchestrator guardrails, reviewing delegation discipline, or diagnosing context window waste in multi-agent workflows'). | 3 / 3 |
Trigger Term Quality | Includes natural keywords users would say: 'orchestrator', 'context window', 'delegation', 'multi-agent workflows', 'guardrails', 'source file reads', 'diagnostic commands'. These are terms practitioners in this domain would naturally use. | 3 / 3 |
Distinctiveness Conflict Risk | Highly specific niche targeting orchestrator context window discipline with distinct triggers like 'PreToolUse hooks', 'delegation bypasses', and 'multi-agent workflows'. Unlikely to conflict with general coding or document skills. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
85%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a strong skill with excellent actionability and workflow clarity. The hook behavior reference provides precise, copy-paste-ready trigger patterns. Minor verbosity in explaining blocking vs non-blocking behavior multiple times and the SOURCE citations could be moved to a changelog or removed.
Suggestions
Remove redundant explanations of blocking vs non-blocking behavior - state once in the overview, then just mark each hook with (blocking) or (non-blocking)
Move the SOURCE citation (session e3280e97) to a separate changelog or remove - it's implementation history, not operational guidance
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Content is mostly efficient but includes some redundancy (e.g., repeating 'blocking' vs 'non-blocking' explanations, the mermaid diagram duplicates text explanations). The hook behavior reference section could be tightened. | 2 / 3 |
Actionability | Provides concrete trigger patterns, specific file extensions, exact command patterns that fire hooks, and clear behavioral outcomes (exit code 2, additionalContext injection). The mermaid workflow diagram gives executable decision logic. | 3 / 3 |
Workflow Clarity | Clear multi-step workflow with explicit decision points in the mermaid diagram. The 'WRONG' path explicitly shows the anti-pattern. Hook trigger conditions are precisely specified with validation built into the blocking gate (exit 2). | 3 / 3 |
Progressive Disclosure | Well-structured with clear sections (What This Plugin Provides, When to Activate, Correct Workflow, Hook Behavior Reference). References external file for detailed anti-pattern analysis. One-level-deep reference to rules/CLAUDE.md and references/investigation-escalation.md. | 3 / 3 |
Total | 11 / 12 Passed |
Validation
90%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 10 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 10 / 11 Passed | |
- Repository
- Jamie-BitFlight/claude_skills
- Commit
fd243f9
- Reviewed
Table of Contents
Is this your skill?
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.