CtrlK
BlogDocsLog inGet started
Tessl Logo

csv-wave-pipeline

Requirement planning to wave-based CSV execution pipeline. Decomposes requirement into dependency-sorted CSV tasks, computes execution waves, runs wave-by-wave via spawn_agents_on_csv with cross-wave context propagation.

40

Quality

41%

Does it follow best practices?

Impact

No eval scenarios have been run

SecuritybySnyk

Passed

No known issues

Fix and improve this skill with Tessl

tessl review fix ./.codex/skills/csv-wave-pipeline/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

55%

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

The skill is highly actionable with excellent workflow clarity—every phase has concrete, executable code with clear sequencing and validation checkpoints. However, it is severely over-engineered for a SKILL.md file: at 600+ lines it includes complete implementations of CSV parsing, topological sort, and other utilities that Claude already knows how to write. The lack of any progressive disclosure (no bundle files, no external references) makes this a monolithic document that wastes significant context window space.

Suggestions

Extract CSV utility functions (parseCsv, parseCsvLine, csvEscape, updateMasterCsvRow) into a referenced bundle file like `csv-utils.js` and reference it from SKILL.md

Remove or drastically condense the wave computation algorithm—describe the approach (Kahn's BFS topological sort with depth tracking) in 2-3 lines and trust Claude to implement it, rather than providing 40+ lines of code

Move the instruction template builder and handoff intake code into separate bundle files, keeping only their interface/usage in the main SKILL.md

Condense the Phase 3 report generation code to a brief description of desired output format rather than full string template code—Claude can generate markdown reports from a schema description

DimensionReasoningScore

Conciseness

The skill is extremely verbose at ~600+ lines. It includes full implementation code for CSV parsing, session initialization, wave computation, result aggregation, instruction templates, and utility functions. Much of this (CSV parsing, topological sort, string escaping) is standard algorithmic knowledge Claude already possesses. The handoff intake section alone is ~50 lines of code for an optional feature. This could be condensed significantly.

1 / 3

Actionability

The skill provides fully executable JavaScript code for every phase: session initialization, wave computation (complete Kahn's algorithm), CSV generation, wave execution with spawn_agents_on_csv calls, result merging, and report generation. The instruction template for agents is complete and copy-paste ready. Output schemas, CSV schemas, and file structures are all concrete.

3 / 3

Workflow Clarity

The three-phase workflow (Decompose → Execute Waves → Aggregate) is clearly sequenced with explicit validation checkpoints: user validation after Phase 1, dependency checking before each wave task, result merging after each wave, and retry offering after Phase 3. Error handling table covers all failure modes. The skip-on-failure pattern and wave ordering rules are explicit. Feedback loops exist for failed tasks (retry option).

3 / 3

Progressive Disclosure

This is a monolithic wall of text with no bundle files and no references to external documentation. The entire implementation—CSV utilities, wave computation algorithm, instruction templates, handoff intake, Phase 1-3 code, error handling, and best practices—is crammed into a single file. The CSV parsing utilities, instruction template, and handoff intake logic could easily be separate referenced files.

1 / 3

Total

8

/

12

Passed

Description

27%

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 is technically detailed but written entirely in implementation jargon rather than user-facing language. It lacks a 'Use when...' clause entirely, making it difficult for Claude to know when to select this skill. While the specific actions are enumerated, the terminology would not match natural user requests.

Suggestions

Add an explicit 'Use when...' clause describing user-facing scenarios, e.g., 'Use when the user wants to break down a complex requirement into parallelizable tasks and execute them in dependency order.'

Replace technical jargon with natural trigger terms users would say, such as 'break down requirements', 'parallel execution', 'task dependencies', 'multi-step planning'.

Briefly explain what 'wave-based CSV execution' means in plain language so Claude can match it to user intent rather than internal implementation details.

DimensionReasoningScore

Specificity

Lists multiple specific concrete actions: decomposes requirements into dependency-sorted CSV tasks, computes execution waves, runs wave-by-wave via spawn_agents_on_csv, and propagates cross-wave context.

3 / 3

Completeness

Describes what it does but completely lacks any 'Use when...' clause or equivalent trigger guidance. Per the rubric, a missing 'Use when...' clause caps completeness at 2, and the 'what' is also expressed in overly technical terms making it weak, so scoring at 1.

1 / 3

Trigger Term Quality

Uses highly technical jargon like 'wave-based CSV execution pipeline', 'spawn_agents_on_csv', 'cross-wave context propagation' that users would never naturally say. Missing natural trigger terms a user might use like 'break down requirements', 'parallel tasks', or 'plan execution'.

1 / 3

Distinctiveness Conflict Risk

The technical specificity of 'wave-based CSV execution' and 'spawn_agents_on_csv' creates some distinctiveness, but the 'requirement planning' prefix is generic enough to potentially overlap with other planning or decomposition skills.

2 / 3

Total

7

/

12

Passed

Validation

72%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation8 / 11 Passed

Validation for skill structure

CriteriaDescriptionResult

skill_md_line_count

SKILL.md is long (961 lines); consider splitting into references/ and linking

Warning

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

8

/

11

Passed

Repository
catlog22/Claude-Code-Workflow
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.