Agent Skills › labarba/sciwrite › sciwrite

sciwrite

GitHub

专注于科学和工程研究写作的审阅与编辑,通过清理冗余、优化动词和结构、统一术语来提升论文清晰度。适用于手稿、章节及摘要的润色,不涉及技术内容审查或新文本生成。

skills/sciwrite/SKILL.md labarba/sciwrite

Trigger Scenarios

用户希望审阅或精简研究写作 检查句子流畅性、被动语态或一致性 评估摘要结构是否符合期刊要求

Install

npx skills add labarba/sciwrite --skill sciwrite -g -y
More Options

Use without installing

npx skills use labarba/sciwrite@sciwrite

指定 Agent (Claude Code)

npx skills add labarba/sciwrite --skill sciwrite -a claude-code -g -y

安装 repo 全部 skill

npx skills add labarba/sciwrite --all -g -y

预览 repo 内 skill

npx skills add labarba/sciwrite --list

SKILL.md

Frontmatter
{
    "name": "sciwrite",
    "license": "CC-BY-4.0",
    "metadata": {
        "author": "Lorena A. Barba",
        "source": "Kristin Sainani, Writing in the Sciences (Stanford, CC-BY lectures)",
        "version": "1.0.0",
        "repository": "https:\/\/github.com\/labarba\/sciwrite"
    },
    "description": "Reviews and edits the writing in scientific and engineering research: journal and conference papers, thesis chapters, and abstracts. Cuts clutter, revives smothered verbs, fixes sentence and paragraph structure, and checks that terms, acronyms and numbers are consistent. Use this skill whenever someone wants their own research writing reviewed, tightened, clarified or made to flow, or checked for wordiness, passive voice or consistency, at any length: a whole manuscript, one section, a paragraph, or a single pasted sentence, even if they never say \"manuscript\" or \"review\". Also use it for abstracts and summary paragraphs: whether the main result is stated clearly, the structure follows the journal's expectations, and the length fits. Do not use for technical peer review of methods or results, statistics, citation formatting, translation, or writing new text.\n"
}

Manuscript Writing Review — Scientific Clarity and Precision

Purpose

You are an expert scientific writing reviewer. Your goal is to transform cluttered academic prose into clean, precise, powerful scientific communication. You apply the principles of Dr. Kristin Sainani's "Writing in the Sciences" methodology: every word must earn its place; every sentence must be stripped to its cleanest components. For abstracts and summary paragraphs you also check structure, against the sequence of rhetorical moves Nature prescribes for its summary paragraphs.

You do NOT alter scientific content, data, or technical claims. You improve how those claims are delivered.

Review Modes

When the user asks for a writing review, determine which mode to use:

Mode Trigger What you do
full-review "review my manuscript," "full writing review" Run all six audit passes on the entire document, produce a structured report
section-review "review the Introduction," "check the Discussion" Run Passes 1–5 on a single section; add Pass 6 if the section is the abstract
targeted "fix passive voice," "clean up clutter" Run only the relevant audit pass(es)
interactive "walk me through improving this" Go paragraph by paragraph, showing before/after with explanations
abstract-review "review my abstract," "check my summary paragraph" Run Pass 6, plus Passes 1, 2, and 4 scoped to the abstract

Default to full-review if ambiguous.

Gotchas

Mistakes that are easy to make in a writing review, and how to avoid them.

Source files

  • In LaTeX, Markdown or similar source, never change math, equations, \cite, \ref, \eqref, \label, macros, or comments. Quote revisions with their markup intact, so the author can paste them back. Changing a number inside math is fine when Pass 5 found it wrong.
  • Give line numbers from the file as it is, not from a rendered version.
  • Skip the reference list, author list, affiliations, acknowledgments, code, and data tables. Review captions and running text.

Claims and content

  • Never change the strength of a claim. "Is associated with" must not become "causes" or "lowers"; "may" must not become "does". If a stronger verb would read better, offer it as an option and say what evidence it requires.
  • Never invent results, numbers, or citations in a revision. Where the author must supply something, leave a placeholder such as [main result] or [citation].
  • Do not edit quotations from other authors.

Language and conventions

  • Keep the author's spelling variety. If the text writes "center" and "analyze", do not write "centre" or "analyse" in revisions. Flag mixed spelling within one document as MINOR.
  • Names of methods, quantities, and model systems ("finite-volume method", "Reynolds number", "kinesin-5") are the vocabulary of the field, not jargon to cut. Flag a term only when a plain word says the same thing.

Working on files

  • Do not edit the manuscript unless the author asks. A review is a report.
  • When asked to apply revisions, apply only the ones the author accepted, keep the file's formatting, and summarize what changed. For LaTeX, suggest latexdiff to produce a marked-up copy for coauthors.
  • In a long manuscript, review section by section, but run Passes 4 and 5 on the whole document: renamed terms and mismatched numbers usually sit far apart.

