CtrlK
BlogDocsLog inGet started
Tessl Logo

mode-classification

Use before routing a /meta-agent request to choose single-agent-creator, team-builder, or agentlas-packager from the user's wording and available files.

75

Quality

92%

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

100%

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

The content is concise, actionable, and well-structured, with a clearly sequenced decision workflow, explicit fallback/clarify loops, and appropriately scoped references. It respects the token budget while giving Claude exactly what it needs to classify the mode.

DimensionReasoningScore

Conciseness

The body is lean and assumes Claude's competence, explaining only the non-obvious decision criteria without padding or restating concepts Claude already knows; every step earns its place.

3 / 3

Actionability

Concrete, specific decision guidance is given — count ownership boundaries, check produces/consumes synthesis need, apply the shape guard, and overlay ontology-backed mode — with explicit file paths (e.g. '.agentlas/contract-injection-map.json', 'modes/ontology-backed-agent.md'). For an instruction-only decision skill this is actionable and copy-ready.

3 / 3

Workflow Clarity

A clear Step 0–3 sequence is laid out with explicit checkpoints and feedback loops ('run the clarify question loop before generating', 'instead of guessing'), and ambiguity/shape guards catch errors early.

3 / 3

Progressive Disclosure

The skill is under 50 lines with well-organized sections (Procedure, Return, Reference) and a single one-level-deep reference ('docs/mode-classifier.md'), matching the simple-skill allowance for a top score.

3 / 3

Total

12

/

12

Passed

Description

85%

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 specific, complete, and well-scoped, clearly stating what it does and when to use it. Its only weakness is trigger-term quality: the wording is more technical than the natural phrases a user would actually say.

Suggestions

Add natural-language trigger variants to the description so it fires when users say things like 'make an agent', 'build a team of agents', or 'package this agent' rather than only on the internal '/meta-agent request' phrasing.

Soften the reliance on internal mode names in the trigger clause; lead with the user-facing intent (creating/packaging agents) and keep mode names as secondary detail.

DimensionReasoningScore

Specificity

Names the three concrete target modes ('single-agent-creator, team-builder, or agentlas-packager') and the concrete action ('routing a /meta-agent request to choose'), matching the anchor for multiple specific concrete actions.

3 / 3

Completeness

It explicitly answers both what ('choose single-agent-creator, team-builder, or agentlas-packager') and when ('Use before routing a /meta-agent request'), satisfying the anchor for clearly answering both with an explicit trigger.

3 / 3

Trigger Term Quality

The trigger ('Use before routing a /meta-agent request') leans on technical jargon and internal mode names rather than natural phrasings a user would say; relevant keywords are present but common variations are missing.

2 / 3

Distinctiveness Conflict Risk

The niche is narrow and specific to meta-agent mode routing among three named modes, making it unlikely to trigger for the wrong skill.

3 / 3

Total

11

/

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.