writing-clearly-and-concisely

Apply Strunk's timeless writing rules to ANY prose humans will read—documentation, commit messages, error messages, explanations, reports, or UI text. Makes your writing clearer, stronger, and more professional.

1.02x

Quality

—

Does it follow best practices?

Impact

94%

1.02x

Average score across 3 eval scenarios

Securityby

Passed

No known issues

Quality

Content

42%

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

The skill is well-organized and token-conscious, but its central progressive-disclosure promise is unfulfilled: `elements-of-style.md` is referenced throughout yet not bundled, and the rule detail that belongs in that reference is inlined instead.

Suggestions

Bundle the referenced `elements-of-style.md` under references/ — it is cited repeatedly in the body but does not exist anywhere in the skill.

Move the inlined "All Rules" list into `elements-of-style.md` and keep SKILL.md as a concise overview that links to it.

Add a concrete before/after example of applying one rule (e.g., active voice) so the inline guidance is actionable even before the reference is loaded.

Dimension	Reasoning	Score
Conciseness	The body is mostly lean with a token-aware warning, but the "All Rules" section restates Strunk's well-known maxims that Claude already knows and duplicates content presumably held in `elements-of-style.md`.	2 / 3
Actionability	It gives a concrete subagent-dispatch workflow and clear use-cases, but the core instruction ("Read `elements-of-style.md`") depends on a file that is not bundled, and the inline rules are abstract maxims with no before/after examples.	2 / 3
Workflow Clarity	The limited-context subagent dispatch is a clear 3-step sequence and the main action is unambiguous, but the primary workflow relies on the non-bundled `elements-of-style.md` and offers no verification that revisions actually improved clarity.	2 / 3
Progressive Disclosure	The body is organized into clear sections and clearly signals a one-level reference (`elements-of-style.md`), but that file is absent from references/scripts/assets and the "All Rules" detail that should live in it is inlined, so the progressive-disclosure structure is broken.	1 / 3
	Total	7 / 12 Passed

Description

50%

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 concrete and domain-rich but uniformly lands at the mid-level: it states what the skill does well yet never gives an explicit "Use when..." trigger, and its second-person voice and breadth limit specificity and distinctiveness.

Suggestions

Add an explicit "Use when..." trigger clause (e.g., "Use when writing or editing prose for humans—documentation, commits, error messages, UI text, or reports") to raise completeness above 2.

Rewrite in third person ("Apply" → "Applies", "your writing" → "the prose") to avoid the specificity penalty for second-person voice.

Add trigger-term variations users commonly say (READMEs, release notes, comments, copywriting) to improve trigger-term coverage.

Dimension	Reasoning	Score
Specificity	The description lists multiple concrete prose domains ("documentation, commit messages, error messages, explanations, reports, or UI text") and outcomes ("clearer, stronger, and more professional"), but uses second-person voice ("Apply", "your writing"), which per the guidelines reduces specificity by one from a base of 3.	2 / 3
Completeness	It clearly answers what ("Apply Strunk's timeless writing rules to ANY prose... Makes your writing clearer") but only implies when via the domain list; there is no explicit "Use when..." clause, which caps completeness at 2 per the guidelines.	2 / 3
Trigger Term Quality	It includes several natural keywords users would say ("commit messages", "documentation", "error messages", "UI text"), but lacks an explicit "Use when..." framing and omits common variations such as READMEs, release notes, comments, or copywriting.	2 / 3
Distinctiveness Conflict Risk	The Strunk framing gives it a recognizable niche, but "ANY prose humans will read" is broad enough to overlap with general writing or editing skills, so it is not yet a clearly distinct, conflict-free trigger set.	2 / 3
	Total	8 / 12 Passed

Validation

93%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
metadata_version	'metadata.version' is missing	Warning

	Total	15 / 16 Passed

Repository: Dicklesworthstone/pi_agent_rust
Commit: abece4a

Reviewed: 4 days ago

Table of Contents

Discovery Implementation Validation

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.