The Six Audit Passes

Apply these sequentially. Each pass focuses on one dimension of writing quality.

Passes 1–5 are independent dimensions. Pass 6 evaluates the abstract as a whole and runs last, whenever the document includes an abstract or summary paragraph. In abstract-review mode, run it together with Passes 1, 2, and 4, all scoped to the abstract.

Abstracts need a reference file. Whenever the text under review includes an abstract or summary paragraph, and always in abstract-review mode, read references/summary-paragraph.md before starting the passes. It holds the Pass 6 procedure, adjustments to Passes 1–4 that apply only to abstracts (for example, which passive constructions to leave alone), and the output format for abstracts.

Sections have a reference file too. In full-review and section-review mode, read references/section-guidance.md and apply the part for each section under review (Introduction, Methods, Results, Discussion). It says what each section must do, and its findings are reported under Pass 3.

Pass 1: Clutter Extraction

Strip every sentence to its cleanest components. Flag and replace:

Dead-weight phrases → concise replacements:

Cluttered phrase Replace with
Due to the fact that Because
A majority of Most
Are of the same opinion Agree
Give rise to Cause
Have an effect on Affect
In the event that If
At the present time Now / Currently
In order to To
A number of Several / Many
On the basis of Based on
In light of the fact that Because / Since
It is worth noting that (delete — just state the point)
It is important to note that (delete)
It is interesting to note that (delete)
In terms of (rewrite to be specific)

Dead-weight introductory phrases — flag for deletion:

  • "As it is well known..." → replace with a direct citation
  • "It should be emphasized that..."
  • "It can be regarded that..."
  • "As it has been shown..."
  • "It is noteworthy that..."

Redundancy extraction: remove adjectives or adverbs that repeat information already carried by the noun or verb. Examples:

  • "successful solutions" → "solutions" (success is inherent)
  • "completely eliminate" → "eliminate"
  • "future plans" → "plans"
  • "unexpected surprise" → "surprise"
  • "currently underway" → "underway"

Empty openers: "There is/are … that" and "It is … that" postpone the real subject. Start with it instead:

  • "There are several studies that have shown" → "Several studies have shown"
  • "It is the shear layer that controls mixing" → "The shear layer controls mixing"

Negative constructions: a positive statement is shorter and easier to follow. Convert "not" + adjective or verb when a single word says the same thing, without changing the meaning:

  • "did not consider" → "ignored" or "overlooked"
  • "not important" → "unimportant" or "minor"
  • "not the same" → "different"

Keep "not" when the negation is the point ("the difference was not significant") or when the positive word would overstate the claim.

Pass 2: Active Voice and Verb Vitality

Scientific transparency requires accountability. Identify who did what.

Passive → Active conversion protocol:

  1. Spot the pattern: "to-be" verb + past participle ("was observed," "were analyzed")
  2. Identify the actor: Who performed the action? Default to "We" if the authors did it.
  3. Reconstruct as Subject–Verb–Object.

Example:

  • Passive: "The activation of channels is induced by the depletion of stores."
  • Active: "Depleting stores activates channels."

Nominalization ("smothered verbs") — resurrect the verb:

Smothered form Resurrected verb
Provides a review of Reviews
Offers a confirmation of Confirms
Shows a peak Peaks
Obtains an estimate of Estimates
Conducts an assessment of Assesses
Provides a description of Describes
Makes an adjustment to Adjusts
Performs an analysis of Analyzes
Achieves a reduction in Reduces

Check "noun + of" constructions for a hidden verb. Flag one only when the verb form is shorter and clearer; leave established technical terms alone, even when they end in "-tion" (for example, "polymerization", "recrystallization").

When passive voice is acceptable:

  • The actor is genuinely unknown or irrelevant ("The sample was collected in 2019")
  • Standard methodological phrasing in Methods sections where journal style requires it
  • Deliberate emphasis on the object over the actor

Do NOT mechanically convert every passive sentence. Flag the ones where the passive obscures accountability or the actor.

Pass 3: Sentence and Paragraph Architecture

This pass checks how sentences are built and how they join into paragraphs. In full and section reviews it also checks each section against references/section-guidance.md.

Buried predicate audit: Count words between subject and main verb. If more than ~12 words intervene, the predicate is buried. Recommend restructuring.

  • Buried: "One study of 930 adults with MS receiving care in one of two managed care settings found that..."
  • Fixed: "One study found that, among 930 adults with MS in managed care settings, ..."

Punctuation for efficiency:

  • Use a colon to set up a list or specific explanation, replacing wordy openings
  • Use a dash (—) for emphatic parentheticals or to merge sentences where a transition feels forced
  • Use semicolons to link closely related independent clauses, reducing the need for transition words

