CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

cw-dev-edit

Review a draft for big-picture issues in argument, structure, stakes, evidence, and payoff. Use when a piece needs developmental editing, a top-level diagnosis, or substantial restructuring before sentence polish.

Quality

83%

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

75%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 well-structured, actionable instruction skill: tables for review areas and evidence verdicts, two named diagnostic tests with numbered steps, and ready-to-use output templates. It is held at 4 across dimensions by the empty Lessons placeholder, the dangling context-contract reference, and the lack of a worked example.

Suggestions

Remove or populate the empty 'Lessons' placeholder section to stop it from consuming tokens for no content.

DimensionReasoningScore

Conciseness

Largely lean and table-driven with no padding of concepts Claude already knows, but the empty 'Lessons' placeholder and some redundancy between the prose intros and the 'When invoked by the agent' step lists could be trimmed.

4 / 5

Actionability

Provides concrete, copy-paste-ready output templates (Full Report, Quick Assessment) with severity levels, a verdict table for evidence, and numbered procedural steps for each structural test; falls short of 5 only because there is no worked example applying a test to a real draft.

4 / 5

Workflow Clarity

The review flow (load context, inspect areas, run structural tests, evidence check, produce report, collaborative fixing loop) is well sequenced with numbered steps and an explicit repeat loop, but the top-level sequence is assembled from sections rather than stated as one explicit ordered checklist.

4 / 5

Progressive Disclosure

A self-contained, well-sectioned instruction skill with clear headers and easy navigation; no bundle files exist to split further, and the only external reference (../../references/context-contract.md) is a dangling project-context path rather than a bundled file, a minor organization gap.

4 / 5

Total

16

/

20

Passed

Description

83%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 is strong: third-person voice, explicit 'Use when...' trigger, and a clear what/when split covering concrete review dimensions. Minor gaps in action comprehensiveness and synonym coverage keep it just below perfect.

Suggestions

Add one or two natural synonyms (e.g., 'feedback', 'critique', 'structure review') to broaden trigger coverage.

Consider naming one more concrete action (e.g., 'flag unsupported claims') to lift specificity toward comprehensive coverage.

DimensionReasoningScore

Specificity

Names the domain ('big-picture issues in argument, structure, stakes, evidence, and payoff') and several concrete actions ('top-level diagnosis', 'substantial restructuring', 'developmental editing'), but the actions are review categories rather than a comprehensive list of discrete operations.

4 / 5

Completeness

Explicitly answers what ('Review a draft for big-picture issues in argument, structure, stakes, evidence, and payoff') and when ('Use when a piece needs developmental editing, a top-level diagnosis, or substantial restructuring before sentence polish') with concrete trigger phrases.

5 / 5

Trigger Term Quality

Includes natural editor-facing phrases ('developmental editing', 'top-level diagnosis', 'substantial restructuring', 'before sentence polish') a user would plausibly say, though it omits common synonyms like 'feedback', 'critique', or 'outline review'.

4 / 5

Distinctiveness Conflict Risk

The 'developmental editing' / 'before sentence polish' framing carves a clear niche apart from line/copy editing, but it could still overlap with adjacent review skills (nemesis read, objections, line edit) mentioned in the body.

4 / 5

Total

17

/

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.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

EveryInc/compound-writing

Path

skills/cw-dev-edit/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.