CtrlK
BlogDocsLog inGet started
Tessl Logo

task-breakdown

Group a session-metrics session's turns into higher-level SEMANTIC TASKS ("what was I actually trying to do") and render a Tasks companion page (*_tasks.html + *_tasks.md) with a worth-it / mixed / likely-waste verdict per task. Trigger when the user runs /task-breakdown, when session-metrics suggests a task breakdown after a JSON export, or when the user asks to "group my turns into tasks", "what tasks did this session cover", "which work was worth it vs wasted", or "break this session into tasks". Consumes the deterministic per-request breakdown (request_units) from a session-metrics JSON export — it never re-derives cost or token numbers. Args: $ARGUMENTS[0] = path to a session-metrics JSON export (optional; if omitted, generate one first).

77

Quality

96%

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

SKILL.md
Quality
Evals
Security

Quality

Content

92%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 body is highly actionable with executable commands, a clear validated workflow, and clean section structure that defers bulk detail to the sibling skill. It is slightly over-explained in the model-pinning rationale and fallback prose.

Suggestions

Tighten the Model note: drop the historical pinning rationale and keep only the forward guidance (capable model; /model sonnet for a cheaper run; avoid Haiku).

Shorten the manual-authoring fallback in step 2 to the essential field list and the 'request_units absent → re-run session-metrics' instruction, since --prepare-tasks is the preferred path.

DimensionReasoningScore

Conciseness

Mostly efficient with concrete commands and no explanations of concepts Claude already knows, but the model-pinning rationale and some defensive prose (e.g. the fallback paragraph) could be trimmed.

4 / 5

Actionability

Provides copy-paste-ready invocations (--prepare-tasks, --render-tasks), a concrete grouping.json schema, exact request_units field names, and two resolved renderer-path candidates covering the common install layouts.

5 / 5

Workflow Clarity

A clear 7-step sequence with explicit validation checkpoints — the renderer validates grouping (duplicate/unknown ids, schema drift), coverage is enforced, and figures must be read back from stdout rather than recomputed.

5 / 5

Progressive Disclosure

Self-contained body with well-labeled sections (Inputs, Steps, Guardrails) and no nested references; bulk detail is correctly deferred to the sibling session-metrics script rather than inlined.

5 / 5

Total

19

/

20

Passed

Description

100%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 is specific, complete, and trigger-rich, clearly stating both what the skill does and when to invoke it with natural user phrases. It is highly distinctive and tightly scoped to its companion skill.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — grouping turns into semantic tasks, rendering a Tasks companion page, assigning per-task verdicts, and consuming request_units — with comprehensive coverage rather than vague language.

5 / 5

Completeness

Explicitly answers both what (group turns into semantic tasks and render a verdicted companion page) and when (an explicit "Trigger when..." clause with concrete phrases), satisfying the Use-when requirement.

5 / 5

Trigger Term Quality

Includes natural user phrases ("group my turns into tasks", "what tasks did this session cover", "which work was worth it vs wasted", "break this session into tasks") plus the /task-breakdown command, covering synonyms and variations.

5 / 5

Distinctiveness Conflict Risk

Occupies a clear niche tied to the session-metrics skill and a specific /task-breakdown command with distinct triggers, giving minimal overlap risk with other skills.

5 / 5

Total

20

/

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.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
centminmod/my-claude-code-setup
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.