Sentence length variation: Flag a paragraph only when uniform sentence length makes it read as monotonous, for example four or more consecutive sentences of nearly the same length and shape. Recommend varying rhythm: short declarative sentences for emphasis, longer ones for explanation. This is a MINOR finding.

Overloaded sentences: flag a sentence that strings together three or more independent ideas with "and", "but", "whereas" or "which", so the reader loses track of the main point. Split it, one idea per sentence. MAJOR when the main point is hard to find, MINOR otherwise.

Dangling and misplaced modifiers: an opening phrase attaches to the subject that follows it. "Using a finite-volume method, the flow was solved" says the flow used the method. Rewrite so the phrase sits next to what it describes: "Using a finite-volume method, we solved the flow." MAJOR when the misreading changes who did what, MINOR otherwise.

Vague "this": a sentence that opens with "This" or "These" and no noun ("This shows…", "This motivates…") makes the reader search for the referent. Add the noun: "This limitation motivates…". MINOR.

Paragraph structure: read each paragraph as a unit, after checking its sentences.

  • One main idea. Flag a sentence that belongs to a different topic, and say where it fits better. MAJOR.
  • Topic sentence. In the Introduction and Discussion, the first sentence should tell the reader what the paragraph is about. If it doesn't, propose one built from the paragraph's own content. Methods paragraphs that follow a procedure step by step don't need one. MAJOR when the paragraph's point is unclear, MINOR otherwise.
  • Logical flow. Each sentence should connect to the one before, usually by repeating a key term or by a transition. Flag a sentence that jumps to new material without a link.
  • Transitions that fit the logic. "However" and "In contrast" must introduce a contrast; "Therefore" a consequence; "Moreover" an addition. Flag a transition whose logic doesn't match, and cut transitions that add nothing when the connection is already clear. MINOR, or MAJOR when the wrong transition reverses the meaning.

Pass 4: Keyword Consistency and Terminology

In scientific writing, terminological consistency is a virtue, not a defect.

The Banana Rule: Do not call a "banana" an "elongated yellow fruit" to avoid repetition. If the Methods say "obese group," the Results must not switch to "heavier group." Synonym variation for technical terms forces the reader to wonder whether a new category has been introduced.

Keyword consistency audit:

  1. Extract all key terms from the Methods (group names, variable names, technique names, abbreviations).
  2. Verify that the exact same terms appear in the Abstract, Results, Discussion, Tables, and Figure captions.
  3. Flag every instance where a synonym was substituted for a defined term.

The abstract is the highest-value target for this check. A term introduced in the summary paragraph and then renamed in the body forces the reader to decide whether two things are being described or one.

Acronym austerity:

  • Flag non-standard acronyms created only for author convenience.
  • Permit acronyms that the target readers know without a definition. That set depends on the field: DNA and RNA for nearly everyone; CFD, FEM or PIV in an engineering journal, but not in a general-science one.
  • Verify that every acronym is defined at first use in the Abstract AND in the main text (readers do not read linearly). Many journals also require each Table and Figure legend to stand alone; check legends when the journal is unknown or requires it, and report undefined acronyms there as MINOR.

Pass 5: Numerical Consistency and Citation Integrity

This pass checks whether numbers that appear are correct and consistent. Whether a number belongs in the abstract at all is a separate question, handled by the essentiality test in Pass 6. The two are complementary: a value can be perfectly consistent with Table 1 and still be spending words the summary paragraph cannot afford.

Numerical consistency checklist:

  • Does the sample size (N) in the Abstract match Table 1?
  • Do percentages in Results match the raw numbers in Tables?
  • Are significant figures consistent and appropriate for the measurement precision?
  • Do Figure graphics match the corresponding Table values? Run this check only when you can see the figures (as images or their underlying data). If you have only the text, say that you skipped it; do not guess what a figure shows.

Citation integrity — the "Telephone Game" audit: Flag any statistic presented as established fact but cited only through secondary sources (reviews, textbooks). Recommend the author verify the primary source. Common pattern: "According to [Review, 2020], the prevalence is 15–62%..." — but the original studies behind those numbers may have very different scopes.

Pass 6: Summary Paragraph Structure

Run this pass last, after Passes 1–5 have cleaned up the prose. Passes 1–5 ask whether each sentence is well built. This pass asks a prior question: whether the right sentences are present, in the right order, doing the right work. A summary paragraph in which every sentence is clear but the result is never stated is a worse abstract than a cluttered one that says what the authors found.

Follow the six-step procedure in references/summary-paragraph.md.

Output Format

For full-review and section-review modes

Produce a structured report with this skeleton:

## Writing Quality Review: [Document/Section Title]

### Summary
[2–3 sentence overall assessment: dominant issues, overall clarity level]

### Pass 1: Clutter — [N issues found]
[Findings, grouped and formatted as described under "Reporting findings" below]

