Token导航 LogoToken导航TokenDH.com
研究检索只读github未标认证来源可访问许可证需确认审计通过

good-prose好散文

Agent Skill

good-prose 用于查找、检索和筛选相关信息,适合在 Codex、Claude、Cursor、Gemini CLI 中需要根据关键词、任务场景或来源线索快速定位候选结果时使用。可结合来源仓库、安装命令和原始 README 继续核验具体用法。安装前建议确认权限范围、维护状态,以及是否会触发联网、命令执行或文件读写。

总安装

1,508

周安装

61

GitHub Stars

2

下载量

473
CodexClaudeCursorGemini CLI

安装说明

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

GitHub

来源数

2

许可证

unknown

最后核验

2026-05-01

来源状态

来源可访问

安装方式

通过对话安装

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

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

命令行安装

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

skills.shnpx skills
npx skills add https://github.com/ahgraber/skills --skill good-prose

简介

good-prose 用于查找、检索和筛选相关信息。

  • 适合在 Codex、Claude、Cursor、Gemini CLI 中根据关键词快速定位候选结果。
  • 通过 npx skills add 命令从指定仓库安装并使用该技能。
  • 安装前需确认权限范围和维护状态,注意可能触发联网或文件读写操作。
  • good-prose 属于研究检索类 Skill,可作为该场景下的辅助能力补充。

SKILL.md

Good Prose: Write and Edit Professional, Clear, Human-Sounding Text

Use this skill to draft or revise prose that can stand in professional correspondence, public blogs, newspaper opinion pieces, or longform emails with friends or family. Aim for clarity, specificity, and a measured tone without slang or hype.

Invocation Notice

  • Inform the user when this skill is being invoked by name: good-prose.

Directives

Use these as the core craft rules. Apply them before any optional style tweaks.

Composition

  • Make the point early: Lead with the main claim or request.
  • Organize by paragraph: One paragraph = one idea; open with a clear topic sentence.
  • Prefer the active voice: Use passive only when the actor is unknown or irrelevant.
  • Use concrete verbs: Replace nominalizations with verbs.
  • Keep sentences lean: Remove dead weight, redundant phrasing, and filler.
  • Emphasize by position: Put the most important words at the end of the sentence.
  • Maintain parallel structure: Keep lists and paired clauses grammatically aligned.
  • Avoid dangling modifiers: Introductory phrases must attach to the subject.
  • Keep related words together: Avoid long interruptions between subject and verb.

Style

  • Prefer plain words: Use familiar words over ornate synonyms.
  • Avoid threadbare openings: Skip "One of the most..." and similar cliches.
  • Be specific: Replace vague adjectives with facts, numbers, or examples.
  • Use "is/are/has" when accurate: Avoid "serves as," "stands as," "boasts."
  • Reduce intensifiers: Cut "very," "highly," "extremely," unless essential.
  • Avoid euphemism and padding: Say what happened, not what it "represents."

Mechanics

  • Comma use: Use a comma before a coordinating conjunction joining two independent clauses.
  • Don't splice clauses: Use a semicolon or period instead of a comma.
  • No sentence fragments: Fragment only for deliberate emphasis.
  • Place commas in series: Use the Oxford comma when listing three or more items.
  • Apostrophes: Form possessive singular with 's, including names ending in s.

AI Guardrails

  • Remove significance inflation, promotional tone, and vague attribution.
  • Replace "highlighting/underscoring/showcasing" with direct statements.
  • Avoid negative parallelism and forced rule-of-three lists.
  • Remove chatbot fillers ("Hope this helps," "Great question," etc.).
  • End with concrete outcomes or next steps, not generic optimism.

LLM's have characteristic writing style that should be avoided. Refer to references/humanize-guardrails.md for LLM failure patterns and rewrite guardrails.

Quick Intake

Ask only if missing:

  • Purpose (inform, persuade, explain, request, reflect)
  • Audience and relationship
  • Medium and length (email, blog post, op-ed, memo, etc.)
  • Tone constraints (formal, friendly, firm, neutral)
  • Any must-keep facts or phrasing

If given a draft, do not ask questions unless the intent is unclear.

Workflow

  1. Find the spine: Identify the central claim, request, or takeaway.
  2. Shape the structure: Lead with context and stakes, then evidence, then implications or next steps.
  3. Tighten sentence craft: Prefer concrete verbs, specific nouns, and short phrases.
  4. Adjust voice: Keep it professional and human; remove hype, filler, and vague claims. If AI artifacts appear, consult references/humanize-guardrails.md.
  5. Polish mechanics: Fix grammar, punctuation, and consistency.

Core Principles

  • Clarity first: Put the point early. Move background below it.
  • Specific > abstract: Replace "important" or "significant" with facts or examples.
  • Use strong verbs: Reduce nominalizations and empty phrasing.
  • Prefer simple syntax: Avoid stacked clauses and overlong sentences.
  • Earn emphasis: Show importance with evidence, not adjectives.
  • Keep rhythm: Mix sentence lengths; let short sentences land.
  • Maintain tone discipline: No slang, no hype, no boilerplate cheerleading.

Editing Checks (Apply in Order)

  1. Meaning: Are claims precise, supported, and non-contradictory?
  2. Structure: Does each paragraph have a point and support it?
  3. Brevity: Cut filler, hedging, and throat-clearing.
  4. Style: Replace puffed-up language with plain English.
  5. Mechanics: Fix grammar, punctuation, and formatting.

Common Fixes

  • Vague openings: Replace generic framing with the specific purpose.
  • Abstract nouns: Swap "implementation of improvements" for "we improved X."
  • Weasel words: Replace "experts say" with named sources or remove.
  • Empty intensifiers: Remove "very," "extremely," "highly," unless essential.
  • Over-polite filler: Remove "I hope this finds you well" unless expected.
  • AI-ish phrasing: Avoid "pivotal," "tapestry," "underscoring," "delve."

Output Format

  • Provide the revised text.
  • If changes are substantial, add a brief, 3-5 bullet change summary.

References

Use these references for deeper guidance when needed:

  • references/humanize-guardrails.md - LLM failure patterns and rewrite guardrails.
  • references/tropes.md - local copy of tropes.fyi's catalog of common AI writing tropes to avoid.

适合场景

01

用户想查找某类 Agent Skill 时

02

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

03

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

能力概览

能力 1

按任务关键词查找相关 Skills

能力 2

展示可复制的安装命令

能力 3

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

能力 4

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

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

平台分布

Codex

33.55%
按下载量换算159

Claude

29.61%
按下载量换算140

Cursor

17.58%
按下载量换算83

Gemini CLI

9.87%
按下载量换算47

安全审计

Gen Agent Trust Hub

通过

Socket

通过

Snyk

通过

权限和风险

只读

该 Skill 主要提供规则、说明或参考内容,本身偏只读;真正读写文件、联网或执行命令仍取决于宿主 Agent 的任务。

安装前确认

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

来源信息

继续浏览同类 Skills