CtrlK
BlogDocsLog inGet started
Tessl Logo

papercuts

Log genuine, recurring repository friction to .agents/PAPERCUTS.md — confusing setup, a flaky repo command or script, a misleading in-repo error, stale generated files, or a non-obvious gotcha that will cost the next contributor time. Also use to review, deduplicate, and resolve existing entries. Gate hard before logging: only friction the repository itself can fix counts. Never log the agent's own sandbox/permission errors, shell-scripting mistakes, transient flakiness, or third-party tool quirks the repo can't change.

65

Quality

80%

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 ./.agents/skills/papercuts/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

85%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 tight, well-structured instruction skill with concrete logging/review workflows, explicit validation gates, and clear organization; only minor gains are available from a worked example and trimming light redundancy.

DimensionReasoningScore

Conciseness

Lean and direct with no padding about concepts Claude already knows, but the two-question test is restated negatively in 'Do NOT log' and then again in the closing 'is this the repo, or is this me?' line, which could be tightened.

4 / 5

Actionability

Gives a concrete copy-paste entry template, a specific file path, and concrete numbered steps for both logging and review; the minor gap is the absence of a filled-in worked example showing a real papercut entry.

4 / 5

Workflow Clarity

Both workflows are clearly sequenced with explicit validation checkpoints — the two-question test acts as a logging gate, review step 1 re-runs it and deletes failures, and step 3 verifies reproduction before resolving — satisfying the destructive/batch validation requirement.

5 / 5

Progressive Disclosure

A single well-organized file with clear section headers (two-question test, Do NOT log, Log proactively, Review or resolve) and easy in-file navigation; the skill is single-purpose with no need for external references.

5 / 5

Total

18

/

20

Passed

Description

75%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 specific, distinctive description that clearly states what the skill does, but it omits an explicit 'Use when...' trigger clause, leaving the invocation conditions only weakly implied.

Suggestions

Add an explicit 'Use when...' clause naming the natural trigger phrases (e.g. 'Use when you hit confusing setup, a flaky repo command, stale generated files, or a non-obvious gotcha worth recording for the next contributor').

Surface the word 'papercut' itself as a trigger term in the description, since that is the natural vocabulary a user would reach for.

Trim the gating/exclusion sentence ('Gate hard before logging...') which belongs in the body, and replace it with forward-looking trigger guidance to strengthen the 'when' half of the description.

DimensionReasoningScore

Specificity

Names several concrete actions tied to a specific artifact — 'Log... friction to .agents/PAPERCUTS.md', 'review, deduplicate, and resolve existing entries' — with comprehensive coverage of what the skill does.

5 / 5

Completeness

The 'what' is clear (log/review/dedupe/resolve repo friction), but there is no explicit 'Use when...' clause; the 'when' is only weakly implied through the friction examples and gating sentence, which per the guidelines caps completeness at 3.

3 / 5

Trigger Term Quality

Includes natural user phrases like 'friction', 'gotcha', 'flaky repo command', 'confusing setup', and 'stale generated files', but is missing some common variations users might actually say (e.g. 'papercut', 'annoying setup step').

4 / 5

Distinctiveness Conflict Risk

Occupies a clear niche (logging fixable repo friction to a specific file) with distinct triggers and an explicit exclusion philosophy, giving minimal conflict risk with other skills.

5 / 5

Total

17

/

20

Passed

Validation

87%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

metadata_version

'metadata.version' is missing

Warning

metadata_field

'metadata' should map string keys to string values

Warning

Total

14

/

16

Passed

Repository
every-app/open-seo
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.