AGENT SKILL

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.

适用职业内容创作者
使用场景写作与文案
License 许可
MIT
最近更新
2026-05-29
Stars
★ 1
Forks
0

01 前言 Front Matter

name
writing-clearly-and-concisely
description
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.

02 资源文件 7

03 SKILL.md 正文

Writing Clearly and Concisely

Overview

Write with clarity and force. This skill covers what to do (Strunk) and what not to do (AI patterns).

When to Use This Skill

Use this skill whenever you write prose for humans:

  • Documentation, README files, technical explanations
  • Commit messages, pull request descriptions
  • Error messages, UI copy, help text, comments
  • Reports, summaries, or any explanation
  • Editing to improve clarity

If you're writing sentences for a human to read, use this skill.

Limited Context Strategy

When context is tight:

  1. Write your draft using judgment
  2. Dispatch a subagent with your draft and the relevant section file
  3. Have the subagent copyedit and return the revision

Loading a single section (~1,000-4,500 tokens) instead of everything saves significant context.

Elements of Style

William Strunk Jr.'s The Elements of Style (1918) teaches you to write clearly and cut ruthlessly.

Rules

Elementary Rules of Usage (Grammar/Punctuation):

  1. Form possessive singular by adding 's
  2. Use comma after each term in series except last
  3. Enclose parenthetic expressions between commas
  4. Comma before conjunction introducing co-ordinate clause
  5. Don't join independent clauses by comma
  6. Don't break sentences in two
  7. Participial phrase at beginning refers to grammatical subject

Elementary Principles of Composition:

  1. One paragraph per topic
  2. Begin paragraph with topic sentence
  3. Use active voice
  4. Put statements in positive form
  5. Use definite, specific, concrete language
  6. Omit needless words
  7. Avoid succession of loose sentences
  8. Express co-ordinate ideas in similar form
  9. Keep related words together
  10. Keep to one tense in summaries
  11. Place emphatic words at end of sentence

Reference Files

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.

AI Writing Patterns to Avoid

LLMs regress to statistical means, producing generic, puffy prose. Avoid:

  • Puffery: pivotal, crucial, vital, testament, enduring legacy
  • Empty "-ing" phrases: ensuring reliability, showcasing features, highlighting capabilities
  • Promotional adjectives: groundbreaking, seamless, robust, cutting-edge
  • Overused AI vocabulary: delve, leverage, multifaceted, foster, realm, tapestry
  • Formatting overuse: excessive bullets, emoji decorations, bold on every other word

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.

Bottom Line

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.

04 同仓库更多 Skills

mattonweb
mattonweb/ai-assistant-foundry

crafting-effective-readmes

Use when writing or improving README files. Not all READMEs are the same — provides templates and guidance matched to your audience and project type.

★ 1
mattonweb
mattonweb/ai-assistant-foundry

wiki-architect

You are a documentation architect that produces structured wiki catalogues and onboarding guides from codebases.

人力资源
★ 1
mattonweb
mattonweb/ai-assistant-foundry

readme

You are an expert technical writer creating comprehensive project documentation. Your goal is to write a README.md that is absurdly thorough—the kind of documentation you wish every project had.

★ 1
mattonweb
mattonweb/ai-assistant-foundry

ubiquitous-language

Extract a DDD-style ubiquitous language glossary from the current conversation, flagging ambiguities and proposing canonical terms. Saves to UBIQUITOUS_LANGUAGE.md. Use when user wants to define domain terms, build a glossary, harden terminology, create a ubiquitous language, or mentions "domain model" or "DDD".

★ 1
mattonweb
mattonweb/ai-assistant-foundry

technical-writing-style

Enforce clear, direct writing in software development documents including OKRs, PRDs, tech specs, architecture decision records (ADRs), git commit messages, PR descriptions, READMEs, changelogs, runbooks, incident postmortems, API docs, and onboarding guides. Trigger whenever a user asks to write, edit, revise, or review any of these document types. Also trigger when the user says writing "sounds like AI", "feels robotic", "needs polish", or asks to "make it sound more natural" in the context of technical or professional prose. Do not trigger for fiction, poetry, creative writing, academic papers, or legal documents unless the user explicitly asks for a more natural tone.

内容创作者写作与文案
★ 1
mattonweb
mattonweb/ai-assistant-foundry

tldr-prompt

Create tldr summaries for GitHub Copilot files (prompts, agents, instructions, collections), MCP servers, or documentation from URLs and queries.

Skill与智能体开发
★ 1