CtrlK
BlogDocsLog inGet started
Tessl Logo

skill-work-slicing

Break a plan or spec into vertical slices that each declare what blocks them — use when work is agreed but not yet cut into fileable pieces

64

Quality

76%

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 ./.claude/skills/skill-work-slicing/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

81%Weight 40%Scale 1-5

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

The content is a well-structured, actionable instruction skill with concrete tracker commands, explicit validation checkpoints, and feedback loops. It is slightly held back by minor conciseness trims and the absence of a full worked command example.

Suggestions

Tighten the horizontal-vs-vertical illustration and a few explanatory sentences to push conciseness toward fully lean.

Add one complete end-to-end example showing a slice list with real-ish ids and the exact bd create / bd dep add sequence in dependency order.

DimensionReasoningScore

Conciseness

The body is efficient and largely assumes Claude's competence, with only minor explanatory sentences (e.g. the horizontal-vs-vertical illustration) that could be trimmed, fitting the 'efficient; minor over-explanation' anchor.

4 / 5

Actionability

It gives concrete, copy-paste-ready commands ('bd create --parent=<id>', 'bd dep add <issue> <depends-on>', 'bd ready') and an exact command-emit fallback, with only minor gaps around a full end-to-end example sequence.

4 / 5

Workflow Clarity

A numbered 4-step workflow is paired with explicit validation/checkpoints (Stop Or Checkpoint Rules, a Verification checklist) and feedback loops (recut on cycle or unverifiable slice); the batch filing operation has validation, so it is not capped at 3.

5 / 5

Progressive Disclosure

No bundle files exist and the skill is self-contained with well-organized sections and no nested references; structure is good and navigation is easy, though it is a single monolithic file rather than a split-with-references layout.

4 / 5

Total

17

/

20

Passed

Description

71%Weight 40%Scale 1-5

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 cleanly answers both what and when with a concrete trigger phrase, and occupies a distinct niche. It is slightly limited by listing only 1-2 concrete actions and omitting common synonyms like 'tickets' or 'tasks'.

Suggestions

Add 1-2 more concrete actions (e.g. 'file the slices as tracker tickets and wire up blocking edges') to lift specificity.

Include natural synonyms users would say such as 'tickets', 'tasks', or 'break down the work' to broaden trigger coverage.

DimensionReasoningScore

Specificity

Names the domain and 1-2 concrete actions ('Break a plan or spec into vertical slices', 'declare what blocks them') but does not enumerate a comprehensive list of actions, matching the anchor for 1-2 concrete actions.

3 / 5

Completeness

It explicitly answers both what ('Break a plan or spec into vertical slices that each declare what blocks them') and when ('use when work is agreed but not yet cut into fileable pieces') with a concrete trigger phrase.

5 / 5

Trigger Term Quality

Relevant keywords like 'plan', 'spec', 'vertical slices', and 'fileable pieces' are present, but common synonyms a user might say ('tickets', 'tasks', 'break down') are missing, so it is not comprehensive.

3 / 5

Distinctiveness Conflict Risk

It carves a clear niche (slicing agreed work into fileable, blocking-declared tickets) with mostly distinct triggers, though it has minor overlap risk with adjacent planning skills like pressure-test and octo:parallel.

4 / 5

Total

15

/

20

Passed

Validation

100%

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

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
nyldn/claude-octopus
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.