CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

skill-router

Use when the user is unsure which skill to use or where to start. Interviews the user with targeted questions and recommends the best skill(s) from the installed library for their goal.

Quality

79%

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

Fix and improve this skill with Tessl

tessl review fix ./plugins/AI-Agents-Safe-Coding-Skills/skills/skill-router/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

71%Weight 40%Scale 1-5

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

Highly actionable content with a clear interview workflow, exact output templates, and a comprehensive routing table. The main costs are token efficiency (repeated instructions and the inlined lookup table) rather than clarity or executability.

Suggestions

Move the ~90-line 'Skill Routing Reference' table into a single one-level-deep reference file (e.g. references/routing-table.md) and keep a short pointer in SKILL.md, preserving lean overview content.

Remove the duplicated prompt-offer instruction — it appears both in Step 4 and again in Constraints ('After recommending, always offer to write a ready-made prompt for them'); state it once.

Trim the redundant warm-opener guidance ('Respond warmly') and rely on the example interaction alone to demonstrate tone, cutting tokens without losing clarity.

DimensionReasoningScore

Conciseness

The body is mostly efficient, but includes tightening opportunities: Step 4's prompt-offer is restated verbatim in Constraints ('After recommending, always offer to write a ready-made prompt'), the example opener and the example interaction partially duplicate the step instructions, and 'Respond warmly' is padding Claude does not need. This matches 'mostly efficient but could be tightened' rather than anchor 4's minor-trimming profile.

3 / 5

Actionability

Fully executable instruction guidance: enumerated interview questions with exact option lists, a copy-paste-ready recommendation output template with exact '@invoke' syntax, a worked example interaction, a category-to-skill lookup table, and default fallbacks for ambiguous cases. This covers the common cases with no significant gaps.

5 / 5

Workflow Clarity

A clear 4-step sequence (acknowledge → funnel questions → recommend → offer prompt) with a skip-condition guardrail ('If an earlier answer makes a later question irrelevant, skip it'). No validation checkpoints exist, but the operation is conversational and non-destructive, making this a minor gap — anchor 4 rather than 5, since explicit error-recovery checkpoints are absent.

4 / 5

Progressive Disclosure

The body is well-sectioned, but the ~90-line 'Skill Routing Reference' lookup table is inlined in SKILL.md — content that would fit a one-level-deep reference file (e.g. references/routing-table.md) to keep the overview lean. With no bundle files provided and bulk lookup data inline, it matches anchor 3's 'content that should be separate is inline' rather than anchor 4's appropriately-placed content.

3 / 5

Total

15

/

20

Passed

Description

78%Weight 40%Scale 1-5

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 description: explicit what-and-when structure with natural trigger phrases and a clearly distinct routing niche. The only gaps are slightly thin action detail and a few missing natural trigger variations.

DimensionReasoningScore

Specificity

Names two concrete actions — 'Interviews the user with targeted questions' and 'recommends the best skill(s) from the installed library' — which matches the anchor for 1-2 concrete actions without comprehensive coverage; it does not list several actions, so it falls short of anchor 4.

3 / 5

Completeness

It explicitly answers both what ('Interviews the user with targeted questions and recommends the best skill(s)...') and when ('Use when the user is unsure which skill to use or where to start') with concrete trigger phrases, matching the top anchor; the when-clause is fully explicit, so anchor 4's 'could be more explicit' does not apply.

5 / 5

Trigger Term Quality

'unsure which skill to use' and 'where to start' are natural phrases users would say, giving good keyword coverage, but common variations like 'which skill should I use' or 'don't know where to begin' are missing, so it does not reach comprehensive synonym coverage of anchor 5.

4 / 5

Distinctiveness Conflict Risk

The skill-routing niche is mostly distinct — uncertainty about skill choice would not trigger a PDF or debugging skill — but 'where to start' is broad enough to overlap with general planning/brainstorming skills for vague goals, leaving minor overlap risk rather than the minimal risk of anchor 5.

4 / 5

Total

16

/

20

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.

Validation — 15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository

administrakt0r/AI-Agents-Safe-Coding-Skills

Path

plugins/AI-Agents-Safe-Coding-Skills/skills/skill-router/SKILL.md

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.