CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

cw-scribe

Route open-ended writing work through the smallest useful Compound Writing workflow. Use when the user wants to start, continue, finish, or improve a piece and has not named a more specific skill.

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

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-structured, lean router skill with concrete routing decisions and a clear start sequence; its main weakness is a dangling reference to a context-contract.md file that is not present in the bundle, which undermines its progressive-disclosure navigation.

Suggestions

Add the missing ../../references/context-contract.md file (or correct the path) so the 'Read before substantial work' instruction resolves to a real document.

Include one short worked example walking a representative request end-to-end through the route table to lift actionability from concrete guidance to fully executable.

Tighten the repeated destination/resolution rules across 'Find The Writer's Starting Point' and 'Artifacts And Progress' to remove the minor redundancy that keeps conciseness at 4.

DimensionReasoningScore

Conciseness

Dense directive prose that assumes Claude's competence ('The user came to write, not admire the plumbing') with no concept padding; a few sentences restate destination/resolution rules across sections and could be trimmed.

4 / 5

Actionability

Concrete routing to named skills (cw-setup-project, cw-onboarding, cw-dev-edit) and named paths (drafts/<piece-slug>/, VOICE.md, STYLE.md) plus a state-to-route table; as an instruction-only skill it lacks a worked end-to-end example, leaving minor gaps.

4 / 5

Workflow Clarity

The numbered 'Start The Work' sequence and gating rule ('Ask a question only when a missing answer would materially change the work') give a clear sequence with most checkpoints present; no explicit validate-fix-retry loop, but the routing nature of the skill does not require one.

4 / 5

Progressive Disclosure

In-body structure is well organized into clear sections and a routing table, but the single signaled external reference ('Read ../../references/context-contract.md before substantial work') does not exist and no references/ directory is present, so the one-level-deep navigation it depends on is broken.

3 / 5

Total

15

/

20

Passed

Description

87%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 description that cleanly answers both what and when, uses natural trigger verbs, and explicitly scopes itself as a fallback router to avoid conflicting with more specific skills. Its only weakness is that the concrete actions are meta-level (route, start, finish, improve) rather than operational specifics.

DimensionReasoningScore

Specificity

Names the domain (Compound Writing workflow) and several concrete actions ('route open-ended writing work', 'start, continue, finish, or improve a piece'); gaps are minor and the actions are high-level for a router skill rather than operational file-ops.

4 / 5

Completeness

Explicitly states both what ('Route open-ended writing work through the smallest useful Compound Writing workflow') and when ('Use when the user wants to start, continue, finish, or improve a piece') with concrete trigger phrases.

5 / 5

Trigger Term Quality

Natural writer phrases ('start, continue, finish, or improve a piece') match what users would say; a few common synonyms (draft, revise, edit) are missing, keeping it just below comprehensive.

4 / 5

Distinctiveness Conflict Risk

The 'has not named a more specific skill' clause explicitly disambiguates its router niche within the Compound Writing family, giving it clear distinct triggers and minimal conflict risk.

5 / 5

Total

18

/

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-scribe/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.