CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

skill-factory

Front-door router for the Skill Factory plugin. Use when users ask generally to create, improve, install, or skillify skills and need the correct lane selected before deeper execution.

Quality

81%

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

86%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 lean router body: an unambiguous verb-to-lane mapping plus one well-signaled, verified reference. The only gaps are minor: no instruction on how to dispatch to the linked skills and no handling of ambiguous or multi-match requests.

DimensionReasoningScore

Conciseness

The body is roughly ten lean lines: a five-entry verb-to-skill mapping and one conditional reference pointer. There is no padding and no explanation of concepts Claude already knows, matching anchor 5 (lean and efficient; every token earns its place).

5 / 5

Actionability

The verb-to-lane mapping ("create -> [[skill-creator]]" etc.) is concrete, executable direction for an instruction-only routing skill, and the reference pointer is specific. It falls short of anchor 5 only because the body never states how to invoke the [[...]] targets (Skill tool vs. agent delegation), leaving a minor gap.

4 / 5

Workflow Clarity

As a simple single-purpose skill, the single routing action is unambiguous, which per the rubric's simple-skill note could justify a 5. However, edge cases are unhandled: requests matching multiple or zero verbs, and ambiguous intent (which contract.yaml itself lists as a risk) have no stated resolution, fitting anchor 4.

4 / 5

Progressive Disclosure

The skill is under 50 lines with clean sections, and its single reference is clearly signaled ("Read when: lane contract details are required") and one level deep; ./references/contract.yaml exists and holds the lane contract details. This matches anchor 5 and the rubric's short-skill allowance.

5 / 5

Total

18

/

20

Passed

Description

70%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, concise description with an explicit and concrete "Use when" clause and natural trigger terms. Its main weakness is that the stated capability is a single routing action described tersely, and a couple of common synonyms for the trigger verbs are absent.

Suggestions

Name the concrete routing action more explicitly (e.g., "Routes broad skill-authoring requests to the correct lane") rather than relying on the terse "Front-door router" label.

Add one or two common synonyms for trigger verbs, such as "build" or "write", to broaden natural keyword coverage.

DimensionReasoningScore

Specificity

"Front-door router" names the domain and a single concrete action (routing to the correct lane), with the verbs create/improve/install/skillify describing input request categories rather than several distinct actions the skill itself performs. This matches anchor 3 (domain plus 1-2 concrete actions) better than anchor 4, which expects several specific actions with only minor coverage gaps.

3 / 5

Completeness

Both what ("Front-door router for the Skill Factory plugin"... "the correct lane selected") and when ("Use when users ask generally to create, improve, install, or skillify skills") are present, with the when clause explicit and concrete. The what is somewhat terse and depends on plugin context to be fully understood, fitting anchor 4 rather than 5.

4 / 5

Trigger Term Quality

"create, improve, install, or skillify skills" are natural phrasings users would actually say, and "skillify" is a distinctive plugin term. A few common synonyms (build, write, author) are missing, fitting anchor 4 (good keyword coverage; a few natural terms missing) rather than 5.

4 / 5

Distinctiveness Conflict Risk

The skill occupies a clear niche (routing skill-authoring requests) and would not trigger for unrelated skills, but its create/improve/install verbs intentionally overlap with the lane skills it dispatches to. Anchor 4 (mostly distinct; minor overlap risk with closely related skills) is the best fit.

4 / 5

Total

15

/

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/skill-factory/fixtures/budget-archive/2026-04-19/skills/team_automation/skill-factory/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.