CtrlK
BlogDocsLog inGet started
Tessl Logo

deep-work

Use when someone wants to plan a deep work day, time-block their calendar or task list, budget or cut shallow work, protect focus hours, track deep-work sessions and streaks, run an end-of-day shutdown ritual, or says "/deep-work" or "/time-block". Classifies tasks deep vs shallow, builds an energy-first time-blocked schedule that refuses deep demand past the 4-hour ceiling, batches shallow work into at most two windows, and logs focus sessions against a weekly target.

76

Quality

96%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

The risk profile of this skill

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.

A well-structured, highly actionable skill body: executable commands at every step, explicit refusal-based validation checkpoints for batch/budget operations, and clean one-level-deep progressive disclosure into real bundle files. Only minor conciseness slack in the intro and rules prose.

DimensionReasoningScore

Conciseness

Mostly lean and executable with copy-paste commands, but the 'What this does' intro paragraph and Rules section restate concepts already in the description, and the flourish 'A calendar full of reactions is not a plan' is padding that could be trimmed. It sits noticeably above the mostly-efficient anchor (3) but short of fully lean (5).

4 / 5

Actionability

Every step gives fully executable, copy-paste-ready bash invocations with real arguments and flags, the Scripts table documents roles and exit codes, and the common cases (audit, plan, log/status) are all covered with concrete examples.

5 / 5

Workflow Clarity

A clear four-step sequence (audit → block → log → shutdown) with explicit validation checkpoints via exit-2 refusals — 'OVER-BUDGET means cut, batch, or delegate before any schedule is built' and the planner 'names what to defer' / 'names what to drop' — providing feedback loops for the batch/destructive operations.

5 / 5

Progressive Disclosure

A concise overview body points one level deep to real, well-signaled bundle files (three references, two assets, three scripts), each annotated with its purpose; the referenced paths all exist and navigation is easy with no nested-reference chains.

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.

A high-quality description: concrete capabilities, natural trigger phrases including slash commands, explicit what-and-when guidance, and a distinct niche. Third-person voice is used correctly throughout the capability clause.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — 'Classifies tasks deep vs shallow', 'builds an energy-first time-blocked schedule that refuses deep demand past the 4-hour ceiling', 'batches shallow work into at most two windows', 'logs focus sessions against a weekly target' — giving comprehensive coverage rather than vague domain naming.

5 / 5

Completeness

Opens with an explicit 'Use when someone wants to...' clause enumerating concrete triggers, then states clearly what the skill does (classify, build, batch, log) — explicitly answering both 'when' and 'what'.

5 / 5

Trigger Term Quality

Covers natural phrasings users would actually say ('plan a deep work day', 'time-block their calendar or task list', 'budget or cut shallow work', 'protect focus hours', 'track deep-work sessions and streaks', 'run an end-of-day shutdown ritual') plus the explicit slash commands '/deep-work' and '/time-block'.

5 / 5

Distinctiveness Conflict Risk

Occupies a clear niche (single-person attention/time-blocking with a 4-hour deep ceiling) with distinctive triggers unlikely to fire for unrelated skills; the metadata distinct_from field reinforces the boundary.

5 / 5

Total

20

/

20

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
alirezarezvani/claude-skills
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.