CtrlK
BlogDocsLog inGet started
Tessl Logo

arn-code-taskify

This skill should be used when the user says "taskify", "create task list", "create tasks", "convert plan to tasks", "generate tasks from plan", "create tasks from plan", "turn plan into tasks", "arness code taskify", or wants to convert a structured project plan's TASKS.md into an executable Claude Code task list with proper dependency management.

66

Quality

80%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./plugins/arn-code/skills/arn-code-taskify/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

70%Weight 40%Scale 1-3

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

A clearly sequenced, validation-rich workflow with good sectioning and explicit error handling. The main gaps are mild verbosity in the deferred-setup and example-output blocks and action templates that lean on placeholders rather than fully executable invocations.

Suggestions

Tighten the Deferred Task List Setup block — the AskUserQuestion option wording, settings.json write procedure, and env-var warning could be condensed into a few lines or moved to a reference file, reducing token cost without losing clarity.

Make the Step 3 TaskCreate template more copy-paste-ready by showing a concrete filled example alongside the '<placeholder>' template, so the guidance reads as fully executable rather than illustrative.

Consider shortening the Step 5 example output to the essential structure (ready / blocked / next-step commands) since the full markdown block duplicates information already conveyed by the bullet list above it.

DimensionReasoningScore

Conciseness

The body is mostly efficient and well-organized with no padding about concepts Claude already knows, but the Deferred Task List Setup block (AskUserQuestion flows, settings.json writes, env-var warnings) and the verbose Step 5 example output add length that could be trimmed or moved to a reference, keeping it at 'Mostly efficient but could be tightened'.

2 / 3

Actionability

It gives concrete, named tool calls (TaskCreate, TaskUpdate, TaskList) with field templates and a worked ID-map example, but several templates are illustrative placeholders rather than fully copy-paste-ready invocations (e.g. the TaskCreate block uses '<Title>' / '<plan file path>' slots), matching the 'Some concrete guidance but incomplete / pseudocode-style' anchor.

2 / 3

Workflow Clarity

The five steps are clearly sequenced (Load → Parse → Create → Set Up Dependencies → Verify) with explicit validation checkpoints (duplicate/circular-dependency checks, a Verify step that compares the created list against TASKS.md, and a Proceed/Abort decision branch on validation failure), matching the 'clear sequence with explicit validation steps and feedback loops' anchor.

3 / 3

Progressive Disclosure

No bundle files exist and the skill is under the simple-skill threshold for external references; content is organized into clearly signaled sections (Workflow / Error Handling) with one level of structure and easy navigation, so per the rubric's simple-skills note it earns 3 on well-organized sections alone.

3 / 3

Total

10

/

12

Passed

Description

90%Weight 40%Scale 1-3

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A strong description with explicit natural-language triggers and a clear, distinctive what-and-when statement. Its only weakness is specificity: it describes the domain and a couple of actions rather than enumerating the full set of concrete operations.

Suggestions

Add a brief, concrete action list to lift specificity — e.g. 'reads TASKS.md, creates tasks via TaskCreate, and wires up dependencies via TaskUpdate' — so the description reads like the 3-anchor 'Extract text... fill forms, merge documents' pattern rather than naming the domain at a high level.

The malformed trigger phrase 'arness code taskify' appears to be a typo for the skill name; either correct it to a form a user would naturally say or drop it, since unnatural tokens dilute trigger quality.

DimensionReasoningScore

Specificity

It names the domain (converting a TASKS.md into a Claude Code task list) and the key actions (create tasks via TaskCreate, wire up dependency management) but does not enumerate the multiple concrete operations as comprehensively as a 3-anchor example like 'Extract text... fill forms, merge documents'; it stays at the 'Names domain and some actions' level.

2 / 3

Completeness

It explicitly answers both 'what' (convert a structured project plan's TASKS.md into an executable Claude Code task list with dependency management) and 'when' ('This skill should be used when the user says...'), satisfying the explicit-trigger requirement that caps lesser examples at 2.

3 / 3

Trigger Term Quality

It packs in many natural phrasings a user would actually say — 'taskify', 'create task list', 'create tasks', 'convert plan to tasks', 'generate tasks from plan', 'turn plan into tasks' — giving strong coverage of natural trigger terms.

3 / 3

Distinctiveness Conflict Risk

The TASKS.md + Claude Code task list + dependency-management niche is highly specific, and the distinctive 'taskify' trigger makes it unlikely to fire for the wrong skill.

3 / 3

Total

11

/

12

Passed

Validation

93%

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

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository
AppsVortex/arness
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.