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.
81
77%
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 strong skill description that clearly defines a specific niche around orchestrator context window discipline. It excels at completeness with an explicit 'Use when' clause and lists concrete preventive actions. The main weakness is that trigger terms lean technical, which could limit matching when users describe the problem in more casual language.
Suggestions
Consider adding more natural-language trigger variations such as 'token waste', 'agent reading too many files', or 'sub-agent coordination problems' to improve discoverability for users who may not use the exact 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 specific 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 fairly technical. Users might more naturally say things like 'agent coordination', 'token usage', or 'sub-agent management' which are missing. | 2 / 3 |
Distinctiveness Conflict Risk | Highly distinctive niche targeting 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
70%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill is well-organized with strong workflow clarity and progressive disclosure, effectively communicating the orchestrator discipline pattern through a clear flowchart and structured hook reference. Its main weaknesses are moderate redundancy between the overview and reference sections, and a lack of concrete executable configuration examples showing how to actually set up or modify the hooks. The content assumes familiarity with the plugin system without showing how it's wired together.
Suggestions
Add a concrete example showing the hook configuration or installation (e.g., the actual PreToolUse hook code or config snippet) to improve actionability.
Consolidate the hook descriptions — the 'What This Plugin Provides' section and 'Hook Behavior Reference' section overlap significantly; consider making the first a brief summary with a pointer to the detailed reference below.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is mostly efficient but includes some redundancy — the hook behavior reference section repeats information already covered in the 'What This Plugin Provides' section. The SOURCE citations with specific session IDs and dates add noise. Some sections like 'When to Activate' are somewhat obvious. | 2 / 3 |
Actionability | The skill provides clear descriptions of what triggers each hook and the correct workflow via a mermaid diagram, but lacks concrete executable examples of how to configure or invoke these hooks. There are no code snippets showing hook implementation, configuration files, or example commands for setup. | 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 conditions and blocking vs non-blocking distinctions. The workflow includes feedback loops (scope changed → present to user). | 3 / 3 |
Progressive Disclosure | Content is well-structured with clear sections progressing from overview to detailed reference. The reference to investigation-escalation.md is a clean one-level-deep link. Rules are mentioned but appropriately not inlined. The hook behavior reference section serves as a useful quick-reference. | 3 / 3 |
Total | 10 / 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
11ec483
- 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.