CtrlK
BlogDocsLog inGet started
Tessl Logo

cw-reader

Review copy as an intended reader encountering it for the first time, with no access to the writer's unstated context. Identify confusing language, missing setup, assumed knowledge, broken expectations, trust-eroding or off-putting moments, and points where the reader may stop. Use for cold reads, fresh-eyes reviews, first-time-reader perspectives, reader-journey checks, or feedback on what feels confusing, missing, alienating, or hard to follow.

68

Quality

81%

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

71%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 well-organized, instruction-only review skill with concrete diagnostic tools and a clear sequenced workflow. Its main weakness is progressive disclosure: the body references a context-contract file that is absent from the bundle, which weakens navigation even though the skill remains usable via its fallback default-reader guidance.

Suggestions

Resolve the broken reference: either create `references/context-contract.md` (and correct the `../../references/` path to match the bundle layout) or inline the minimal context-contract guidance so the Establish The Reader step is self-contained.

Tighten the Principles section by removing points already covered in Make A Cold Pass and Diagnose The Friction, keeping only principles that add new guidance.

Consider a one-line pointer at the top of the body stating the fallback behavior (read as an uninstructed first-time reader) so the skill's default path is discoverable without depending on the external file.

DimensionReasoningScore

Conciseness

The body is lean and assumes Claude's competence throughout, with no padding or over-explanation of basic concepts; the only minor trim opportunity is that the Principles section partially restates points already made in the Cold Pass and Diagnose sections.

4 / 5

Actionability

It gives concrete, specific guidance — a diagnostic table with exact questions, a tracking checklist, and a copy-paste-structured output template — which is highly actionable for an instruction-only skill; placeholders and reliance on Claude to supply substance keep it just short of fully executable.

4 / 5

Workflow Clarity

The process is clearly sequenced (Establish The Reader → Make A Cold Pass → Diagnose The Friction → Output) with checklist-style track items and a diagnostic table; no validation feedback loop is present, but none is required for a read-only review task that performs no destructive or batch operation.

4 / 5

Progressive Disclosure

Section structure is clean and the skill is largely self-contained, but the single external reference ("Read `../../references/context-contract.md`") points to a file that does not exist in the bundle, undermining navigation and leaving the Establish The Reader step dependent on a missing resource.

3 / 5

Total

15

/

20

Passed

Description

92%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 strong, well-constructed description: it states concrete capabilities, gives explicit use-when trigger phrases, and occupies a distinctive niche. The only minor gap is trigger-term diversity, which leans on a single idiomatic cluster rather than spanning synonyms.

DimensionReasoningScore

Specificity

The description enumerates multiple concrete actions — "Identify confusing language, missing setup, assumed knowledge, broken expectations, trust-eroding or off-putting moments, and points where the reader may stop" — giving comprehensive coverage with no significant gaps.

5 / 5

Completeness

It explicitly answers both what ("Review copy as an intended reader... Identify...") and when ("Use for cold reads, fresh-eyes reviews...") with concrete trigger phrases, matching the top anchor.

5 / 5

Trigger Term Quality

Strong natural trigger phrases appear ("cold reads, fresh-eyes reviews, first-time-reader perspectives, reader-journey checks"), but coverage is clustered around one idiom and misses some common lay synonyms, so it stops short of fully comprehensive.

4 / 5

Distinctiveness Conflict Risk

The cold-read / first-time-reader framing carves a clear niche with distinct triggers and minimal overlap; the body's boundaries section reinforces separation from sibling skills.

5 / 5

Total

19

/

20

Passed

Validation

100%

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

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
EveryInc/compound-writing
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.