CtrlK
BlogDocsLog inGet started
Tessl Logo

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.

67

Quality

80%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./plugins/orchestrator-discipline/skills/orchestrator-discipline/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

67%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A well-structured, concrete body with a clear workflow flowchart and a properly signaled reference file. The main weakness is redundancy between the overview and the Hook Behavior Reference section, which inflates token cost without adding clarity.

Suggestions

Consolidate the blocking/non-blocking explanation and the hook trigger lists so each appears once — either in 'What This Plugin Provides' or in 'Hook Behavior Reference', not both — to reduce redundancy (conciseness).

Move the full per-hook trigger specification tables (extension lists, command lists) into a dedicated reference file and keep SKILL.md as a concise overview pointing to it (progressive_disclosure).

Add an explicit validate→fix→retry feedback loop or checklist for the delegation workflow — e.g., what to do when a delegated agent's summary indicates scope change or failure — to strengthen workflow clarity beyond a single spot-check step.

DimensionReasoningScore

Conciseness

Mostly efficient and assumes competence, but the blocking/non-blocking distinction and the hook trigger conditions are restated across 'What This Plugin Provides' and 'Hook Behavior Reference', producing redundant content that could be tightened. Not a 4 because the duplication is more than minor; not a 2 because the body is dense and useful rather than padded with concepts Claude already knows.

3 / 5

Actionability

Provides concrete, executable specifications — explicit extension lists, exact diagnostic command lists, and a decision flowchart — with only minor gaps. Not a 5 because much of the body describes the plugin's behavior rather than giving copy-paste guidance, and the delegation steps reference another skill ('per agent-orchestration:delegate') rather than standing alone.

4 / 5

Workflow Clarity

The mermaid flowchart lays out a clear sequence with decision branches (Q1, Q2) and a 'Spot-check agent output' checkpoint, plus an explicit WRONG path. Not a 5 because it lacks a full validate→fix→retry feedback loop and checklist structure for the more complex delegation cases.

4 / 5

Progressive Disclosure

Clear sectioned overview with one well-signaled, one-level-deep reference (./references/investigation-escalation.md, verified present). Not a 5 because the detailed Hook Behavior Reference trigger lists are inlined in SKILL.md and could be split into a separate reference file.

4 / 5

Total

15

/

20

Passed

Description

92%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A strong, specific description that clearly states both the enforcement actions and the activation triggers, with concrete natural-language 'Use when' guidance. The only minor gap is a lack of synonyms or variants in the trigger terms.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — 'reading source files it will not edit', 'running diagnostic commands that waste context', 'rationalizing delegation bypasses', and 'Activates PreToolUse hooks that surface decision points' — giving comprehensive coverage of what the skill enforces.

5 / 5

Completeness

Explicitly answers both what ('Orchestrator context window discipline enforcement… Activates PreToolUse hooks…') and when ('Use when setting up orchestrator guardrails, reviewing delegation discipline, or diagnosing context window waste') with concrete trigger phrases.

5 / 5

Trigger Term Quality

The 'Use when' clause surfaces natural phrases a user would say ('orchestrator guardrails', 'delegation discipline', 'context window waste', 'multi-agent workflows'), but coverage stops short of comprehensive synonyms. Not a 5 because no synonyms/variants are offered, and not a 3 because the terms are clearly natural rather than jargon-only.

4 / 5

Distinctiveness Conflict Risk

Targets a clearly defined niche — orchestrator context-window discipline in multi-agent Claude Code workflows — with distinct triggers and minimal overlap risk with other skills.

5 / 5

Total

19

/

20

Passed

Validation

100%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
Jamie-BitFlight/claude_skills
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.