CtrlK
BlogDocsLog inGet started
Tessl Logo

team-lead-reference

Provides model routing rules, validates delegation prerequisites, supplies cost tracking templates, defines dead-letter queue formats for Team Lead orchestration. Load when assigning tasks to agents, choosing model tiers, starting delegation session, running multi-agent workflow, delegating work, choosing which model to use, or assigning tasks.

77

Quality

96%

Does it follow best practices?

Impact

No eval scenarios have been run

SecuritybySnyk

Passed

No known issues

SKILL.md
Quality
Evals
Security

Quality

Content

92%

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-crafted orchestration reference skill that excels at conciseness through heavy use of tables and structured formats. The workflow is clearly sequenced with appropriate validation checkpoints and error recovery paths. The main weakness is that progressive disclosure relies on external files that aren't provided in the bundle, and the skill packs a lot of reference material (DLQ format, dispute protocol) that could potentially be split out.

DimensionReasoningScore

Conciseness

The content is highly efficient — uses tables extensively to compress information, avoids explaining concepts Claude already knows, and every section delivers actionable reference material without padding or unnecessary context.

3 / 3

Actionability

Provides concrete JSON envelope templates, specific checklists with numbered items, exact file paths for logging, precise scoring criteria with examples, and clear routing rules. The delegation envelope is copy-paste ready with field-level documentation.

3 / 3

Workflow Clarity

The delegation sequence is clearly numbered 1-7 with explicit steps. Status handling includes feedback loops (Blocked → upgrade/escalate, never re-dispatch unchanged; Needs context → provide info, re-dispatch). Pre-delegation policy checks serve as validation checkpoints before destructive delegation. The Deepen-Plan Protocol has clear decision criteria for when to skip vs. deepen.

3 / 3

Progressive Disclosure

References to external files like agent-registry.md, orchestration-protocols skill, session-checkpoints skill, and observability-logging skill are present and clearly signaled. However, no bundle files are provided to verify these references exist, and some content (like the Dead Letter Queue format and Dispute Protocol) could potentially be split into separate reference files to keep the main skill leaner.

2 / 3

Total

11

/

12

Passed

Description

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 strong skill description that clearly articulates specific capabilities (model routing, delegation validation, cost tracking, dead-letter queues) and provides explicit trigger guidance with a comprehensive 'Load when...' clause. The description is well-scoped to a distinct domain of multi-agent orchestration, making it easy to distinguish from other skills. It uses proper third-person voice throughout.

DimensionReasoningScore

Specificity

Lists multiple specific concrete actions: 'model routing rules', 'validates delegation prerequisites', 'supplies cost tracking templates', 'defines dead-letter queue formats'. These are distinct, concrete capabilities.

3 / 3

Completeness

Clearly answers both 'what' (model routing rules, delegation prerequisites, cost tracking templates, dead-letter queue formats) and 'when' with an explicit 'Load when...' clause listing seven trigger scenarios.

3 / 3

Trigger Term Quality

Includes strong natural trigger terms users would say: 'assigning tasks to agents', 'choosing model tiers', 'delegation', 'multi-agent workflow', 'choosing which model to use', 'delegating work'. Good coverage of natural variations.

3 / 3

Distinctiveness Conflict Risk

Targets a clear niche of multi-agent orchestration, model routing, and delegation workflows. The combination of 'Team Lead orchestration', 'dead-letter queue formats', and 'model tiers' is highly distinctive and unlikely to conflict with other skills.

3 / 3

Total

12

/

12

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.

Validation11 / 11 Passed

Validation for skill structure

No warnings or errors.

Repository
monkilabs/opencastle
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.