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

66%

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

Quality

Content

64%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 is an admirably concise router skill that maps user intents to sub-skills. Its main weakness is the lack of disambiguation guidance — there's no criteria for distinguishing between overlapping intents (e.g., 'improve' vs 'refactor') and no fallback for ambiguous requests. The referenced contract.yaml is not present in the bundle, making it impossible to verify completeness.

Suggestions

Add brief disambiguation criteria or example triggers for each lane (e.g., 'create: user wants a new skill from scratch; improve: user has an existing skill and wants to enhance it; refactor: user wants structural changes without new functionality').

Include a fallback instruction for ambiguous requests (e.g., 'If intent is unclear, ask the user to clarify before routing').

Ensure the referenced `./references/contract.yaml` exists in the bundle, or remove the reference if it doesn't exist.

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 clear, but there's no guidance on how to determine which lane to select (e.g., decision criteria, example user inputs mapped to lanes). The skill relies on implicit understanding of when 'create' vs 'improve' vs 'refactor' applies.	2 / 3
Workflow Clarity	The routing is a single-step dispatch, which is simple enough, but there's no handling of ambiguous requests, no fallback behavior, and no validation step for confirming the correct lane was selected before delegating.	2 / 3
Progressive Disclosure	References the contract.yaml file for details, which is good one-level-deep disclosure. However, the bundle has no files provided, so the referenced path cannot be verified, and the five sub-skills are referenced without any brief description of what each does to aid navigation.	2 / 3
	Total	9 / 12 Passed

Description

67%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 adequately communicates its routing purpose and includes an explicit 'Use when' clause, which is a strength. However, it relies on internal jargon ('front-door router', 'lane selected', 'deeper execution') that doesn't help with user-facing trigger matching, and the action verbs are quite generic, creating potential overlap with other skills.

Suggestions

Replace internal jargon like 'front-door router' and 'correct lane selected before deeper execution' with user-facing language describing what the routing achieves for the user.

Expand trigger terms with natural variations users might say, such as 'build a skill', 'add a new skill', 'update a skill', 'edit a skill', or 'manage skills'.

Dimension	Reasoning	Score
Specificity	It names a domain ('Skill Factory plugin') and some actions ('create, improve, install, or skillify skills'), but the description is more about routing than concrete actions. The phrase 'front-door router' and 'correct lane selected before deeper execution' are somewhat abstract.	2 / 3
Completeness	It 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') with an explicit 'Use when' clause.	3 / 3
Trigger Term Quality	Includes relevant terms like 'create', 'improve', 'install', and 'skillify skills' which users might say, but 'front-door router' and 'lane selected' are internal jargon unlikely to match user queries. Missing natural variations like 'build a skill', 'add a skill', 'make a new skill'.	2 / 3
Distinctiveness Conflict Risk	The description positions itself as a router for skill-related requests, which is somewhat distinctive, but terms like 'create' and 'improve' are very generic and could overlap with many other skills. The 'Skill Factory' mention helps but the broad action verbs increase conflict risk.	2 / 3
	Total	9 / 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/skill-factory/fixtures/budget-archive/2026-04-19/skills/team_automation/skill-factory/SKILL.md
Commit: d933d80

Reviewed: 24 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.