Token导航 LogoToken导航TokenDH.com
研究检索external-serviceclawhub未标认证来源可访问clear审计通过

bookforge-prose-clarity-reviserBookforge 散文清晰度修订器

Agent Skill

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

总安装

1,909

周安装

78

GitHub Stars

公开资料未说明

下载量

618
OpenClaw

安装说明

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

GitHub

来源数

2

许可证

MIT-0

最后核验

2026-05-01

来源状态

来源可访问

安装方式

通过对话安装

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

请帮我安装这个 Agent Skill:bookforge-prose-clarity-reviser(Bookforge 散文清晰度修订器)
来源仓库:https://github.com/quochungto/bookforge-prose-clarity-reviser
安装命令:
openclaw skills install bookforge-prose-clarity-reviser
安装前请先检查当前环境是否支持对应 CLI,并向我确认将要执行的命令、安装目录、联网范围和文件读写权限;确认后再执行。

命令行安装

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

ClawHubOpenClaw
openclaw skills install bookforge-prose-clarity-reviser

简介

提升文本清晰度,应用四大原则改写晦涩语句。

  • 适用于报告、邮件、文档等需要高可读性的场景。
  • 强调主语明确、动词有力、新旧信息有序排列。
  • 不改变原意前提下增强表达效率与专业度。
  • 适合对初稿进行润色而非替代创作。bookforge-prose-clarity-reviser 属于研究检索类 Skill,可作为该场景下的辅助能力补充。

SKILL.md

name
prose-clarity-reviser
description
Revise dense, unclear prose into clear, readable sentences by applying four diagnostic principles — characters-as-subjects, actions-as-verbs, old-before-new information flow, and complexity-last sentence endings. Use this skill whenever the user shares a draft passage, paragraph, or document and asks you to make it clearer, more readable, easier to follow, less dense, less academic-sounding, or better written — even if they don't use those words. Also triggers on: \"can you revise this,\" \"this feels clunky,\" \"my advisor said this is unclear,\" \"make this flow better,\" \"my writing sounds stilted,\" or any request to improve prose style in research papers, reports, essays, grant proposals, or professional documents. Apply all four principles end-to-end; return a revised version with brief annotations showing what changed and why.
version
1.0.0
homepage
https://github.com/bookforge-ai/bookforge-skills/tree/main/books/the-craft-of-research/skills/prose-clarity-reviser
metadata
{"openclaw":{"emoji":"📚","homepage":"https://github.com/bookforge-ai/bookforge-skills"}}
status
draft
source-books
title
The Craft of Research, 4th Edition
authors
["Wayne C. Booth", "Gregory G. Colomb", "Joseph M. Williams", "Joseph Bizup", "William T. FitzGerald"]
chapters
[17]
tags
[research-methodology, prose-revision, writing-style, clarity, academic-writing]
depends-on
[]
execution
tier
1
mode
full
inputs
description
One or more paragraphs of draft prose to revise — a sentence, paragraph, section, or full document excerpt
tools-required
[]
tools-optional
[Read, Write]
mcps-required
[]
environment
Any agent environment. Works on pasted text or referenced files.

Prose Clarity Reviser

When to Use

The user has written prose — in any research, academic, or professional context — and wants it to be clearer or more readable. Typical triggers:

  • User pastes a paragraph and says "this is confusing" or "make this clearer"
  • User shares a draft section and asks for a style pass or readability revision
  • A supervisor, editor, or reviewer has flagged the writing as dense, abstract, or hard to follow
  • The user says their writing sounds too "academic," too stiff, or too indirect
  • The user asks why their sentences don't "flow" or why readers keep re-reading them

Do not apply these principles as the user writes new text. These are revision tools — apply them only after a draft exists. Applying them during drafting causes paralysis.

Scope: This skill handles sentence-level and paragraph-level style revision only. It does not restructure arguments, reorganize sections, or evaluate evidence. For those concerns, use a different skill.

Context

Required (must be present before proceeding)

  • The text to revise: One or more sentences or paragraphs. If the user says "revise my paper" without sharing text, ask them to paste the passage.

