CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

paperclip-converting-plans-to-tasks

Decide whether Paperclip work needs delegation, and connect justified tasks with owners and real dependencies. Use when turning an authorized plan into work.

Quality

78%

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 ./skills/paperclip-converting-plans-to-tasks/SKILL.md
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.

This is a tight, instruction-only skill: every sentence drives a decision, concrete mechanics (field names, link formats, verification) are embedded, and the length is right-sized with no bundle files needed. The only room for improvement is naming the actual task-creation tool/command and tightening a few abstract directives.

DimensionReasoningScore

Conciseness

Every line is operative guidance with zero padding — no explanations of concepts Claude already knows, and justifications are compressed to single clauses like "People read these descriptions". Matches the lean anchor exactly.

5 / 5

Actionability

Concrete, executable specifics are given — the field name `blockedByIssueIds`, a copy-paste link format example `[BRA-2](/BRA/issues/BRA-2#document-plan)`, and "Check the available agents before assigning" — but some directives stay abstract ("Give each delegate enough context and a clear deliverable") and the actual task-creation mechanism is never named.

4 / 5

Workflow Clarity

A coherent implicit sequence runs from default handling to delegation, dependencies, and an explicit checkpoint ("Verify the saved relationships"), and this is not a destructive or batch operation so no cap applies. Minor gaps: steps are unnumbered and the reviewer flow lacks its own verification step, keeping it below anchor 5.

4 / 5

Progressive Disclosure

Under 50 lines, single purpose, no external references needed — the simple-skill exception applies, and the short well-organized prose under a clear title is appropriately structured with nothing inlined that belongs in a separate file.

5 / 5

Total

18

/

20

Passed

Description

62%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 answers both what and when explicitly and is well-scoped to a distinct niche, but its action list is thin and its trigger vocabulary lacks natural synonyms. Adding one or two more concrete actions and more natural trigger phrasing would lift it to the top band.

Suggestions

Add 1-2 more concrete actions to round out coverage, e.g. mentioning how dependencies are recorded or that reviewers publish verdicts on their own tasks.

Broaden trigger terms with natural user phrasings such as "break down a plan", "split work into tasks", or "assign tasks to owners" in the 'Use when' clause.

Make the 'when' clause more concrete about the entry point, e.g. "Use when an approved plan needs to be turned into tracked, assignable tasks".

DimensionReasoningScore

Specificity

Names the domain (Paperclip delegation) with two concrete actions — "decide whether Paperclip work needs delegation" and "connect justified tasks with owners and real dependencies" — but coverage is not comprehensive (no mention of task creation, deliverables, or dependency mechanics).

3 / 5

Completeness

Both parts are present: a clear "what" (decide delegation, connect tasks with owners and dependencies) and an explicit "Use when turning an authorized plan into work" clause. The "when" is explicit but could use more concrete, natural trigger phrases, so it falls short of anchor 5.

4 / 5

Trigger Term Quality

Relevant keywords like "plan", "tasks", and "delegation" appear, but common variations users would naturally say ("break down", "split", "assign", "subtasks") are missing, and the trigger phrase "turning an authorized plan into work" is somewhat stilted.

3 / 5

Distinctiveness Conflict Risk

Scoping to "Paperclip" and to the plan-to-task delegation niche makes it mostly distinct, but generic words like "plan", "tasks", and "dependencies" leave minor overlap risk with general planning or task-management skills.

4 / 5

Total

14

/

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: 1 suspicious

Warning

Total

15

/

16

Passed

Repository

paperclipai/paperclip

Path

skills/paperclip-converting-plans-to-tasks/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.