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.
78
73%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./plugins/orchestrator-discipline/skills/orchestrator-discipline/SKILL.mdQuality
Discovery
85%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 description that clearly defines a specific niche (orchestrator context window discipline) with concrete actions and explicit 'Use when' triggers. Its main weakness is that the trigger terms lean toward technical jargon that may not match how users naturally phrase their needs, though this is somewhat mitigated by the specialized nature of the skill's audience.
Suggestions
Add more natural-language trigger variations such as 'agent reading too many files', 'subagent not being used enough', or 'orchestrator doing too much work itself' to improve discoverability for users who may not use the precise technical terminology.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: prevents reading unedited source files, blocks wasteful diagnostic commands, prevents delegation bypass rationalizations, and activates PreToolUse hooks for decision points. These are clearly defined, actionable capabilities. | 3 / 3 |
Completeness | Clearly answers both what ('Prevents the orchestrator from reading source files it will not edit, running diagnostic commands...') and when ('Use when setting up orchestrator guardrails, reviewing delegation discipline, or diagnosing context window waste in multi-agent workflows'). The explicit 'Use when' clause with multiple trigger scenarios is present. | 3 / 3 |
Trigger Term Quality | Includes some relevant terms like 'orchestrator', 'context window', 'delegation', 'multi-agent workflows', and 'guardrails', but these are somewhat technical/jargon-heavy. A user might more naturally say 'agent is reading too many files' or 'subagent not being used' rather than 'context window discipline enforcement'. | 2 / 3 |
Distinctiveness Conflict Risk | Highly distinctive niche focused specifically on orchestrator context window discipline with PreToolUse hooks. The combination of orchestrator guardrails, delegation discipline, and context window waste is very specific and unlikely to conflict with other skills. | 3 / 3 |
Total | 11 / 12 Passed |
Implementation
62%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill provides a well-structured overview of orchestrator discipline enforcement with clear workflow diagrams and specific trigger patterns. Its main strengths are workflow clarity and the explicit blocking/non-blocking distinction for hooks. Weaknesses include some redundancy between sections, lack of executable configuration examples, and heavy inline detail that could benefit from better progressive disclosure into reference files.
Suggestions
Add executable configuration examples showing how to install/activate the hooks (e.g., the actual hook registration code or config file content)
Consolidate the hook trigger/non-trigger details into a separate reference file (e.g., HOOK_REFERENCE.md) and keep only summaries in the main SKILL.md
Remove the duplicated hook descriptions — the 'What This Plugin Provides' section and 'Hook Behavior Reference' section cover overlapping ground
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is reasonably efficient but includes some redundancy — the hook behavior reference section repeats information already covered in the 'What This Plugin Provides' section. The SOURCE citations and some explanatory text could be tightened. However, it largely avoids explaining concepts Claude already knows. | 2 / 3 |
Actionability | The skill provides concrete trigger patterns and a clear mermaid workflow diagram, but lacks executable code examples for setup, configuration, or hook implementation. The hook descriptions tell what happens but don't show how to configure or install them. The trigger patterns are specific but presented descriptively rather than as executable/copy-paste configurations. | 2 / 3 |
Workflow Clarity | The mermaid flowchart clearly sequences the correct orchestrator workflow with decision points, and explicitly marks the wrong path. The hook behavior reference provides clear trigger/non-trigger distinctions. The blocking vs non-blocking distinction is well-documented with explicit consequences (exit code 2). The workflow includes feedback loops (scope changed → present to user). | 3 / 3 |
Progressive Disclosure | There is one reference to an external file (investigation-escalation.md) and mention of rules/CLAUDE.md, but no bundle files were provided to verify these exist. The content is somewhat monolithic — the detailed hook trigger patterns could be split into a reference file, with the main SKILL.md providing just the overview. The structure is decent but the inline detail is heavy for a top-level skill file. | 2 / 3 |
Total | 9 / 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
b9f32ec
- 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.