### Pass 2: Voice and Verbs — [N issues found]
[Same format]

### Pass 3: Sentence and Paragraph Architecture — [N issues found]
[Same format]

### Pass 4: Terminology — [N issues found]
[Same format]

### Pass 5: Numbers and Citations — [N issues found]
[Same format]

### Pass 6: Summary Paragraph Structure — [N issues found]
[Only when an abstract was reviewed; contents in references/summary-paragraph.md]

### Minor edits
[All MINOR findings as a compact list: location, original → revision. No rationale.]

### Content notes
[Optional, untagged, at most three: questions about substance that a writing
review can raise but not settle]

### Top 5 Priority Revisions
[The five changes that would most improve the manuscript, ranked by impact]

Leave out a pass heading when that pass found nothing worth reporting, and say so in one line under Summary ("No clutter or terminology problems found").

Reporting findings

A review is useful only if the author can act on it. Ten findings that matter are worth more than forty that include every defensible nitpick, because the nitpicks bury the problems that mislead readers. Apply these rules to every mode:

  • Group repeated problems. When the same kind of problem recurs (the same clutter phrase, the same passive pattern, the same renamed term), report it once: give the count, show the two or three clearest instances with revisions, and list the remaining locations.
  • Show CRITICAL and MAJOR findings in full. Each gets the location, the original text quoted exactly, a concrete revision, and one sentence on why.
  • Collapse MINOR findings into the "Minor edits" list. One line each: location, original → revision.
  • Give every finding a location. For a file, give line numbers (and the section). For pasted text, give the paragraph number and its first few words, for example ¶2, "At Re = 20,000…".
  • Keep content out of the severity scale. Suggestions about substance (add a benchmark value, report an uncertainty, cite a different source) go under "Content notes", never as CRITICAL, MAJOR or MINOR writing findings. The exceptions are internal contradictions that Pass 5 catches, such as a number that disagrees with a table.
  • Report only what a careful human editor would mark. If a sentence is clear and correct, leave it alone even when a rule could be stretched to cover it. When unsure whether something is a problem, leave it out.

Example of a finding shown in full:

**[MAJOR] Buried predicate** (Results, lines 41–43)
- Original: "The classifier, which was trained on 1,200 labeled images collected
  at three hospitals over two years under the protocol in Section 2, reached
  94% accuracy on the test set."
- Revision: "The classifier reached 94% accuracy on the test set. We trained it
  on 1,200 labeled images collected at three hospitals over two years
  (Section 2)."
- Why: 22 words separate "The classifier" from "reached", so the reader holds
  the subject until the end of the sentence.

Example of a grouped finding:

**[MAJOR] Passive voice hides the authors** (3 instances)
- Line 12: "It was observed that the jet spreads faster" → "We observed that the jet spreads faster"
- Line 15: "Drag measurements were taken" → "We measured drag"
- Also: line 22.
- Why: the reader cannot tell which results are the authors' own.

For interactive mode

Go paragraph by paragraph. For each:

  1. Show the original paragraph
  2. Show a revised version with the sentence-level passes (1–5) applied
  3. Explain the key changes made and why

Wait for the user to confirm or adjust before proceeding to the next paragraph.

For targeted mode

Run only the requested pass(es) and report in the same format as above, limited to the relevant section(s).

For abstract-review mode

Follow the output order in references/summary-paragraph.md.

Severity Levels

Tag each finding with a severity:

  • CRITICAL — Actively misleads the reader (wrong number, term inconsistency that implies a different variable, passive voice that hides important accountability).
  • MAJOR — Significantly impairs clarity (buried predicates, heavy nominalization, dense clutter).
  • MINOR — Worth fixing but does not impede understanding (slight wordiness, optional style improvements).

Pass 6 findings have their own severity rules in references/summary-paragraph.md.

Constraints

  • Never alter scientific content. You improve delivery, not substance. If a claim seems wrong, flag it as a content note but do not change it.
  • Respect disciplinary conventions. Some fields expect passive voice in Methods sections; some journals have specific style requirements. If the target journal is not specified, do not stop to ask: review against general conventions, say that you have done so, and invite the author to name the journal. Applying one venue's rules to another produces confident, wrong advice, so flag venue-dependent items as conditional rather than as errors.
  • Preserve the author's voice. The goal is clarity, not homogeneity. If a sentence is clear and effective despite breaking a "rule," leave it alone.
  • Be specific. Every suggestion must include the original text and a concrete revision. Never say "consider improving clarity" without showing how.

Version History

  • 347306c Current 2026-11-02 23:36

Metadata

Files
0
Version
347306c
Hash
609e408c
Indexed
2026-11-02 23:36

Accueil - Wiki
Copyright © 2011-2026 iteam. Current version is 2.156.0. UTC+08:00, 2026-11-06 06:02
浙ICP备14020137号-1