CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

plugin-router

Analyze broad, mixed, or unclear Plugin Factory follow-up requests and select the correct plugin lane. Use when plugin intent lacks a clear lane owner.

Quality

69%

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/plugin-factory/fixtures/budget-archive/2026-04-21/deferred-store/skills/team_automation/plugin-router/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

57%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 well-organized and token-efficient, with clear scope boundaries and failure handling. Its central weakness is that the detailed routing protocol it delegates to references/workflow.md is not actually present in the bundle, leaving both actionability and workflow execution dependent on a missing file.

Suggestions

Ship references/workflow.md (and the other referenced bundle files) with the skill, or inline the core routing protocol so the skill is self-contained.

Include one complete example handoff object with populated field values so the output contract is copy-paste concrete.

Merge the overlapping ownership restatements in 'Execution Boundaries' into a single boundary statement to trim redundancy.

DimensionReasoningScore

Conciseness

The body is lean and assumes Claude's competence (e.g., 'Route first, execute second.', 'redact secrets and sensitive data by default') with no padding or explanation of known concepts; only minor trimming is possible in the ownership restatements across 'Execution Boundaries'.

4 / 5

Actionability

Concrete elements exist (handoff object field list, example route mappings like '"Install this plugin from GitHub and verify visibility." -> route to `[[plugin-installer]]`', and a validation command), but the core routing protocol is delegated to references/workflow.md, which is missing from the bundle, leaving key executable detail absent.

3 / 5

Workflow Clarity

A sequence is implied (route -> validate -> hand off with blocked_by on ambiguity) and validation with fail-fast is specified, but the actual multi-step routing workflow lives in the missing references/workflow.md, so steps are present only in outline with substantial gaps.

3 / 5

Progressive Disclosure

The SKILL.md is a short, well-sectioned overview with one-level-deep references clearly signaled by 'Read when:' conditions; however, all four referenced bundle files (workflow.md, contract.yaml, evals.yaml, task-profile.json) are absent from the actual bundle, so navigation dead-ends and keeps this below a 5.

4 / 5

Total

14

/

20

Passed

Description

71%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 cleanly answers both what the skill does and when to use it, with an explicit 'Use when' trigger clause. Its main weakness is trigger-term breadth: it relies on narrow internal jargon ('lane owner', 'Plugin Factory follow-up') and misses natural synonyms a user might say.

Suggestions

Add natural trigger variations such as 'route', 'dispatch', 'triage', or 'pick the right plugin skill' to widen keyword coverage.

Note the relationship to the canonical front-door router (e.g., 'Use after plugin-factory-router when a follow-up still lacks a clear lane owner') to reduce overlap risk with the root routing skill.

DimensionReasoningScore

Specificity

The description names the domain ('Plugin Factory follow-up requests') and two concrete actions ('Analyze... requests and select the correct plugin lane'), matching the anchor for 1-2 concrete actions but not comprehensive coverage.

3 / 5

Completeness

Both what ('Analyze broad, mixed, or unclear Plugin Factory follow-up requests and select the correct plugin lane') and when ('Use when plugin intent lacks a clear lane owner') are explicitly stated with a concrete trigger phrase.

5 / 5

Trigger Term Quality

Relevant keywords like 'Plugin Factory', 'follow-up requests', 'plugin intent', and 'lane' are present, but common natural variations users would say ('route', 'dispatch', 'triage', 'which plugin skill') are missing.

3 / 5

Distinctiveness Conflict Risk

The Plugin Factory lane-routing niche is distinct, with only minor overlap risk against the canonical front-door router skill it defers to; a broad plugin request could plausibly match both.

4 / 5

Total

15

/

20

Passed

Validation

81%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 13 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

metadata_version

'metadata.version' is missing

Warning

relative_links

Relative link issues: 1 missing, 1 suspicious

Warning

referenced_paths_exist

Referenced path issues: 6 missing

Warning

Total

13

/

16

Passed

Repository

jscraik/Agent-Skills

Path

Plugins/plugin-factory/fixtures/budget-archive/2026-04-21/deferred-store/skills/team_automation/plugin-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.