CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

skill-router

The index of every pro-workflow skill and command, grouped by job, with when to reach for each and whether it is human-run or auto-triggered. Use when you are not sure which skill fits, want the full map, or ask "what can this do", "which skill for X", "list the workflow".

Quality

91%

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

85%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.

An exemplary instruction-only skill body: lean per-skill entries, a concrete routing procedure, honest maintenance guidance, and clean structure with a single well-signaled external reference. The only improvements are trimming the motivational opener and adding one worked routing example.

Suggestions

Add one worked routing example under 'How to use it' (e.g., job: 'commit these changes' -> matches Quality and review -> smart-commit), which would raise actionability to fully executable coverage of common cases.

Collapse the two-sentence opener into a single statement of purpose, e.g. '41 skills and 23 commands exceed anyone's working memory; this index is the map.'

State the update trigger as a concrete checklist condition (skill added/renamed/removed/fires differently) rather than a paragraph, so maintenance steps are scannable alongside the entries.

DimensionReasoningScore

Conciseness

One line per skill with [human]/[auto] tags and no padding or over-explanation, but the two-sentence motivational opener ('You cannot hold 41 skills and 23 commands in your head. This is the index so you do not have to.') could be trimmed to a single statement of purpose.

4 / 5

Actionability

The routing procedure is concrete and executable ('State the job in one line. Match it to a group below. If two skills look close, the when to reach clause is the tiebreaker') plus a clear maintenance rule, but there is no worked example of an actual job resolving to a specific skill.

4 / 5

Workflow Clarity

The routing sequence is stated as an unambiguous three-step procedure with an explicit tiebreaker rule; the operation is read-only, so no validation checkpoints are needed and the simple-skill exception applies.

5 / 5

Progressive Disclosure

Well-sectioned groups with easy navigation, a dedicated command-only section, and exactly one clearly-signaled one-level reference (rules/skill-conventions.mdc); the index itself is correctly inline because the router must load to function.

5 / 5

Total

18

/

20

Passed

Description

95%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 that fully covers what the index contains and when to reach for it, with unusually good quoted trigger phrases. Its only defect is second-person voice in the 'Use when' clause, which costs it a specificity point under the rubric's third-person rule.

DimensionReasoningScore

Specificity

Comprehensively states what the index provides ('grouped by job', 'when to reach for each', 'whether it is human-run or auto-triggered') but 'Use when you are not sure' is second person voice, which the rubric penalizes by reducing specificity by 1 from a base of 5.

4 / 5

Completeness

Explicitly answers both questions: what ('The index of every pro-workflow skill and command, grouped by job...') and when ('Use when you are not sure which skill fits...') with concrete trigger phrases.

5 / 5

Trigger Term Quality

Quotes the exact natural phrases a user would say ('what can this do', 'which skill for X', 'list the workflow', 'want the full map'), giving comprehensive synonym coverage for a routing request.

5 / 5

Distinctiveness Conflict Risk

Occupies a clear meta-level niche (skill selection and listing) whose triggers ('which skill fits', 'full map', 'list the workflow') do not overlap with the operational triggers of any individual skill.

5 / 5

Total

19

/

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

relative_links

Relative link issues: 1 suspicious

Warning

Total

15

/

16

Passed

Repository

rohitg00/pro-workflow

Path

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.