papercut

Capture or triage small Neva repository and engineering-harness frictions without derailing feature work.

Quality

76%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./.codex/skills/papercut/SKILL.md

Quality

Content

100%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 model of lean, actionable instruction design: a copy-paste entry template, clearly sequenced capture/triage phases, an explicit verification gate, and well-signaled scope guardrails. No bundle files are present or needed.

Dimension	Reasoning	Score
Conciseness	The ~38-line body is lean and efficient with no padding and no explanation of concepts Claude already knows; every line (capture template, triage steps, scope guardrails) earns its place.	5 / 5
Actionability	A copy-paste-ready journal entry template (with timestamp/author header and "what I was doing -> what got in the way" prompt) plus concrete numbered triage steps give fully actionable guidance for an instruction-only skill.	5 / 5
Workflow Clarity	Capture and Triage are clearly sequenced with an explicit verification gate ("Reproduce or otherwise verify each candidate before assigning a cause") and a guard ("Leave unverified entries intact"); the simple-skill exception applies.	5 / 5
Progressive Disclosure	Under 50 lines with well-organized ## Capture / ## Triage sections and a single clearly-signaled one-level reference to .codex/papercuts.md; no bundle files are needed, so the simple-skill exception yields a 5.	5 / 5
	Total	20 / 20 Passed

Description

53%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 states the skill's purpose in lean, third-person voice but omits an explicit "Use when..." trigger clause and the natural trigger phrases that would help it surface at the right moment. Adding concrete trigger terms would lift completeness and trigger_term_quality.

Suggestions

Append an explicit trigger clause, e.g. "Use when a person or agent hits a flaky command, stale cache, misleading error, obsolete script, or docs that contradict observed behavior during other Neva work."

Surface concrete trigger keywords (flaky command, stale cache, misleading error, obsolete script) in the description itself rather than only in the body, so the skill matches natural user phrasing.

Add a one-level "what" enumeration (capture an entry / triage and convert to a durable outcome) to nudge specificity from 3 toward 4-5.

Dimension	Reasoning	Score
Specificity	"Capture or triage" names two concrete verbs and the domain ("small Neva repository and engineering-harness frictions"), matching the anchor for 1-2 concrete actions without comprehensive coverage.	3 / 5
Completeness	The description gives a clear "what" but no "Use when..." trigger clause; the explicit-trigger guidance cap of 3 applies since "when" is only weakly implied by "without derailing feature work".	3 / 5
Trigger Term Quality	"frictions" is a relevant keyword, but the natural phrases users would actually say (e.g. "flaky command", "stale cache") appear only in the body, not the description, so common variations are missing.	3 / 5
Distinctiveness Conflict Risk	The Neva-scoped "small frictions" niche is mostly distinct with only minor overlap risk against general issue-tracking skills, though the absence of explicit triggers keeps it just short of a 5.	4 / 5
	Total	13 / 20 Passed

Validation

93%

Warnings & errors only

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

Criteria	Description	Result
relative_links	Relative link issues: 1 suspicious	Warning

	Total	15 / 16 Passed

Repository: nevalang/neva
Path: .codex/skills/papercut/SKILL.md
Commit: 127afd9

Reviewed: 4 hours ago

Table of Contents

Discovery Implementation Validation

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.