subagent-contract
Global contract for all specialist subagents — enforces role boundaries, scope discipline, and DONE/BLOCKED status signaling. Use when loading any agent that should operate as a bounded specialist following supervisor delegation patterns.
Install with Tessl CLI
npx tessl i github:Jamie-BitFlight/claude_skills --skill subagent-contract84
Does it follow best practices?
If you maintain this skill, you can automatically optimize it using the tessl CLI to improve its score:
npx tessl skill review --optimize ./path/to/skillValidation for skill structure
Discovery
75%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 description effectively communicates its specialized purpose for multi-agent orchestration with clear 'what' and 'when' clauses. However, it relies heavily on technical jargon that may not match natural user language, and the specific actions enforced could be more concrete. The distinctiveness is strong due to its narrow, well-defined scope.
Suggestions
Add more natural trigger terms users might say, such as 'agent rules', 'agent coordination', 'multi-agent', or 'agent handoff'
Make actions more concrete by specifying what 'enforces role boundaries' means in practice (e.g., 'prevents scope creep', 'validates task completion', 'manages agent handoffs')
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (specialist subagents, role boundaries, scope discipline) and some actions (enforces, signaling), but uses abstract concepts rather than concrete actions. 'Enforces role boundaries' and 'scope discipline' are somewhat vague compared to listing specific operations. | 2 / 3 |
Completeness | Clearly answers both what ('enforces role boundaries, scope discipline, and DONE/BLOCKED status signaling') and when ('Use when loading any agent that should operate as a bounded specialist following supervisor delegation patterns'). Has explicit 'Use when' clause with trigger guidance. | 3 / 3 |
Trigger Term Quality | Includes some relevant terms like 'subagents', 'specialist', 'supervisor delegation', 'DONE/BLOCKED status', but these are technical jargon. Missing natural user phrases - users might say 'agent rules', 'agent behavior', or 'multi-agent coordination' which aren't present. | 2 / 3 |
Distinctiveness Conflict Risk | Very specific niche targeting subagent contracts and delegation patterns. Terms like 'DONE/BLOCKED status signaling', 'bounded specialist', and 'supervisor delegation' create a distinct identity unlikely to conflict with other skills. | 3 / 3 |
Total | 10 / 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 well-structured contract skill that provides clear, actionable guidance for subagent behavior. Its strengths are the explicit status signaling protocol, quality checklists, and anti-pattern examples. The main weakness is moderate redundancy where concepts like 'no assumptions' and 'scope discipline' are restated across multiple sections, adding token overhead without new information.
Suggestions
Consolidate redundant concepts - 'no assumptions', 'scope discipline', and 'BLOCKED signaling' appear in multiple sections; merge into single authoritative statements with cross-references
Consider whether XML-style tags (<contract>, <rules>, etc.) add sufficient value to justify their token cost, or if markdown headers alone would suffice
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is reasonably efficient but includes some redundancy - the same concepts (no assumptions, scope discipline, BLOCKED signaling) are repeated across multiple sections. The XML-style tags add structure but also token overhead. | 2 / 3 |
Actionability | Provides concrete, specific guidance with exact status signal formats ('STATUS: DONE', 'STATUS: BLOCKED'), explicit checklists, and clear behavioral rules. The anti-patterns section gives specific examples of what not to do. | 3 / 3 |
Workflow Clarity | Clear workflow with explicit validation checkpoints via quality checklists before signaling DONE or BLOCKED. The supervisor protocol section provides clear sequence for receiving tasks and returning results with feedback loops. | 3 / 3 |
Progressive Disclosure | Excellent structure with clear overview reference to the workflow diagram for complete details, well-organized sections with semantic groupings, and appropriate use of collapsible-style sections via XML tags. Single-level reference to external documentation. | 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 | |
- 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.