Useful but not required

  • Audience: Who are the intended readers? Specialists, generalists, students, peers? Knowing the audience determines whether field-specific nominalizations can stay as-is (see Principle 2 nuance below).
  • Purpose of the passage: Is this a methods section, an argument, an introduction? This affects how active vs. passive voice should be used (see Principle 4).

The Four Principles

Every unclear sentence violates one or more of these four structural rules. Diagnose before revising.


Principle 1: Characters as Subjects

The rule: The grammatical subject of every clause should name the main character in that clause's story — the entity doing, experiencing, or driving the action.

Why it matters: Readers orient themselves by asking "who or what is this sentence about?" When the subject is an abstraction, a nominalization, or an empty phrase, readers lose the thread. They have to work backward to reconstruct the actual agent.

Diagnostic — underline the first 6–7 words of every clause. Then ask:

  1. Does the subject name a concrete character (person, organization, organism, system, concept your field treats as an active agent)?
  2. If the subject is abstract, is it an abstraction your readers already treat as a familiar actor (e.g., "inflation," "the immune system" in a medical paper)?

If no to both — revise:

  1. Identify who or what the sentence is really about. If you cannot name a character, invent one (use "we," "researchers," "the study").
  2. Make that character the grammatical subject.
  3. Keep subjects short, specific, and concrete. Long whole-subjects (e.g., "The standardization of indices for the measurement of mood disorders") signal that the real character has been buried.

Field-specific note: In your discipline, the main characters may be abstractions — "monetary policy," "institutionalization," "gene expression." This is acceptable when those abstractions are already familiar to your audience and can be treated as acting entities. The problem occurs when you layer additional abstractions around them as additional nominalizations.


Principle 2: Actions as Verbs (Nominalization Detection)

The rule: The key action in every clause should appear as a verb, not as a noun derived from a verb or adjective (a nominalization).

Why it matters: When actions become nouns, three things go wrong simultaneously: (1) you lose the specific verb and replace it with a vague one like *make*, *have*, *do*, or *be*; (2) you bury the characters as modifiers or objects of prepositions; (3) you clutter the sentence with articles and prepositions that would not be needed if the action were a verb.

Nominalization markers to scan for:

  • Suffixes: *-tion, -ness, -ment, -ence, -ity, -ance, -al* (when used as noun)
  • Common nominalizations: *analysis, assumption, consideration, development, establishment, examination, implementation, improvement, indication, investigation, provision, requirement, utilization*
  • Some nominalizations look identical to their verb: *change, delay, report, plan, review, shift, study* — context determines which they are

Diagnostic — for each nominalization you find, ask:

  1. Is this the subject of a verb? If so, and if it derives from a verb, that verb has been buried.
  2. Is this from my field's standard vocabulary — a term readers recognize as a concept, not just a buried verb? (e.g., "hospitalization," "measurement" in a clinical paper) If yes, it may stay.

To revise:

  1. Find the buried verb inside the nominalization (e.g., *consideration* → *consider*, *establishment* → *establish*, *utilization* → *use*).
  2. Make that verb the main verb of the clause.
  3. Move the character (now freed from modifier position) back to subject position.

The exception: Do not convert every nominalization into a verb. When a nominalization refers to a concept that your readers treat as familiar and established — especially if you introduced it earlier in the passage — leave it as a noun. Abstract nouns used to echo earlier content serve the old-before-new principle (Principle 3). Revise unnecessary nominalizations; keep necessary ones.


Principle 3: Old Before New (Information Flow)

The rule: Begin each sentence with information readers already know (old) — either from the previous sentence or from shared context — and place new information at the end.

Why it matters: Readers build meaning incrementally. When each sentence opens with something familiar, readers have an anchor. They can attach the new information at the end to something they already hold in mind. When sentences open unpredictably, readers cannot connect them; the passage feels disjointed even if every individual sentence is well-formed.

This principle overrides Principle 1 when they conflict. If you must choose between starting with a character or starting with familiar information, always choose the familiar information.

