Write with clarity and force. This skill covers what to do (Strunk) and what not to do (AI patterns).
Works with
AI-first code editor with Composer
Before installing skills in Cursor, ensure your development environment meets these requirements:
node --versionwriting-clearly-and-conciselyExecute the skills CLI command in your project's root directory to begin installation:
Fetches writing-clearly-and-concisely from davila7/claude-code-templates and configures it for Cursor.
The CLI shows a list of agents. Use arrow keys and space to select Cursor:
Confirm successful installation by checking the skill directory location:
Restart Cursor to activate writing-clearly-and-concisely. Access via /writing-clearly-and-concisely in your agent's command palette.
We perform automated surface-level scans (Gen AI Scanner, Socket, Snyk) during installation. These checks detect common vulnerabilities but do not guarantee complete security. Always review skill source code and verify the publisher's reputation before production use.
Skills execute code in your environment. Always review source, verify the publisher, and test in isolation before production.
Submit your Claude Code skill and start earning
Create detailed user stories, acceptance criteria, and feature specs
Example
Generate user stories for 'password reset feature' with acceptance criteria, edge cases, and test scenarios
Reduce spec writing time by 50%, ensure comprehensive coverage
Research competitors, compare features, identify gaps
Example
Analyze 5 competitor products, create feature comparison matrix, suggest differentiation opportunities
Complete competitive research in 2 hours instead of 2 days
Evaluate features using frameworks (RICE, ICE, Kano) and create prioritized backlogs
Example
Score 20 feature ideas using RICE framework, generate prioritized roadmap with rationale
1
total installs
1
this week
24.2K
GitHub stars
0
upvotes
Run in your terminal
1
installs
1
this week
24.2K
stars
Write with clarity and force. This skill covers what to do (Strunk) and what not to do (AI patterns).
Use this skill whenever you write prose for humans:
If you're writing sentences for a human to read, use this skill.
When context is tight:
Loading a single section (~1,000-4,500 tokens) instead of everything saves significant context.
William Strunk Jr.'s The Elements of Style (1918) teaches you to write clearly and cut ruthlessly.
Elementary Rules of Usage (Grammar/Punctuation):
Elementary Principles of Composition:
The rules above are summarized from Strunk's original text. For complete explanations with examples:
| Section | File | ~Tokens |
|---|---|---|
| Grammar, punctuation, comma rules | 02-elementary-rules-of-usage.md |
2,500 |
| Paragraph structure, active voice, concision | 03-elementary-principles-of-composition.md |
4,500 |
| Headings, quotations, formatting | 04-a-few-matters-of-form.md |
1,000 |
| Word choice, common errors | 05-words-and-expressions-commonly-misused.md |
4,000 |
Most tasks need only 03-elementary-principles-of-composition.md — it covers active voice, positive form, concrete language, and omitting needless words.
LLMs regress to statistical means, producing generic, puffy prose. Avoid:
Be specific, not grandiose. Say what it actually does.
For comprehensive research on why these patterns occur, see signs-of-ai-writing.md. Wikipedia editors developed this guide to detect AI-generated submissions — their patterns are well-documented and field-tested.
Writing for humans? Load the relevant section from elements-of-style/ and apply the rules. For most tasks, 03-elementary-principles-of-composition.md covers what matters most.
Make data-driven prioritization decisions faster
Draft PRDs, status updates, and stakeholder presentations
Example
Create executive summary of Q3 roadmap, monthly progress report, feature launch announcement
Save 3-5 hours/week on communication overhead
Prerequisites
Time Estimate
30-60 minutes to see productivity improvements
Steps
Common Pitfalls
✓ Do
✗ Don't
💡 Pro Tips
✓ Use when
Use for user story writing, competitive research, roadmap prioritization, stakeholder communication, and PRD drafting. Best for reducing repetitive documentation and research work.
✗ Avoid when
Avoid for strategic product vision (requires deep customer empathy), pricing decisions (needs market and financial expertise), or when face-to-face customer discovery is more valuable than speed.
davila7/claude-code-templates
mattpocock/skills
parcadei/continuous-claude-v3
cursor/plugins
ailabs-393/ai-labs-claude-skills
pproenca/dot-skills
I recommend writing-clearly-and-concisely for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
Keeps context tight: writing-clearly-and-concisely is the kind of skill you can hand to a new teammate without a long onboarding doc.
We added writing-clearly-and-concisely from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
Solid pick for teams standardizing on skills: writing-clearly-and-concisely is focused, and the summary matches what you get after install.
Registry listing for writing-clearly-and-concisely matched our evaluation — installs cleanly and behaves as described in the markdown.
writing-clearly-and-concisely reduced setup friction for our internal harness; good balance of opinion and flexibility.
writing-clearly-and-concisely fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
writing-clearly-and-concisely has been reliable in day-to-day use. Documentation quality is above average for community skills.
Solid pick for teams standardizing on skills: writing-clearly-and-concisely is focused, and the summary matches what you get after install.
I recommend writing-clearly-and-concisely for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
showing 1-10 of 42