CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

router-first-architecture

Router-First Architecture

Quality

53%

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 ./.claude/skills/archive/router-first-architecture/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

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

The body is a lean, well-structured instruction skill with concrete commands and a clear router-first workflow plus fallback checkpoint. It would benefit from a touch more detail on the `command: null` fallback path.

DimensionReasoningScore

Conciseness

The body is efficient and assumes Claude's competence, with only minor padding such as the 'Source Sessions' notes; it does not explain concepts Claude already knows.

4 / 5

Actionability

It provides concrete, executable guidance such as `math-router route "<intent>"` and a real `coActivate` JSON snippet, with minor gaps around how to handle the `command: null` fallback in practice.

4 / 5

Workflow Clarity

The sequence is clear (use router first, fall back only if `command: null`) with a built-in checkpoint, and the two-layer architecture is well laid out; no destructive or batch validation is required here.

4 / 5

Progressive Disclosure

At under 50 lines with no external bundle files, the well-organized section headers (Pattern, DO, DON'T, Co-Activation, Two-Layer Architecture) satisfy the simple-skill exception for a top score.

5 / 5

Total

17

/

20

Passed

Description

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

The description is effectively just a title with no statement of capabilities or trigger conditions, so it fails all four dimensions. It needs concrete actions plus an explicit 'Use when...' clause.

Suggestions

Rewrite to state concrete actions, e.g. 'Routes user intent to exact CLI commands via domain routers before invoking individual tools.'

Add an explicit trigger clause: 'Use when a domain router exists for the requested operation or when selecting between multiple math/script tools.'

Include natural trigger terms users would actually say (e.g. 'math operations', 'pick the right script', 'route the request') instead of the jargon label 'Router-First Architecture'.

DimensionReasoningScore

Specificity

The description "Router-First Architecture" is a title only; it names no concrete actions or capabilities whatsoever, matching the 'entirely vague; no concrete actions' anchor.

1 / 5

Completeness

It answers neither what the skill does nor when to use it; both 'what' and 'when' are missing, matching the lowest anchor.

1 / 5

Trigger Term Quality

"Router" is internal technical jargon rather than natural user phrasing, and there are no natural keywords a user would say when needing this skill.

1 / 5

Distinctiveness Conflict Risk

"Router-First Architecture" is very broad and would overlap with any routing-related skill, though the 'router-first' qualifier gives it a faint niche just above entirely generic.

2 / 5

Total

5

/

20

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.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

parcadei/Continuous-Claude-v3

Path

.claude/skills/archive/router-first-architecture/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.