CtrlK
BlogDocsLog inGet started
Tessl Logo

prose

Apply Strunk's writing rules to prose—documentation, commits, error messages, UI text. Clearer, stronger, more professional. Also handles sharpening and tightening drafts by subtraction.

84

Quality

80%

Does it follow best practices?

Impact

Pending

No eval scenarios have been run

SecuritybySnyk

Passed

No known issues

Optimize this skill with Tessl

npx tessl skill review --optimize ./skills/prose/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Discovery

60%

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

This description effectively communicates specific capabilities and target content types, with the Strunk's reference providing useful context. However, it lacks an explicit 'Use when...' clause which limits Claude's ability to know exactly when to select this skill. The trigger terms could be expanded to include more natural user phrasings.

Suggestions

Add an explicit 'Use when...' clause with trigger phrases like 'when user asks to edit writing, improve prose, make text concise, or apply style guidelines'

Include more natural trigger terms users might say: 'edit', 'revise', 'tighten', 'concise', 'wordy', 'verbose', 'writing style'

DimensionReasoningScore

Specificity

Lists multiple concrete actions: 'Apply Strunk's writing rules', 'sharpening and tightening drafts by subtraction', and specifies target content types: 'documentation, commits, error messages, UI text'.

3 / 3

Completeness

Clearly answers 'what' (apply Strunk's rules, sharpen/tighten drafts) but lacks an explicit 'Use when...' clause. The 'when' is only implied through the content types listed.

2 / 3

Trigger Term Quality

Includes some natural terms like 'documentation', 'commits', 'error messages', 'UI text', 'drafts', but missing common variations users might say like 'edit my writing', 'improve prose', 'make it concise', 'writing style'.

2 / 3

Distinctiveness Conflict Risk

The Strunk's rules reference provides some distinctiveness, but 'sharpening drafts' and 'clearer, stronger' language could overlap with general writing/editing skills. The specific mention of commits and error messages helps differentiate somewhat.

2 / 3

Total

9

/

12

Passed

Implementation

100%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

This is an exemplary skill file that demonstrates excellent conciseness while remaining highly actionable. It provides concrete rules, a practical LLM-ism catalog with specific fixes, and clear workflows for both writing and editing. The progressive disclosure is well-executed with appropriate warnings about token costs and clear navigation to related resources.

DimensionReasoningScore

Conciseness

The skill is lean and efficient, assuming Claude's competence. It doesn't explain what Strunk's Elements of Style is beyond necessary context, and every section serves a clear purpose. The LLM-ism catalog is dense but earns its place as actionable reference.

3 / 3

Actionability

Provides concrete, executable guidance throughout: specific rules numbered and bolded for emphasis, a detailed LLM-ism catalog with examples and fixes, a clear 4-step sharpening workflow, and a practical subagent dispatch strategy for limited context.

3 / 3

Workflow Clarity

The sharpening workflow is clearly sequenced with explicit steps (read, cut, scan, verify). The limited context strategy provides a clear 3-step process. The 'test' at the end serves as a validation checkpoint for editing decisions.

3 / 3

Progressive Disclosure

Excellent structure with clear overview, well-organized sections, and appropriate references to external files (elements-of-style.md, RECIPE.md, related skills). The warning about token consumption is a thoughtful touch. References are one level deep and clearly signaled.

3 / 3

Total

12

/

12

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.

Validation11 / 11 Passed

Validation for skill structure

No warnings or errors.

Repository
tslateman/duet
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.