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.
57
66%
Does it follow best practices?
Impact
—
No eval scenarios have been run
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./Plugins/skill-factory/fixtures/budget-archive/2026-04-19/skills/team_automation/skill-factory/SKILL.mdQuality
Discovery
67%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 adequately communicates its routing purpose and includes an explicit 'Use when' clause, which is its strongest aspect. However, it relies on internal jargon ('front-door router', 'lane selected', 'deeper execution') that doesn't help Claude understand the concrete value, and the trigger terms could be broader to capture more natural user phrasings. The description would benefit from being more specific about what routing outcomes are possible and using more user-facing language.
Suggestions
Replace internal jargon like 'front-door router', 'lane selected', and 'deeper execution' with concrete descriptions of what the skill actually does (e.g., 'Routes skill-related requests to the appropriate Skill Factory workflow').
Expand trigger terms to include natural variations users might say, such as 'build a skill', 'make a skill', 'add a skill', 'update a skill', 'new skill', or 'edit a skill'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | It names the domain ('Skill Factory plugin') and some actions ('create, improve, install, or skillify skills'), but the description is more about routing than concrete actions. The actual capabilities are vague—'correct lane selected before deeper execution' doesn't describe what it concretely does. | 2 / 3 |
Completeness | It explicitly answers both 'what' (front-door router for the Skill Factory plugin that selects the correct lane) and 'when' ('Use when users ask generally to create, improve, install, or skillify skills'). The 'Use when...' clause is present and provides explicit trigger guidance. | 3 / 3 |
Trigger Term Quality | Includes some relevant keywords like 'create', 'improve', 'install', and 'skillify skills' that users might say. However, 'front-door router' and 'lane selected' are internal jargon, and it misses natural variations like 'build a skill', 'make a skill', 'add a skill', or 'update a skill'. | 2 / 3 |
Distinctiveness Conflict Risk | It's somewhat specific to the Skill Factory plugin routing role, but terms like 'create', 'improve', and 'install' are generic enough to potentially conflict with other skill-related tools. The 'skillify' term is distinctive, but the broader terms could overlap with downstream skills that actually perform creation or improvement. | 2 / 3 |
Total | 9 / 12 Passed |
Implementation
64%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is an admirably concise router skill that maps five intents to five sub-skills. Its brevity is a strength, but it lacks disambiguation logic for edge cases, fallback behavior, and the referenced contract.yaml is not present in the bundle to verify. The skill would benefit from a few more lines specifying how to handle ambiguous requests.
Suggestions
Add brief disambiguation criteria or example user phrases for each lane to make routing decisions more actionable (e.g., 'create: user wants a new skill from scratch; improve: user has an existing skill and wants it enhanced').
Specify fallback behavior when a request doesn't clearly match one lane (e.g., ask the user to clarify, or default to a specific lane).
Ensure the referenced ./references/contract.yaml exists in the bundle, or note what it should contain so the skill is self-sufficient if the file is missing.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Extremely lean — every token earns its place. No unnecessary explanation of what routing is or how skills work. Just the mapping and a reference link. | 3 / 3 |
Actionability | The routing table is concrete and the lane names are specific, but there's no guidance on how to determine which lane applies (e.g., disambiguation criteria, keywords to match, or fallback behavior). A router skill should specify decision logic more explicitly. | 2 / 3 |
Workflow Clarity | The routing is presented as a simple mapping, which is appropriate for a router, but there's no handling of ambiguous or multi-intent requests, no fallback/default behavior, and no validation step (e.g., confirming the selected lane with the user before dispatching). | 2 / 3 |
Progressive Disclosure | References the contract.yaml for details, which is good one-level-deep disclosure. However, the bundle has no files provided, so the referenced path (./references/contract.yaml) cannot be verified, and there's no indication of what each sub-skill covers to help navigate. | 2 / 3 |
Total | 9 / 12 Passed |
Validation
90%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
- Commit
d00c351
- 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.