Diagnostic — underline the first 6–7 words of every sentence (skip short introductory phrases like "At first," "For the most part"). Then run your eye down the page and ask:

  1. Do the sentence-opening words form a consistent, related set? They do not need to be identical, but they should name people or concepts that your readers will see as clearly related.
  2. Does each sentence begin with a word or phrase that echoes something from the previous sentence or from shared context?

If no — revise:

  1. Reorder: move the familiar information to the front of the sentence.
  2. Use pronouns, synonyms, or summary nouns to refer back to what was just mentioned.
  3. Move new, complex, or technical information to the end of the sentence. This often requires using the passive voice (see Principle 4).

Active vs. passive and information flow: The passive voice is not a flaw. Its primary function is to flip old and new information — to move older, familiar information from the end of one sentence to the beginning of the next. When familiar information would naturally be the object of an active verb, use the passive to promote it to subject position. Do not use passive or active based on a blanket rule; use whichever puts the right information at the beginning.


Principle 4: Complexity Last (Sentence Endings)

The rule: Place the newest, most complex, most technically demanding information at the end of a sentence, never at the beginning.

Why it matters: Readers can handle complexity better when they arrive at it from stable ground. If a sentence opens with a long, complex subject or an unfamiliar technical phrase, readers must decode it before they even know what the sentence is doing. Placing complexity last lets readers approach it with context already built.

Three contexts where this principle is especially important:

  1. Introducing a new technical term — the term should appear in the last few words of the sentence, not the first.
  2. Presenting a long, complex bundle of information — if a clause requires a long phrase or subordinate clause, push it to the sentence's end.
  3. Opening a paragraph — the last few words of the paragraph's opening sentence should name the key terms that the rest of the paragraph will develop.

Diagnostic — underline the last 5–6 words of every sentence. Ask:

  1. Are those words the most important, complex, or emphatic in the sentence?
  2. Are they technical terms being introduced for the first time?
  3. Are they concepts that the next several sentences will develop?

If no — revise: Move the most important, newest content to the sentence's end. This may require splitting the sentence, using a passive verb, or reordering clauses.


Active vs. Passive: The Decision Criterion

Use active voice when:

  • The writer/researcher is performing an action that only they can perform: *argue, conclude, suggest, claim, design, prove*
  • The action you want to emphasize is something only the authors did (rhetorical or intellectual ownership)

Use passive voice when:

  • Describing a process that any qualified person could repeat (standard in methods sections of scientific writing)
  • You need to move familiar information to the front of a sentence (information flow rule)

Do not use active or passive based on a blanket stylistic rule. The passive is not a sign of weak writing — it is a structural tool for managing information flow.


Revision Protocol

Apply in this order. Do not try to apply all four principles simultaneously.

Pass 1 — Diagnosis (mark up the text)

  1. Highlight the first 6–7 words of every clause. Skip short introductory phrases.
  2. Scan for nominalizations: look for words ending in *-tion, -ness, -ment, -ence, -ity*. Mark each one.
  3. Ask of each highlighted opening: Is this a character? Is this familiar information?
  4. Highlight the last 5–6 words of every sentence. Ask: Is this the most important content?

Pass 2 — Character and verb revision (Principles 1 and 2)

  1. Find sentences where the subject is not a character. Identify the real character.
  2. Find nominalizations. Determine which are field-standard (keep) and which bury a verb (convert).
  3. Rewrite: make real characters the subjects of specific, concrete verbs.

Pass 3 — Information flow revision (Principle 3)

  1. Reorder sentence openings to begin with familiar information.
  2. Shift new, complex, or technical content to sentence ends.
  3. Adjust active/passive as needed to serve information flow — not as a separate stylistic choice.

Pass 4 — Sentence endings (Principle 4)

  1. Check sentence endings. If the most important content is buried mid-sentence, reorder.
  2. Check paragraph-opening sentences. Confirm that the last few words introduce the paragraph's key term.

Pass 5 — Output

  1. Produce the revised text.
  2. For each paragraph, add a brief annotation listing: what changed and which principle was applied. Format:

