workflow-skill-designer
Meta-skill for designing orchestrator+phases structured workflow skills. Creates SKILL.md coordinator with progressive phase loading, TodoWrite patterns, and data flow. Triggers on "design workflow skill", "create workflow skill", "workflow skill designer".
78
73%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Risky
Do not use without reviewing
Optimize this skill with Tessl
npx tessl skill review --optimize ./.claude/skills/workflow-skill-designer/SKILL.mdQuality
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 communicates a specific, niche capability (designing structured workflow skills) with concrete outputs (SKILL.md coordinator, phase loading, TodoWrite patterns). It includes explicit trigger terms and clearly answers both what and when. The only minor weakness is that the trigger terms section uses a slightly non-standard format ('Triggers on') rather than 'Use when', but it effectively serves the same purpose.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'designing orchestrator+phases structured workflow skills', 'Creates SKILL.md coordinator with progressive phase loading, TodoWrite patterns, and data flow'. These are concrete, specific capabilities. | 3 / 3 |
Completeness | Clearly answers both what ('Meta-skill for designing orchestrator+phases structured workflow skills. Creates SKILL.md coordinator with progressive phase loading, TodoWrite patterns, and data flow') and when ('Triggers on "design workflow skill", "create workflow skill", "workflow skill designer"'). | 3 / 3 |
Trigger Term Quality | Includes explicit trigger phrases that users would naturally say: 'design workflow skill', 'create workflow skill', 'workflow skill designer'. Also includes domain-specific terms like 'orchestrator', 'phases', 'TodoWrite patterns' that help with matching. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive niche — a meta-skill specifically for designing workflow skills with orchestrator+phases patterns. The trigger terms are very specific ('workflow skill designer') and unlikely to conflict with general coding or document skills. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
47%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a comprehensive meta-skill with excellent workflow structure and clear phase sequencing, but it severely violates conciseness principles. The document is roughly 3-4x longer than necessary, with redundant tables, bilingual annotations, and extensive pattern explanations that could be extracted into reference files or condensed significantly. The actionability is moderate — templates and patterns are provided but lean toward conceptual illustration rather than executable specifics.
Suggestions
Reduce token count by 60-70%: move Pattern 6-9 detailed explanations into a separate patterns-reference.md file, keeping only 1-2 line summaries with Ref: links in SKILL.md
Choose one language (English or Chinese) consistently — bilingual inline comments double token cost without adding clarity for Claude
Convert the SKILL.md and Phase File templates into actual file-generation code or concrete examples with real skill names rather than placeholder-heavy pseudotemplates
Consolidate the multiple mapping tables (Frontmatter Conversion, Orchestrator Content Mapping, Design Decision Framework) into a single concise decision checklist
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Extremely verbose at ~400+ lines. Contains extensive explanations of patterns Claude could infer, redundant tables mapping the same concepts multiple ways, bilingual (English/Chinese) content that doubles token cost, and lengthy template sections. Much of this could be condensed to 1/3 the size without losing actionable information. | 1 / 3 |
Actionability | Provides concrete templates, code examples (JavaScript pseudocode for AskUserQuestion, TodoWrite patterns), and specific file structures. However, much of the code is illustrative pseudocode rather than truly executable, and the skill relies heavily on conceptual patterns rather than copy-paste-ready implementations. The templates are useful but contain placeholder syntax that requires significant interpretation. | 2 / 3 |
Workflow Clarity | The 4-phase execution flow is clearly sequenced with explicit Ref: markers, a Phase Reference Documents table, and well-defined input/output for each phase. Validation is explicitly covered in Phase 4, and the compact recovery pattern (Pattern 9) provides thorough error recovery with checkpoint verification steps and dual-layer protection. | 3 / 3 |
Progressive Disclosure | The skill correctly references 4 phase files via a Phase Reference Documents table with on-demand loading, which is good progressive disclosure. However, the SKILL.md itself is monolithic — Pattern 9 (Compact Recovery) alone spans ~100 lines of detailed implementation that could be in a separate reference file. The inline templates and extensive pattern documentation bloat the coordinator beyond its coordination role. | 2 / 3 |
Total | 8 / 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 |
|---|---|---|
allowed_tools_field | 'allowed-tools' contains unusual tool name(s) | Warning |
Total | 10 / 11 Passed | |
- Repository
- catlog22/Claude-Code-Workflow
- Commit
0f8e801
- 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.