tessl install https://github.com/softaworks/agent-toolkit --skill writing-clearly-and-conciselygithub.com/softaworks/agent-toolkit
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.
Average Score
86%
Content
85%
Description
82%
Generated
Validations
Total score
14/16| Criteria | Score |
|---|---|
skill_md_line_count SKILL.md line count is 94 (<= 500) | |
frontmatter_valid YAML frontmatter is valid | |
name_field 'name' field is valid: 'writing-clearly-and-concisely' | |
description_field 'description' field is valid (204 chars) | |
description_voice 'description' uses third person voice | |
description_trigger_hint Description includes an explicit trigger hint | |
compatibility_field 'compatibility' field not present (optional) | |
allowed_tools_field 'allowed-tools' field not present (optional) | |
metadata_version 'metadata' field is not a dictionary | |
metadata_field 'metadata' field not present (optional) | |
license_field 'license' field is missing | |
frontmatter_unknown_keys No unknown frontmatter keys found | |
body_present SKILL.md body is present | |
body_examples Examples detected (code fence or 'Example' wording) | |
body_output_format Output/return/format terms detected | |
body_steps Step-by-step structure detected (ordered list) |
Content
Suggestions 2
Total score
11/12| Dimension | 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 uses a table for quick reference to external files with token counts. | 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—no demonstration of transforming bad prose to good prose. | 2/3 |
workflow_clarity For a writing skill, the workflow is clear: write draft, optionally dispatch subagent with relevant section file, apply rules. The 'Limited Context Strategy' provides explicit steps, and the skill clearly indicates which file to use for most tasks. | 3/3 |
progressive_disclosure Excellent structure with a concise overview, clear table pointing to one-level-deep reference files with token counts, and explicit guidance that 'most tasks need only' one specific file. Navigation is well-signaled and organized. | 3/3 |
Suggestions
Add 2-3 concrete before/after examples showing rules applied (e.g., passive→active voice transformation, removing puffery from a sentence)
Include a brief example of the subagent dispatch pattern mentioned in the Limited Context Strategy section
Overall Assessment
This is a well-structured skill that efficiently communicates writing principles without over-explaining. Its main strength is excellent progressive disclosure with clear pointers to reference files and token budgets. The primary weakness is limited actionability—while rules are listed clearly, concrete before/after examples demonstrating their application would make the skill more immediately useful.
Description
Suggestions 2
Total score
10/12| Dimension | 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') with a clear 'Use when...' clause at the start. | 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 'prose humans will read' and references Strunk's rules, the broad scope (documentation, commit messages, error messages, etc.) could overlap with other writing-focused skills or style guides. The Strunk reference adds some distinctiveness but isn't a strong differentiator. | 2/3 |
Suggestions
Add 2-3 specific actions that describe what the skill does, e.g., 'Eliminates passive voice, removes unnecessary words, tightens sentences'
Consider narrowing scope or adding more distinctive triggers to reduce potential overlap with other writing/style skills
Overall Assessment
This is a solid description with a clear 'Use when...' clause 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 enumerate what those rules actually do (e.g., 'eliminates passive voice', 'removes unnecessary words', 'tightens sentences').