- [P1] — character moved to subject - [P2] — nominalization converted to verb - [P3] — old-before-new reordering - [P4] — complexity moved to sentence end - [P3+voice] — passive/active adjusted for information flow


Examples

Example 1: Heavy Nominalization + Abstract Subject

Before:

The standardization of indices for the measurement of mood disorders has now made possible the quantification of patient response as a function of treatment differences.

After:

Having standardized indices for measuring mood disorders, we now can quantify patients' responses to different treatments.

Annotations:

  • [P2] *standardization* → *standardized*, *measurement* → *measuring*, *quantification* → *quantify*, *response* → *responses*
  • [P1] Subject changed from the abstract nominalized phrase to *we*
  • [P2] Vague verb *made possible* replaced by specific verb *can quantify*

Example 2: Information Flow Broken Across Sentences

Before:

Locke frequently repeated himself because he did not trust the power of words to name things accurately. Seventeenth-century theories of language, especially Wilkins's scheme for a universal language involving the creation of countless symbols for countless meanings, had centered on this naming power. A new era in the study of language that focused on the ambiguous relationship between sense and reference begins with Locke's distrust.

After:

Locke often repeated himself because he distrusted the naming power of words. This naming power had been central to seventeenth-century theories of language, especially Wilkins's scheme for a universal language involving the creation of countless symbols for countless meanings. Locke's distrust begins a new era in the study of language, one that focused on the ambiguous relationship between sense and reference.

Annotations:

  • [P3] Sentence 2 rewritten to open with *This naming power* — picks up the phrase from sentence 1's end
  • [P3] Sentence 3 rewritten to open with *Locke's distrust* — picks up the concept from sentence 2's end
  • [P2] *distrust of* → *distrusted* (minor nominalization)
  • [P4] New technical concept (*ambiguous relationship between sense and reference*) moved to sentence 3's end

Example 3: Complexity at the Front, Technical Term Placement

Before:

The monoamine hypothesis has been the leading biological account of depression for over three decades.

After:

For over three decades, the leading biological account of depression has been the monoamine hypothesis.

Annotation:

  • [P4] Technical term *monoamine hypothesis* moved to sentence end, where new technical terms belong when first introduced. The familiar framing (*for over three decades*) now anchors the sentence's opening.

Field-Specific Notes

Sciences (natural, social, clinical): Use passive in methods sections to describe repeatable processes. Use active and first person (*we conclude*, *we argue*, *we designed*) when describing intellectual contributions unique to the authors. Do not use passive to appear "objective" — it only changes whose story is being told.

Humanities: Main characters are often real people or abstract concepts (*democracy*, *modernity*, *the text*). These abstractions can stay as subjects if they are familiar to your audience and you are not layering additional nominalizations around them.

Technical and policy writing: Characters are often institutions, systems, or policies. Keep them as subjects. Avoid nominalizing verbs that describe what those institutions actually do (*implement* vs. *implementation of*, *regulate* vs. *regulation of*).


See references/before-after-sentence-pairs.md for 15+ additional before/after sentence pairs illustrating all four principles across different academic disciplines.

License

This skill is licensed under CC-BY-SA-4.0. Source: BookForge — The Craft of Research, 4th Edition by Wayne C. Booth, Gregory G. Colomb, Joseph M. Williams, Joseph Bizup, William T. FitzGerald.

Related BookForge Skills

This skill is standalone. Browse more BookForge skills: bookforge-skills

适合场景

01

OpenClaw 用户查找和安装 Skill 时

02

用户想查找某类 Agent Skill 时

03

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

04

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

能力概览

能力 1

按任务关键词查找相关 Skills

能力 2

展示可复制的安装命令

能力 3

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

能力 4

补充不同宿主或平台的使用分布数据

能力 5

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

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

平台分布

OpenClaw

79.66%
按下载量换算492

安全审计

VirusTotal

通过

ClawScan

通过

Static analysis

通过

权限和风险

external-service

该 Skill 可能调用第三方服务、云服务或外部模型 API,使用前需要确认账号、额度、数据发送范围和服务条款。

安装前确认

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

来源信息

继续浏览同类 Skills