writing-clearly-and-concisely
Use when writing prose humans will read—documentation, commit messages, error messages, explanations, reports, or UI text. Applies Strunk's timeless rules for clearer, stronger, more professional writing.
88
83%
Does it follow best practices?
Impact
96%
1.01xAverage score across 3 eval scenarios
Passed
No known issues
Quality
Discovery
82%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 is a solid description with explicit 'Use when' guidance and good trigger term coverage across multiple content types. The main weakness is the lack of specific concrete actions—it says it applies Strunk's rules but doesn't explain what that means in practice (e.g., 'eliminates passive voice', 'removes unnecessary words'). The broad scope also creates some overlap risk with other writing-related skills.
Suggestions
Add 2-3 specific actions that describe what Strunk's rules actually do, e.g., 'Eliminates passive voice, removes unnecessary words, tightens sentence structure'
Consider narrowing the scope or adding distinguishing details to reduce overlap with other writing/editing skills
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (prose writing) and lists several types of content (documentation, commit messages, error messages, explanations, reports, UI text), but doesn't describe concrete actions—only mentions 'Applies Strunk's timeless rules' without specifying what those rules do. | 2 / 3 |
Completeness | Explicitly answers both what ('Applies Strunk's timeless rules for clearer, stronger, more professional writing') and when ('Use when writing prose humans will read—documentation, commit messages, error messages, explanations, reports, or UI text'). | 3 / 3 |
Trigger Term Quality | Includes natural keywords users would say: 'documentation', 'commit messages', 'error messages', 'explanations', 'reports', 'UI text', 'writing', 'prose'. These are terms users naturally use when requesting help with written content. | 3 / 3 |
Distinctiveness Conflict Risk | While it specifies 'Strunk's rules' as a differentiator, the broad scope of 'prose humans will read' could overlap with other writing, editing, or documentation skills. The reference to Strunk helps but doesn't fully eliminate conflict risk. | 2 / 3 |
Total | 10 / 12 Passed |
Implementation
85%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a well-structured skill that efficiently teaches writing principles without over-explaining. Its main strength is the progressive disclosure strategy with token-counted reference files. The primary weakness is the lack of concrete before/after examples demonstrating the rules in action, which would make the guidance more immediately actionable.
Suggestions
Add 2-3 concrete before/after examples showing transformations (e.g., passive→active voice, verbose→concise) to make the rules immediately actionable
Include a brief example of the subagent dispatch pattern mentioned in the Limited Context Strategy section
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is lean and efficient, assuming Claude's competence. It provides rules as numbered lists without over-explaining concepts Claude already knows, and appropriately defers detailed explanations to reference files. | 3 / 3 |
Actionability | Provides clear rules and anti-patterns to avoid, but lacks concrete before/after examples showing the rules applied. The guidance is specific but not fully executable—telling what to do without showing transformations. | 2 / 3 |
Workflow Clarity | The limited context strategy provides a clear 3-step workflow for applying the skill. The overall structure (when to use, how to apply, what to reference) creates an unambiguous process for a writing/editing task. | 3 / 3 |
Progressive Disclosure | Excellent structure with a concise overview, clear table of reference files with token counts, and one-level-deep references. The recommendation to use only one file for most tasks demonstrates thoughtful organization. | 3 / 3 |
Total | 11 / 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.
Validation — 11 / 11 Passed
Validation for skill structure
No warnings or errors.
- Repository
- softaworks/agent-toolkit
- Commit
3027f20
- 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.