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

62%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

—

The risk profile of this skill

Fix and improve this skill with Tessl

tessl review fix ./Plugins/plugin-factory/skills/team_automation/plugin-router/SKILL.md

Quality

Content

50%Scale 1-3

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

This skill is a routing helper that clearly defines its boundaries, failure modes, and anti-patterns, which is valuable. However, it delegates its core workflow entirely to an external reference without providing any inline routing logic or decision tree, making the body alone insufficient for execution. The output schema lists fields but lacks a concrete example object, reducing actionability.

Suggestions

Add a concrete JSON example of the routing handoff object with all fields populated, so Claude can produce the correct output shape without consulting references.

Include at least a summary decision tree or routing table inline (e.g., intent keyword -> lane mapping) rather than deferring the entire workflow to references/workflow.md.

Consolidate the duplicate reference listings — the 'Read when' section and the 'References' section at the bottom overlap; pick one approach and remove the other.

Dimension	Reasoning	Score
Conciseness	The skill is moderately efficient but includes some unnecessary sections and verbose explanations. The 'Philosophy' section, 'When to Use' vs 'When not to use' overlap, and the 'Gotchas' section contain some redundancy. However, it doesn't over-explain basic concepts and stays relatively focused on routing-specific guidance.	2 / 3
Actionability	The skill provides some concrete guidance (examples of routing, output schema fields, validation command) but lacks executable code or a complete handoff object example. The output format lists field names without showing a concrete JSON example, and the core workflow is deferred entirely to 'references/workflow.md' without any inline detail.	2 / 3
Workflow Clarity	The workflow is essentially 'see references/workflow.md' with no inline steps. While failure modes and anti-patterns are well-documented, the actual routing decision process is absent from the skill body. The validation step is present but the core multi-step routing protocol is entirely delegated, leaving the skill body without a clear sequence.	2 / 3
Progressive Disclosure	References are listed and some are well-signaled with context ('Read when:' section is good), but bundle files were not provided so we cannot verify the references exist. The skill delegates its core workflow entirely to a reference file, which means the body alone is insufficient. The references section at the bottom is a flat list without context, duplicating some of the earlier 'Read when' links.	2 / 3
	Total	8 / 12 Passed

Description

75%Scale 1-3

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 well-structured with both a 'what' and 'when' clause, and it occupies a distinct niche as a routing/triage skill for ambiguous plugin requests. However, it could be more specific about the concrete actions it performs beyond 'analyze and select,' and the trigger terms are somewhat jargon-heavy rather than reflecting natural user language.

Suggestions

Add more specific concrete actions, e.g., 'Classifies ambiguous requests, disambiguates overlapping plugin intents, and routes to the appropriate lane (create, edit, debug, etc.)'

Include more natural trigger terms or variations a user might use, such as 'unclear plugin request', 'not sure which plugin', 'mixed plugin needs', or 'multi-intent plugin request'

Dimension	Reasoning	Score
Specificity	It names a domain ('Plugin Factory follow-up requests') and describes a general action ('analyze and select the correct plugin lane'), but does not list multiple specific concrete actions—it's essentially one action (routing/triage) described at a moderate level of detail.	2 / 3
Completeness	It clearly answers both 'what does this do' (analyze mixed/unclear requests and select the correct plugin lane) and 'when should Claude use it' ('Use when plugin intent lacks a clear lane owner'), with an explicit trigger clause.	3 / 3
Trigger Term Quality	It includes some relevant terms like 'Plugin Factory', 'follow-up requests', 'plugin lane', and 'plugin intent', but these are fairly domain-specific jargon. It lacks natural user-facing trigger terms a user might actually say (e.g., 'which plugin', 'route my request', 'unclear plugin type').	2 / 3
Distinctiveness Conflict Risk	The description carves out a clear niche as a triage/routing skill specifically for ambiguous Plugin Factory requests where no lane owner is obvious. This is unlikely to conflict with individual plugin lane skills that handle specific, well-defined intents.	3 / 3
	Total	10 / 12 Passed

Validation

90%

Warnings & errors only

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

Validation — 10 / 11 Passed

Validation for skill structure

Criteria	Description	Result
metadata_version	'metadata.version' is missing	Warning

	Total	10 / 11 Passed

Repository: jscraik/Agent-Skills
Path: Plugins/plugin-factory/skills/team_automation/plugin-router/SKILL.md
Commit: d933d80

Reviewed: 21 hours ago

Table of Contents

Discovery Implementation Validation

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.