skill-factory-router
Routes Codex skill lifecycle requests by selecting one Skill Factory lane, mode, and handoff. Use when users ask to create a skill, skillify a workflow, fix or audit a skill, improve skill quality, analyze routing failures, install a skill, or decide whether to keep, merge, split, or retire skill guidance.
75
92%
Does it follow best practices?
Impact
—
No eval scenarios have been run
Passed
No known issues
Quality
Discovery
100%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This is a strong description that clearly defines a specific routing/orchestration role within a skill management system. It excels at providing explicit trigger terms through a well-structured 'Use when' clause and uses distinctive domain-specific language that minimizes conflict risk. The description is concise yet comprehensive, covering both the mechanism (routing to lanes/modes) and the full range of triggering scenarios.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: routing skill lifecycle requests, selecting a Skill Factory lane/mode/handoff, creating skills, skillifying workflows, fixing/auditing skills, improving quality, analyzing routing failures, installing skills, and deciding on keep/merge/split/retire. | 3 / 3 |
Completeness | Clearly answers both 'what' (routes Codex skill lifecycle requests by selecting a Skill Factory lane, mode, and handoff) and 'when' (explicit 'Use when' clause listing specific trigger scenarios like creating, fixing, auditing, installing, or retiring skills). | 3 / 3 |
Trigger Term Quality | Includes many natural trigger terms users would say: 'create a skill', 'skillify a workflow', 'fix or audit a skill', 'improve skill quality', 'routing failures', 'install a skill', 'keep, merge, split, or retire'. These cover a wide range of user phrasings for skill management tasks. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive with domain-specific terminology like 'Codex skill lifecycle', 'Skill Factory lane', 'skillify a workflow', and 'routing failures'. This niche vocabulary makes it very unlikely to conflict with other skills. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
85%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a well-structured routing skill with strong actionability through its decision table, YAML handoff template, and concrete examples. The workflow is clear with appropriate validation gates and failure modes. Minor conciseness issues arise from overlapping constraint sections and some redundant guidance, but overall the skill is effective and well-organized.
Suggestions
Merge 'Constraints And Boundaries' and 'Execution Boundaries' into a single section to eliminate redundancy and save tokens.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is mostly efficient but includes some redundancy — constraints and execution boundaries overlap significantly, and some sections (Philosophy, When To Use) could be tightened. The anti-patterns and gotchas sections add modest value but border on over-explanation for a routing skill. | 2 / 3 |
Actionability | The decision table provides concrete routing rules, the handoff template is a copy-paste-ready YAML schema, and the examples map specific user phrases to exact lane/mode selections. The procedure is specific and executable. | 3 / 3 |
Workflow Clarity | The 6-step procedure is clearly sequenced with explicit decision points (first-principles check, blocking question gate). The fail-fast validation section and the failure mode section provide clear error recovery paths. The handoff template includes a blocked_by field for incomplete routes. | 3 / 3 |
Progressive Disclosure | The skill is structured as a routing overview that explicitly defers to lane-specific content ('Load the selected lane only after routing is complete'). References are clearly listed at the end with specific paths, and the skill avoids inlining lane details. Without bundle files provided, the references section is well-organized and one level deep. | 3 / 3 |
Total | 11 / 12 Passed |
Validation
100%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 11 / 11 Passed
Validation for skill structure
No warnings or errors.
- Repository
- jscraik/Agent-Skills
- Commit
4c78f98
- 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.