CtrlK
BlogDocsLog inGet started
Tessl Logo

agent-team-design

Use when designing a new multi-agent team, visible agents folder, role boundaries, handoff flow, PM Soul, Memory Curator, Policy Gate, or evaluation role. Use for agent-team repo creation even when the user only says they want a meta-agent or agent operating system.

72

Quality

88%

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

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.

A concise, well-structured procedural skill that respects the token budget and stays appropriately short for its scope. Its main weakness is actionability and validation: the steps name artifacts and conditions but stop short of executable, verifiable guidance for a consequential design task.

Suggestions

Add a concrete validation/checkpoint step (e.g. 'Verify each role maps to exactly one owner and every handoff has a named target before declaring the design done') so the workflow has an explicit success check.

Tighten 'Define the user job and target runtime' and 'Add team roles only when ... is useful' into more actionable guidance — e.g. name the minimal role set, the decision criteria as a checklist, or a concrete template for the output.

Optionally include a tiny example of the expected output shape (role list + handoff direction + owners) so the result is copy-paste ready rather than left to interpretation.

DimensionReasoningScore

Conciseness

Lean and efficient — a short numbered procedure with concrete file paths and a tight output spec; no padding, no explaining concepts Claude already knows. Every token earns its place.

3 / 3

Actionability

Gives concrete file paths (e.g. 'agents/10-single-agent-builder/agent.md', '.agentlas/company-blueprint.json') but the steps are directional ('Define the user job', 'Add team roles only when... is useful') rather than fully executable instructions, leaving key detail to judgment.

2 / 3

Workflow Clarity

Steps are clearly sequenced (1-5) but there are no validation checkpoints or feedback loops; given that multi-agent topology design is a consequential, easy-to-misjudge step, the missing 'how to verify the design' check keeps it at 2 rather than 3.

2 / 3

Progressive Disclosure

A short, well-organized skill under 50 lines with no external bundle files; the sections (Procedure, Output) are clearly structured and no nested references are needed, which the rubric allows to score 3 for simple skills.

3 / 3

Total

10

/

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.

A strong, specific description with explicit trigger guidance and clear niche demarcation. It names concrete artifacts and roles and provides multiple natural trigger phrases covering both direct and indirect user requests.

DimensionReasoningScore

Specificity

Lists multiple specific concrete targets — 'visible agents folder', 'role boundaries', 'handoff flow', 'PM Soul, Memory Curator, Policy Gate', and 'evaluation role' — naming concrete artifacts and roles rather than vague actions.

3 / 3

Completeness

Explicitly answers both 'what' (designing a multi-agent team with role boundaries, handoff flow, named roles) and 'when' via two explicit 'Use when...'/'Use for...' trigger clauses.

3 / 3

Trigger Term Quality

Covers natural user phrasings a person would actually say — 'designing a new multi-agent team', 'agent-team repo creation', 'meta-agent', 'agent operating system' — with good breadth of variations.

3 / 3

Distinctiveness Conflict Risk

The trigger domain — multi-agent team design, agent-team repos, meta-agent/agent OS — is a clear niche with distinct vocabulary unlikely to fire for unrelated 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.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
agentlas-ai/Agentlas-OS
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.