Token导航 LogoToken导航TokenDH.com
前端设计需要联网github未标认证来源可访问许可证需确认审计通过

writing-clearly-and-concisely写得清楚简洁

Agent Skill

用于辅助文档、README、Markdown、说明文和内容稿件的整理与改写。它适合让 Agent 提炼结构、补齐章节、统一术语、检查链接或把零散材料整理成可读文档。使用时应保留项目已有事实、命令和路径,不要把未确认的信息写成确定结论;涉及对外文案时,还需要控制语气,避免过度营销或夸大能力。

总安装

652

周安装

28

GitHub Stars

公开资料未说明

下载量

228
CodexClaudeCursorGemini CLI

安装说明

本站只整理中文说明和来源信息,不托管安装包,也不代用户安装。

GitHub

来源数

2

许可证

unknown

最后核验

2026-05-01

来源状态

来源可访问

安装方式

通过对话安装

复制提示词发给支持本地命令或 Skills 的 AI 助手,先确认命令和权限,再让它执行。

请帮我安装这个 Agent Skill:writing-clearly-and-concisely(写得清楚简洁)
来源仓库:https://github.com/cygnusfear/agent-skills
仓库路径:skills/writing-clearly-and-concisely
安装命令:
npx skills add https://github.com/cygnusfear/agent-skills --skill writing-clearly-and-concisely
安装前请先检查当前环境是否支持对应 CLI,并向我确认将要执行的命令、安装目录、联网范围和文件读写权限;确认后再执行。

命令行安装

复制命令到本机终端执行。该命令会通过 npx skills 从第三方来源获取 Skill;本站只展示命令,不托管安装包,也不自动执行。

skills.shnpx skills
npx skills add https://github.com/cygnusfear/agent-skills --skill writing-clearly-and-concisely

简介

writing-clearly-and-concisely 基于《风格的要素》优化文本表达。

  • 适用于文档、错误消息、UI 文案等面向人类的 prose 写作。
  • 强调简洁、主动语态与结构清晰,删除冗余修饰。
  • 使用前应确认受众语言习惯,避免过度简化导致歧义。
  • 适用宿主包括 Codex、Claude、Cursor、Gemini CLI,接入前应确认版本、权限和运行环境要求。

SKILL.md

Writing Clearly and Concisely

Overview

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

WARNING: elements-of-style.md consumes ~12,000 tokens. Read it only when writing or editing prose.

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.

Structure Principles

BLUF (Bottom Line Up Front)

U.S. military communication standard: put your conclusion first, then explain.

The rule: Your first sentence answers what you need and by when. The reader can act without reading further.

Structure:

  1. BLUF statement (1-2 sentences): the decision, action, or key point
  2. Supporting context: only what's needed to understand or act

Test: Can someone act on your message after reading only the first sentence?

Before: "I've been working on the marketing materials for the conference. The design team worked hard on the layout. Could you take a look when you get a chance?"

After: "I need you to approve the attached flyer by noon Friday. It's for the August conference."

Skip BLUF when:

  • Delivering bad news (empathy first)
  • Skeptical audience (persuade before concluding)
  • Technical topics requiring foundation (explain concepts first—see below)

See: https://en.wikipedia.org/wiki/BLUF_(communication))

Explain Concepts Before Using Them

Information must be disclosed in the correct order. Never reference a term, concept, or acronym before you've defined it. If you use it, the reader must already understand it.

Limited Context Strategy

When context is tight:

  1. Write your draft using judgment
  2. Delegate a worker via teams with your draft and elements-of-style.md
  3. Have the worker copyedit and return the revision

If you REALLY REALLY need to preserve context, you can skip the full elements-of-style.md and instead use Orwell's rules:

  • Never use a metaphor, simile, or other figure of speech which you are used to seeing in print.
  • Never use a long word where a short one will do.
  • If it is possible to cut a word out, always cut it out.
  • Never use the passive where you can use the active.
  • Never use a foreign phrase, a scientific word, or a jargon word if you can think of an everyday English equivalent.
  • Break any of these rules sooner than say anything outright barbarous.

All 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

Section V: Words and Expressions Commonly Misused

Alphabetical reference for usage questions

Bottom Line

Writing for humans? Read elements-of-style.md and apply the rules. Low on tokens? Delegate a worker via teams to copyedit with the guide.

适合场景

01

用户想查找某类 Agent Skill 时

02

需要根据任务场景推荐可安装能力包时

03

需要对比不同来源的安装命令和来源信息时

能力概览

能力 1

按任务关键词查找相关 Skills

能力 2

展示可复制的安装命令

能力 3

保留来源站点、仓库和原始说明,方便继续核验

能力 4

展示第三方安全扫描或审计结果

安装后应在对应宿主中按原始 README 的触发条件使用;具体调用方式请以来源页面和 README 为准。

平台分布

Codex

35.92%
按下载量换算82

Claude

25.91%
按下载量换算59

Cursor

19.13%
按下载量换算44

Gemini CLI

9.39%
按下载量换算21

安全审计

Gen Agent Trust Hub

通过

Socket

通过

Snyk

通过

权限和风险

需要联网

该 Skill 可能需要联网访问来源站点、仓库或外部 API;具体网络访问范围需要结合源码和 README 复核。

安装前确认

本站仅展示第三方公开信息,不托管安装包,不提供自动安装或运行环境。安装前应自行审查源码、依赖和命令行为。当前只有一个来源,正式发布前建议补源仓库或其他目录站核验。

来源信息

继续浏览同类 Skills