CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

diagnose-why-work-stopped

Compatibility entry point for failed, stalled, looping, or over-recovered Paperclip work. Use fix-failed-paperclip-run for the full diagnosis, regression, repair, real verification, and green-PR workflow; honor an explicitly requested diagnosis-only scope.

Quality

71%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./.agents/skills/diagnose-why-work-stopped/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

65%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 lean, well-structured redirect skill that delegates the main workflow cleanly and adds genuine value through its scope carve-out, classification taxonomy, and invariants. Its weaknesses are in the diagnosis guidance itself: key directives are abstract without examples or methods, and the diagnosis path lacks an explicit sequence with checkpoints.

Suggestions

Add a brief concrete example of a "general behavioral contract" repair frame and what checking it against a "productive counterexample" looks like in practice.

Sequence the diagnosis-only path as explicit steps (inspect subtree and recent repairs -> classify each non-progressing node -> route by classification) with a checkpoint such as confirming the classification before proposing any repair.

Name a concrete method or command for "inspect the relevant subtree and recent repairs" so the investigation step is executable rather than descriptive.

DimensionReasoningScore

Conciseness

The ~30-line body is dense with no padding and no explanation of concepts Claude already knows; every section carries substantive guidance. Not 5 because a few sentences ("Historical task links and private incident access are not required", the plan-approval-gate sentence) could be trimmed or tightened.

4 / 5

Actionability

Concrete elements exist (explicit link to the owning skill, enumerated workflow steps, a three-way classification with definitions, numbered invariants), but several directives are unexecutable as written — "Frame any repair as a general behavioral contract, check it against a productive counterexample" has no example, and "inspect the relevant subtree" names no method or command. This is anchor 3: some concrete guidance but incomplete.

3 / 5

Workflow Clarity

The delegated workflow is enumerated with embedded validation language ("reproduce it red", "verify the real workflow", "green-PR"), but the skill's own diagnosis path presents a classification taxonomy without a sequenced procedure or explicit checkpoints, and the scope branch (diagnosis-only vs. full) is stated as a rule rather than a decision step. Sequence is present but checkpoints are implicit in the diagnosis path — anchor 3.

3 / 5

Progressive Disclosure

The skill is under 50 lines with no bundle files (no references/, scripts/, or assets/), and the body is a clear overview with a single well-signaled one-level-deep link to the owning skill ([Fix Failed Paperclip Run](../fix-failed-paperclip-run/SKILL.md)) and well-organized sections. The simple-skill exception applies: nothing that belongs elsewhere is inlined.

5 / 5

Total

15

/

20

Passed

Description

66%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 concise, reasonably specific redirect description that clearly states its role and relationship to the owning skill, with good natural trigger terms for failure states. Its main weakness is the absence of an explicit "Use when..." trigger clause, which caps completeness, and its trigger conditions overlap heavily with the sibling skill it defers to.

Suggestions

Add an explicit trigger clause, e.g. "Use when Paperclip work has failed, stalled, looped, or over-recovered" to answer "when" directly.

Include common user phrasings like "stuck" or "blocked" alongside failed/stalled/looping to broaden natural trigger coverage.

State the entry point's own concrete action first (route to the owning skill) before enumerating the delegated workflow's actions.

DimensionReasoningScore

Specificity

Lists several concrete actions ("full diagnosis, regression, repair, real verification, and green-PR workflow") plus its own role as a "Compatibility entry point" that honors a "diagnosis-only scope". Not 5 because the enumerated actions belong to the delegated skill and the entry point's own behavior is only minimally described.

4 / 5

Completeness

The "what" is clear (compatibility entry point delegating to fix-failed-paperclip-run), but there is no "Use when..." clause or equivalent explicit trigger guidance — the states "failed, stalled, looping" only weakly imply when to use it, which caps completeness at 3 per the judging guidelines.

3 / 5

Trigger Term Quality

"failed, stalled, looping, over-recovered, Paperclip work" gives good natural-keyword coverage of failure states a user would actually say. Not 5 because common variations like "stuck", "blocked", or "not progressing" are missing; not 3 since multiple distinct natural trigger terms are present rather than just some.

4 / 5

Distinctiveness Conflict Risk

The description carves a clear niche ("Compatibility entry point") and explicitly routes to the sibling skill ("Use fix-failed-paperclip-run for the full... workflow"), but its trigger surface overlaps almost entirely with that closely related skill, keeping it at anchor 4 rather than 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

relative_links

Relative link issues: 1 suspicious

Warning

Total

15

/

16

Passed

Repository

paperclipai/paperclip

Path

.agents/skills/diagnose-why-work-stopped/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.