CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

task-planning

Write or revise a useful Paperclip plan with a clear outcome and verification. Use when a plan is requested or uncertainty needs resolving before execution.

65

Quality

82%

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

86%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 a lean, well-sequenced instruction set that respects the token budget and gives concrete directives with an explicit approval checkpoint and clear delegation criteria. Its only notable gap is that document-saving mechanics are deferred to the `paperclip` skill without inline examples or a sample plan structure.

DimensionReasoningScore

Conciseness

The ~20-line body ("Plan only as much as the work needs... A request for a plan alone does not require child tasks or a new approval gate") delivers non-obvious judgment calls with zero padding and no explanations of concepts Claude already knows — every token earns its place, matching the lean-and-efficient anchor.

5 / 5

Actionability

Concrete directives such as "Save a requested plan as the issue document with key `plan`. Update its current revision instead of duplicating it, and link the saved document in your response" are mostly executable, but the save mechanics are deferred ("legacy agents follow the `paperclip` skill's document and planning API mechanics") and no sample plan format is shown, leaving minor gaps versus fully copy-paste-ready guidance.

4 / 5

Workflow Clarity

A coherent sequence is present (decide whether to plan, describe contents, save/update the document, approval, execute/delegate) with an explicit checkpoint ("request confirmation of the latest plan revision and wait for that decision"), but the sequence is prose-implicit rather than crisply ordered and there is no guidance for a rejected-plan revision loop, so it sits at anchor 4 rather than 5.

4 / 5

Progressive Disclosure

The skill is under 50 lines with no bundle files and no need for external references; the short paragraphs are logically ordered and cross-references to `paperclip` and `paperclip-converting-plans-to-tasks` are one level deep and clearly signaled, qualifying for the simple-skill exception.

5 / 5

Total

18

/

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 clearly and explicitly states both what the skill does and when to use it, in concise third-person voice. Its main weaknesses are limited action specificity beyond write/revise and thin trigger-term coverage confined to the single "plan" keyword family.

Suggestions

Broaden trigger-term coverage with natural variations users would actually say, such as "planning", "roadmap", or "break down this work", to lift trigger_term_quality beyond one keyword family.

Enumerate more concrete capabilities in the description (e.g., handling approval confirmation, converting plans into delegated tasks) to raise specificity beyond the single write/revise action pair.

Mention the saved artifact (the issue document with key "plan") in the description to sharpen distinctiveness from adjacent Paperclip planning skills.

DimensionReasoningScore

Specificity

"Write or revise a useful Paperclip plan with a clear outcome and verification" names the domain and two actions (write, revise) plus plan-content attributes, but does not list several specific actions, matching the anchor for 1-2 concrete actions rather than the several-action anchor at 4.

3 / 5

Completeness

It explicitly answers both what ("Write or revise a useful Paperclip plan with a clear outcome and verification") and when ("Use when a plan is requested or uncertainty needs resolving before execution") with concrete trigger phrases, matching the anchor-5 example rather than the weaker/explicit-but-imprecise "when" at 4.

5 / 5

Trigger Term Quality

"Use when a plan is requested or uncertainty needs resolving before execution" provides the core natural phrase, but coverage stays within the single "plan" keyword family; common variations users would say (planning, roadmap, break down this work) are missing, matching anchor 3 rather than the good-coverage anchor at 4.

3 / 5

Distinctiveness Conflict Risk

"Paperclip plan" anchors a distinct niche, but "plan"/"planning" is a broad term and closely related sibling skills exist in the same ecosystem (the body references paperclip-converting-plans-to-tasks), so there is minor overlap risk matching anchor 4 rather than minimal conflict risk at 5.

4 / 5

Total

15

/

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

frontmatter_unknown_keys

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

Warning

Total

15

/

16

Passed

Repository

paperclipai/paperclip

Path

packages/skills-catalog/catalog/bundled/paperclip-operations/task-planning/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.