scientific-writer
Use when the user has a scientific draft (with its dataset, figures, and optional analysis code) and wants it iteratively revised until it clears a quality bar. Five specialist judges (figures, scientific content, style, formatting, code) critique the draft; a fresh, independent peer_reviewer grades it on those same axes (1-5 each → a percentage) with honesty guardrails; a scientific_writer revises prose, figures, and code — regenerating figures by running the user's plot command — until the peer-review score clears the threshold or the budget is hit. Not for writing a paper from a blank page,
npx skills add gaasher/Agent-Loop-Skills --skill scientific-writer --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# Scientific Writer Loop The artifact is a **piece of scientific writing** (draft + its dataset + figures + optional code). Each iteration **critiques → grades → revises**: five specialist judges produce concrete findings, an independent **peer_reviewer** turns the paper into a graded 0-100 score on the same axes, and a **scientific_writer** fixes the prose, figures, and code — running the user's `<plot_command>` to regenerate figures. The loop runs until the score clears `<pass_threshold>` or the budget is hit. All work happens on copies inside a sandbox; the user's originals are never touched. The cast (all in this folder): - `roles/figures_judge.md`, `roles/scientific_judge.md`, `roles/style_judge.md`, `roles/formatting_judge.md`, `roles/code_reviewer.md` — the five critics; each emits the shared `schemas/finding.schema.json`. - `roles/peer_reviewer.md` — the summative grader (its own honesty rules); emits `schemas/peer_review.schema.json` and decides `pass`. - `roles/scientific_writer.md` — the reviser; fixes code → regenerates figures → updates prose. - `schemas/finding.schema.json`, `schemas/peer_review.schema.json` — the two validated outputs. **Spawn-or-degrade.** On Claude
- Why the grader is built this way (the honesty problem)
- When to use
- Setup
- The loop
- Ledger
- Constraints
- Stops
What does the scientific-writer skill do?
Use when the user has a scientific draft (with its dataset, figures, and optional analysis code) and wants it iteratively revised until it clears a quality bar. Five specialist judges (figures, scientific content, style, formatting, code) critique the draft; a fresh, independent peer_reviewer grades it on those same axes (1-5 each → a percentage) with honesty guardrails; a scientific_writer revises prose, figures, and code — regenerating figures by running the user's plot command — until the peer-review score clears the threshold or the budget is hit. Not for writing a paper from a blank page,
How do I install it?
Run `npx skills add gaasher/Agent-Loop-Skills --skill scientific-writer --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From gaasher/Agent-Loop-Skills, a repository with 146 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.