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".

Quality

73%

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Passed

No known issues

Fix and improve this skill with Tessl

tessl review fix ./.claude/skills/wf-player/SKILL.md

Quality

Content

62%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

This skill demonstrates strong workflow architecture with clear phase sequencing, comprehensive error handling, and thoughtful resume/checkpoint logic. Its main weakness is heavy reliance on external phase and spec files that aren't provided, leaving the SKILL.md as more of a routing document than a self-contained guide. The actionability suffers because the actual execution details are entirely deferred to missing files.

Suggestions

Inline the essential content from phases/01-load.md through 04-complete.md (at least key steps and commands) so the SKILL.md is actionable without external files, or provide the bundle files.

Add concrete executable examples — e.g., a sample Skill() invocation for a skill node, a ccw cli command for a CLI node, and a sample session-state.json snippet — so Claude can act without guessing.

Remove the architecture ASCII diagram or merge it with the phase descriptions to reduce duplication and improve conciseness.

Dimension	Reasoning	Score
Conciseness	The content is reasonably efficient and avoids explaining basic concepts Claude would know. However, the architecture ASCII diagram and some tables could be tightened — the architecture block largely duplicates what the phase sections describe, and some table entries are somewhat verbose.	2 / 3
Actionability	The skill provides structured guidance with clear phases, error handling tables, and specific constants, but critical execution details are deferred to external phase files (phases/01-load.md, etc.) and spec files that are not provided. The main SKILL.md itself contains no executable code or concrete commands beyond the display format example, making it incomplete as standalone guidance.	2 / 3
Workflow Clarity	The multi-step workflow is clearly sequenced through numbered phases with explicit entry routing, resume/checkpoint logic, and a comprehensive error handling table with specific resolution strategies per failure mode. The critical CLI node blocking warning and the resume reconciliation steps (resetting running nodes to pending) demonstrate strong validation and recovery awareness.	3 / 3
Progressive Disclosure	The skill references external files (phases/01-load.md through 04-complete.md, specs/node-executor.md, specs/state-schema.md) with clear signaling, which is good structure. However, no bundle files are provided, meaning the referenced content doesn't actually exist in the evaluated context, and the phase descriptions in SKILL.md are too thin to be useful without those files — each phase is essentially 'read this other file and execute.'	2 / 3
	Total	9 / 12 Passed

Description

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.

This is a strong, technically detailed description that clearly specifies what the skill does and when to trigger it. Its main weakness is that the trigger terms are command-based rather than natural language, which could cause it to be missed when users describe their intent in plain English rather than using the exact command prefix. The description is well-structured but leans heavily on technical jargon.

Suggestions

Add natural language trigger terms users might say, such as 'run workflow', 'execute template', 'resume workflow', or 'play workflow' to complement the command-based triggers.

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.	3 / 3
Trigger Term Quality	Includes specific trigger commands ('wf-player', '/wf-player') and domain terms like 'workflow template', 'JSON template', 'DAG', 'checkpoint', but these are technical jargon rather than natural user language. Missing common variations a user might say like 'run workflow', 'execute template', 'resume workflow'.	2 / 3
Distinctiveness Conflict Risk	Highly distinctive with a clear niche: workflow template execution from wf-composer JSON files with specific trigger commands. References specific tools (ccw-coordinator, team-coordinate) and patterns, making it very unlikely to conflict with other skills.	3 / 3
	Total	11 / 12 Passed

Validation

81%

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 — 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: 07491b0

Reviewed: 20 days 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.