CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

plugin-factory-router

Route plugin-factory requests to the right lane. Use when plugin creation, building, installation, review, or routing is broad, mixed, or under-specified.

Quality

65%

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/skills/plugin-factory-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 a disciplined, terse policy document with strong safety boundaries and a fail-fast validation gate backed by an executable script. But it reads more as policy than an operational guide: the routing procedure is never sequenced, key sections stay abstract without a worked example, and the reference situation is mixed — local references are clean while four external paths dangle outside the bundle and three bundle files go unlinked.

Suggestions

Add a short numbered routing sequence (parse request, check required inputs, match route cues from the runtime notes, return lane + rationale + exact next command) with the fail-fast gate as an explicit step, instead of leaving ordering implicit across the Inputs/Deliverables/Failure-mode sections.

Include one worked example of the routing output (selected lane, one-sentence rationale, exact next command, blocked case) so the deliverable format is executable rather than merely described.

Repair the References section: link the bundled contract.yaml, evals.yaml, and task-profile.json where the body currently duplicates their content, and resolve or remove the four Infrastructure/references/... paths that are absent from the bundle.

DimensionReasoningScore

Conciseness

The body is terse and imperative throughout ("Route before acting", "Keep scope tight", "Fail fast") and never explains concepts Claude already knows. It misses anchor 5 because the no-install/no-execute rule is repeated in Execution Boundaries, Gotchas, Constraints, and Anti-Patterns, and "When to use" restates the frontmatter description.

4 / 5

Actionability

Some guidance is concrete — deliverables like "One selected lane", "One exact next command or prompt to execute", and a runnable validation script — but the core routing procedure and the "First-Principles Gate" ("identify the user outcome, copied assumption, smallest effective mechanism") remain abstract, with no worked example of the routing output. This sits between anchor 3 and anchor 4; incomplete concrete guidance places it at 3.

3 / 5

Workflow Clarity

Inputs, Deliverables, Failure mode, and Validation sections imply a sequence and include a fail-fast checkpoint with a runnable script, but the routing steps themselves (parse request, check inputs, match route cues, emit handoff) are never sequenced; ordering is implicit and the referenced workflow.md only lists lanes. Anchor 3 (sequence present but implicit) fits better than 4 (explicit checkpoints at each step).

3 / 5

Progressive Disclosure

Local references are well handled — references/workflow.md and references/current-codex-plugin-runtime.md exist in the bundle, are one level deep, and are clearly signaled with "Read when:" cues. However, four referenced paths under Infrastructure/references/ do not exist in the bundle, and the bundled contract.yaml, evals.yaml, and task-profile.json are never linked from the body. Some structure, but organization gaps hold it at anchor 3 rather than 4.

3 / 5

Total

13

/

20

Passed

Description

58%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 explicitly answers both what it does and when to use it, with a clearly named plugin-factory niche. However, it offers only one concrete action, leans on internal lane vocabulary ("the right lane", "broad, mixed, or under-specified"), and shares trigger verbs with the sibling lanes it routes among, which caps specificity, trigger quality, and distinctiveness at mid-scale.

Suggestions

Name the concrete routing outcome in the description, e.g. "Selects exactly one plugin lane (creator, builder, installer) and returns the rationale plus the exact next command to run."

Replace the meta-qualifier "broad, mixed, or under-specified" with natural user triggers such as "when the user provides a plugin URL, asks to create, build, install, or review a plugin, or the request is ambiguous".

Differentiate the router from its sibling lanes by leading with the decision function ("decides which plugin-factory lane handles a request") rather than repeating the same creation/building/installation trigger verbs those skills already use.

DimensionReasoningScore

Specificity

"Route plugin-factory requests to the right lane" names the domain and a single concrete action (routing), but lists no other concrete capabilities or outcomes. It matches anchor 3 (domain plus 1-2 concrete actions, not comprehensive); it is not 4 because it does not list several specific actions.

3 / 5

Completeness

Both parts are explicit: the what ("Route plugin-factory requests to the right lane") and a when clause ("Use when plugin creation, building, installation, review, or routing is broad, mixed, or under-specified"). It falls short of anchor 5 because the when-clause is conditioned on abstract request shape rather than concrete user trigger phrases.

4 / 5

Trigger Term Quality

"plugin creation, building, installation, review, or routing" provides some relevant keywords, but qualifiers like "broad, mixed, or under-specified" and "the right lane" are internal vocabulary, and natural user phrasings (e.g. "add a plugin", "plugin URL", "audit this plugin") are missing. Anchor 3 fits better than 4 because common variations are absent.

3 / 5

Distinctiveness Conflict Risk

"plugin-factory" carves a clear niche distinct from non-plugin skills, but the triggers reuse the same creation/building/installation verbs as the sibling plugin-creator/builder/installer lanes it routes to, creating real overlap risk with closely related skills. Not 4, because the overlap is more than minor; not 2, because the domain itself is specific.

3 / 5

Total

13

/

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

metadata_version

'metadata.version' is missing

Warning

Total

15

/

16

Passed

Repository

jscraik/Agent-Skills

Path

Plugins/plugin-factory/skills/plugin-factory-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.