CtrlK
BlogDocsLog inGet started
Tessl Logo

team-builder

Interactive agent picker for composing and dispatching parallel teams

58

Quality

67%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No known issues

Fix and improve this skill with Tessl

tessl review fix ./skills/team-builder/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

77%

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

The skill is highly actionable with a well-sequenced, validated workflow, but it is monolithic and repeats the layout-parsing logic across sections. Splitting the parsing rules and worked example into reference files and de-duplicating would improve token efficiency and structure.

Suggestions

De-duplicate the flat/subdirectory layout-parsing rules by defining them once and referencing that section, instead of restating them in both Prerequisites and Step 1.

Move the detailed layout-parsing algorithm and the full worked example into separate reference files (e.g. references/LAYOUTS.md) to keep SKILL.md a lean overview.

Trim the Examples section to a short illustrative excerpt rather than reproducing the full menu output.

DimensionReasoningScore

Conciseness

The body is mostly lean and assumes Claude's competence, but the flat/subdirectory layout-parsing rules are restated in both Prerequisites and Step 1, and the Examples section repeats menu content already shown.

2 / 3

Actionability

It gives exact glob patterns, the `claude agents` command, concrete Agent tool invocation parameters, menu templates, and selection-parsing rules that are effectively copy-paste ready.

3 / 3

Workflow Clarity

A clear 5-step sequence (Discover, Present Menu, Handle Selection, Spawn, Synthesize) with explicit checkpoints for no-agents, over-5 selection, and per-agent failure with inline continuation.

3 / 3

Progressive Disclosure

It is a single monolithic file with no external references at all; the layout-parsing logic and full worked example could live in separate reference files rather than all inline.

2 / 3

Total

10

/

12

Passed

Description

57%

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

The description is concise and distinguishes a clear niche, but it lacks explicit "Use when" trigger guidance and its actions are somewhat abstract. Adding a trigger clause and more concrete action verbs would lift it.

Suggestions

Add an explicit 'Use when...' clause naming triggering situations, e.g. 'Use when you want to pick which agents run a task or compose an ad-hoc team from multiple domains.'

Replace abstract verbs with concrete operations, e.g. 'Browse available agents, pick a subset, and dispatch them in parallel on a shared task.'

Include common trigger term variations users would say: 'agents', 'subagents', 'agent team', 'multiple agents'.

DimensionReasoningScore

Specificity

"composing and dispatching parallel teams" names the domain and two actions, but they are abstract verbs rather than concrete verb-noun operations like extracting text or filling forms.

2 / 3

Completeness

It states what the skill does (compose and dispatch parallel teams) but has no "Use when..." trigger clause, which caps completeness at 2 per the guidelines.

2 / 3

Trigger Term Quality

"agent", "team", "parallel teams" are relevant natural terms, but common variations such as "subagents", "multiple agents", or "agent team" are absent.

2 / 3

Distinctiveness Conflict Risk

"Interactive agent picker for composing and dispatching parallel teams" carves a clear niche around team composition that is unlikely to trigger for unrelated skills.

3 / 3

Total

9

/

12

Passed

Validation

93%

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

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

metadata_version

'metadata.version' is missing

Warning

Total

15

/

16

Passed

Repository
affaan-m/ECC
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.