wf-player
Workflow template player — load a JSON template produced by wf-composer, bind context variables, execute nodes in DAG order (serial/parallel), persist state at checkpoints, support resume from any checkpoint. Uses ccw-coordinator serial-blocking for CLI nodes and team-coordinate worker pattern for parallel agent nodes. Triggers on "wf-player " or "/wf-player".
80
77%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./.claude/skills/wf-player/SKILL.mdQuality
Discovery
85%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 excels at specificity and distinctiveness, providing detailed technical capabilities and a clear niche. However, the trigger terms are overly technical command-based triggers rather than natural language terms users might use, which could limit discoverability when users describe their intent in plain language rather than using exact commands.
Suggestions
Add natural language trigger terms alongside command triggers, e.g., 'Use when the user wants to run a workflow, execute a template, resume a workflow from a checkpoint, or mentions workflow execution.'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: load JSON templates, bind context variables, execute nodes in DAG order (serial/parallel), persist state at checkpoints, support resume from any checkpoint. Very detailed about what it does. | 3 / 3 |
Completeness | Clearly answers both 'what' (load JSON templates, bind variables, execute DAG nodes, persist/resume checkpoints) and 'when' (triggers on 'wf-player' or '/wf-player'). The trigger clause is explicit, though narrow. | 3 / 3 |
Trigger Term Quality | Includes some trigger terms like 'wf-player' and '/wf-player', but these are highly technical/internal command names. Missing natural language terms a user might say like 'run workflow', 'execute template', 'resume workflow', or 'DAG execution'. The terms are jargon-heavy rather than natural user language. | 2 / 3 |
Distinctiveness Conflict Risk | Highly distinctive with a clear niche: workflow template execution from wf-composer JSON files with specific patterns (ccw-coordinator, team-coordinate). The specific command triggers ('wf-player', '/wf-player') and references to companion tools make it very unlikely to conflict with other skills. | 3 / 3 |
Total | 11 / 12 Passed |
Implementation
70%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 orchestration skill with excellent workflow clarity and progressive disclosure. The architecture overview, routing tables, and error handling are strong. The main weakness is that the core phases delegate entirely to external files, leaving the SKILL.md itself lacking in concrete, executable guidance — the reader gets a good map but no actual implementation details to act on directly.
Suggestions
Add at minimum a concrete code/pseudocode snippet for the template loading and variable binding logic in Phase 1, so the skill file itself contains some executable guidance rather than purely delegating
Include a brief example of what a session-state.json looks like (even 5-10 lines) to make the state management actionable without requiring the reader to consult specs/state-schema.md for basic understanding
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is reasonably efficient and avoids explaining basic concepts, but some sections like the architecture ASCII diagram and the phase descriptions that just say 'Read phases/0X-*.md and execute' with minimal added value could be tightened. The repeated 'Objective/Success' pattern for phases that delegate to external files adds some overhead. | 2 / 3 |
Actionability | The skill provides structured tables and clear routing logic, but the core execution phases (1-4) delegate entirely to external files with only vague objective statements. The actual executable guidance is missing from this file — there's no concrete code for template parsing, variable binding, or node execution. The CLI node blocking pattern is called out as critical but lacks executable detail. | 2 / 3 |
Workflow Clarity | The multi-step workflow is clearly sequenced with an architecture overview, explicit phase ordering, entry routing table, resume/reconciliation logic, and a comprehensive error handling table with specific resolution strategies. The checkpoint/resume mechanism provides a clear feedback loop for interrupted executions, and the critical CLI blocking pattern is explicitly called out. | 3 / 3 |
Progressive Disclosure | Excellent progressive disclosure — the SKILL.md serves as a clear overview and router, with phases delegated to `phases/01-load.md` through `phases/04-complete.md` and specs referenced via `specs/node-executor.md` and `specs/state-schema.md`. References are one level deep and clearly signaled with purpose descriptions. | 3 / 3 |
Total | 10 / 12 Passed |
Validation
81%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 9 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
allowed_tools_field | 'allowed-tools' contains unusual tool name(s) | Warning |
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 9 / 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.