Writing clearly and concisely — Strunk's rules plus AI-writing anti-patterns
Strunk's Elements of Style compressed into agent guidance, plus a field-tested catalog of AI writing tics to avoid (puffery, empty -ing phrases, promo adjectives, overused AI vocabulary)
- What
- Strunk's Elements of Style compressed into agent guidance, plus a field-tested catalog of AI writing tics to avoid (puffery, empty -ing phrases, promo adjectives, overused AI vocabulary)
- Cost
- Free
- Needs
- nothing to install — the skill is writing guidance your agent applies to prose; optional reference files load from the source repo when needed
- Install
- Copy the installer prompt below into your Muse — your agent does the rest.
Curated by Skill Harbor — @softaworks' skill for agents that write prose humans will read (docs, commit messages, error messages, reports, UI copy). It pairs two halves: what to do — Strunk's Elements of Style compressed into 18 rules (active voice, positive form, definite specific concrete language, omit needless words, emphatic words at sentence end) with a reference-file index for loading just the needed section (~1k–4.5k tokens) when context is tight — and what not to do — the AI writing patterns to kill (puffery like "pivotal" and "enduring legacy", empty "-ing" phrases like "ensuring reliability", promotional adjectives like "seamless" and "cutting-edge", overused AI vocabulary like "delve" and "leverage", formatting overuse). It even includes a limited-context strategy: draft with judgment, then dispatch a subagent with the relevant section to copyedit. MIT-licensed. Honest caveats: style is taste-laden — Strunk's 1918 rules are a strong default but not a substitute for a project's own voice guide; the anti-pattern list is a moving target as model prose drifts; it guides prose quality, not factual accuracy. Skill Harbor never reviews the code, review it yourself before use. Discovered via skills.sh.
Version:
Install
Prerequisites: nothing to install — the skill is writing guidance your agent applies to prose; optional reference files load from the source repo when needed Install "Writing clearly and concisely — Strunk's rules plus AI-writing anti-patterns" for me. It gives my agent @softaworks' guidance: Strunk's 18 rules compressed (active voice, positive form, concrete language, omit needless words) with section files to load on demand, plus a field-tested catalog of AI writing patterns to avoid (puffery, empty -ing phrases, promotional adjectives, overused AI vocabulary, formatting overuse). MIT-licensed. Repository: https://github.com/softaworks/agent-toolkit/blob/main/dist/plugins/writing-clearly-and-concisely/skills/writing-clearly-and-concisely/SKILL.md 1. Fetch the SKILL.md file (and any helper files) from the repository path into a temporary folder and summarize what it does in one or two sentences. 2. Safety check: review the SKILL.md and scripts for anything suspicious (unexpected network calls, shell commands, credential harvesting). This repo should contain zero secrets in code, credentials only via the secure vault, allowed hosts declared in the SKILL.md. Verify that holds here; STOP on any red flag and tell me. 3. Install it as a skill: copy SKILL.md and its helper files into the agent's skills directory, in a folder named "writing-clearly-and-concisely". 4. Verify with no network calls: frontmatter valid, files in place. 5. Report what was installed, where, and what I still need to do myself (e.g. nothing — it is guidance; tell the agent to apply it whenever it writes prose for humans). GitHub is optional: if I have a GitHub account or the gh CLI, you may use it; otherwise public access is fine. Never require it unless it's in the prerequisites above. Rules: don't touch anything outside the temp folder and the install target. If anything looks off, stop and ask me.
Questions
How do I install a build?
Every product page includes a copy-paste install prompt. Paste it into your Muse and it sets the build up for you — no manual configuration.
Where does my money go?
Straight to the seller. Skill Harbor never processes payments: checkout happens on the seller’s own page, usually Stripe.
What does the ✓ next to a creator’s name mean?
It means we confirmed the identity of the person behind the listing. It says nothing about the code itself — always check a build before installing it.