CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

planning-work

Coordinate substantial work with multiple outcomes, dependencies, handoffs, or durable checkpoints. Use when decomposing work, resuming a tracked effort, or revising a plan after evidence changes its premises. Reuse the active environment's work record and authorization.

Quality

89%

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

The canonical home for this skill is planning-work in slurpyb/pi-taskfile

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.

An exemplary instruction-only skill body: a five-stage workflow with explicit 'Ready when' validation gates, a failure-feedback loop, a concrete depth-selection table, and a checklist-style handoff format, all delivered in lean prose with clean one-level-deep reference routing. The only gap is that concrete worked instances and environment-specific commands are deferred to references rather than shown inline.

DimensionReasoningScore

Conciseness

The body is lean, imperative, and free of padding — e.g., 'Execute one bounded unit per owner at a time, check its result, and record the observed evidence before dependent work' — with no explanation of concepts Claude already knows. Every section (role, workflow, output, references) earns its place, matching the 'lean and efficient; assumes Claude's competence' anchor rather than the 4 anchor's 'minor instances of over-explanation'.

5 / 5

Actionability

Concrete, usable structures throughout: the four contract fields (Outcome, Scope and constraints, Verification, Completion condition), a Compact/Structured/Design-intensive depth-selection table with explicit 'Select when' criteria, per-stage 'Ready when' gates, and a five-field output checklist. It falls short of 5 because several directives deliberately defer specifics to the environment ('Discover concrete commands and conventions from the environment') and no worked instance is inlined (examples live in worked-examples.md); it is well above 3's pseudocode-level vagueness.

4 / 5

Workflow Clarity

Five numbered stages each end in an explicit validation checkpoint ('**Ready when:**...'), stage 4 contains a full error-recovery feedback loop ('When a check fails, use its evidence to diagnose and correct the unit; when attempts repeat the same failure, revisit the premise'), and stage 5 covers interruption/resume reconciliation. The output section is itself a checklist, matching the 5 anchor (explicit validation steps, feedback loops, checklist); the destructive/batch cap does not apply since this skill coordinates rather than performs risky operations.

5 / 5

Progressive Disclosure

All four bundle references (task-contracts.md, decomposition.md, verification.md, worked-examples.md) exist and are exactly one level deep. Each is signalled inline at its decision point ('Read [task contracts](references/task-contracts.md) when creating a structured or design-intensive plan...') and again in a References section with a one-line 'read for' purpose, plus the guard note 'Select the current decision; these are not additional mandatory phases.' This matches the clear-overview, well-signaled one-level-deep 5 anchor; the ../sibling-skill links are cross-family navigation, not nested bundle references.

5 / 5

Total

19

/

20

Passed

Description

83%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 strong description: explicit third-person 'what' with a concrete 'Use when' clause carrying three distinct trigger scenarios, and a clearly bounded coordination/resumption niche. The only weaknesses are mild abstraction in the 'what' ('substantial work') and a few missing natural synonyms in the trigger vocabulary.

DimensionReasoningScore

Specificity

The description lists several specific actions — 'decomposing work, resuming a tracked effort, or revising a plan after evidence changes its premises' — plus 'Reuse the active environment's work record and authorization', matching the 'several specific actions; minor gaps' anchor. It falls short of 5 because the actions stay at the coordination level ('coordinate substantial work') rather than the concrete artifact-level operations of the 5 anchor, and it clearly exceeds the 1-2-action scope of 3.

4 / 5

Completeness

It explicitly answers both: what ('Coordinate substantial work with multiple outcomes, dependencies, handoffs, or durable checkpoints... Reuse the active environment's work record and authorization') and when ('Use when decomposing work, resuming a tracked effort, or revising a plan after evidence changes its premises'). The 'when' clause carries three concrete trigger phrases, making it more explicit than the 4 anchor's example, so anti-drift confirms 5 over 4.

5 / 5

Trigger Term Quality

It includes natural planning terms users would say — 'decomposing work', 'resuming a tracked effort', 'revising a plan', 'dependencies', 'handoffs' — giving good keyword coverage. Not 5 because common synonyms like 'break down', 'project', or 'milestone' are missing and 'durable checkpoints' is jargon users would not naturally say; above 3 since several genuinely natural trigger phrases are present.

4 / 5

Distinctiveness Conflict Risk

The description carves a distinct coordination/resumption niche ('durable checkpoints', 'resuming a tracked effort', 'revising a plan after evidence changes its premises'), but the skill's own references to closely related planning skills (task-breakdown, writing-plans) indicate minor overlap risk for generic 'plan this work' requests. This matches 'mostly distinct; minor overlap risk' rather than the clear-niche 5 or the still-overlapping 3.

4 / 5

Total

17

/

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.

Validation — 15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

relative_links

Relative link issues: 4 suspicious

Warning

Total

15

/

16

Passed

Repository

slurpyb/pi-taskfile

Path

.agents/references/agent/ref.kjhwrSP2/SKILL.md

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.