Index of every page on this site: llms.txt
All skills
tristanmanchester avatar

/nature-article-writer

@3323bc9
Run it yourself

Draft, revise, or critique a primary-research manuscript for a specifically chosen Nature or Nature Portfolio journal, or deliberately develop that broad-reader scientific style. Ground claims in the supplied results and calibrate journal requirements separately. Do not impose this journal style on generic documentation, reviews, press releases, or unrelated writing.

Use this Skill: https://skilld.dev/gh/tristanmanchester/agent-skills/nature-article-writer

Nothing lands on disk. Nothing to clean up.

Fork this Skill

Edit a local copy. It keeps the author and licence.

referencesvoice-and-variation.md

≈1.1k tokens on demand. Your agent reads this file only when SKILL.md points to it.

Voice and variation

This file adapts anti-slop and "humanizer" principles to scientific prose. The goal is not to make papers casual. The goal is to remove the machine-like habits that make scientific text feel generic, over-smoothed, or oddly promotional.

What "human" usually means here

For research manuscripts, human-sounding prose usually has:

  • a specific claim at the centre
  • proportion between evidence and language
  • local sentence variety
  • paragraph endings that actually do argumentative work
  • selective signposting rather than transition spam
  • some friction and texture where the thinking is difficult, instead of frictionless generic phrasing

Common machine-like habits to cut

1. Adjective-led importance

Weak:

  • novel, groundbreaking, remarkable, critical, compelling, transformative

Repair:

  • replace the adjective with the thing the evidence actually shows

2. Generic significance endings

Weak:

  • These findings highlight the importance of ...
  • Together, our results open new avenues for ...

Repair:

  • say what follows from the result, under what conditions, and where the uncertainty remains

3. Conveyor-belt signposting

Weak:

  • Additionally
  • Moreover
  • Importantly
  • Notably
  • Taken together
  • Overall

Repair:

  • use sentence structure and paragraph order to carry the logic
  • keep only the few transitions that genuinely prevent misreading

4. Formulaic contrast frames

Weak:

  • not only ... but also
  • this is not merely ...
  • rather than simply ...

Repair:

  • state the actual contrast directly

5. Abstract noun haze

Weak:

  • landscape, interplay, framework, paradigm, hallmark, cornerstone, suite, robust approach

Repair:

  • name the system, variable, assay, model, or process

6. Over-smoothed sentence openings

Watch for high concentrations of sentence starts with:

  • This
  • These
  • It
  • We
  • or the same transition adverb

Repair by varying the opening around:

  • the object being measured
  • the contrast being made
  • the figure or condition under discussion
  • the actual new fact

7. Repetitive paragraph shapes

A suspicious draft often has paragraph after paragraph that:

  • starts with a generic topic sentence
  • gives a blob of middle detail
  • ends with a vague importance line

Repair:

  • give each paragraph one sharper job
  • end on the exact point that enables the next move

What not to overcorrect

Passive voice

Do not purge all passive voice. Methods often need it, and some result sentences benefit from object-first framing.

Repetition

Technical prose sometimes needs repeated terms for clarity. Replacing every repeated noun with a synonym can make the manuscript worse.

Caution

Some fields require careful hedging. Do not "humanize" by stripping out all restraint.

Technical density

Some papers really are dense. The aim is not simplification at all costs, but guided density.

Productive revision passes

Pass 1: remove generic importance language

Delete or replace every sentence that claims importance without specifying a consequence.

Pass 2: reduce hidden verbs

Turn abstract noun phrases back into actions where possible.

Pass 3: diversify sentence openings

Check the first word or first 2-3 words of consecutive sentences. If many repeat, vary them.

Pass 4: restore stress position

Look at sentence endings. Too many weak endings on procedural detail, acronyms, or empty nouns make the prose sag.

Pass 5: preserve the paper's intellectual temperature

The manuscript should sound calm and exact. Do not inject personality; inject precision.

Dangerous rewrites

Avoid these common overcorrections:

  • making the paper sound like a press release
  • replacing all technical terms with vague simpler ones
  • adding literary metaphors
  • removing caveats that are scientifically necessary
  • forcing "variety" by using synonyms for core technical entities

A good test

After revision, ask:

  • Could this sentence appear in almost any paper?
  • Is the claim supported right here or in the next sentence?
  • Does the paragraph feel inevitable rather than templated?
  • Does the conclusion sound earned rather than staged?

If the answer is no, revise again.

Source: SKILL.md on GitHub

skilld matched fixed text patterns in SKILL.md and file names. Patterns miss obfuscated code.

skilld run checks every file with the same patterns. It asks for approval before it loads a Skill with a behavior marked Needs approval.

1 warning1mo3 checks · Risk MEDIUM
  • Gen Agent Trust Hub1mo

    The skill helps users draft scientific manuscripts for Nature Portfolio journals. It contains deceptive metadata claiming the author is OpenAI, which misrepresents its source. It also processes external drafts and notes without isolation boundaries, creating an indirect prompt injection surface, and directs the agent to execute shell commands to run provided Python diagnostic scripts.

  • Socket1mo

    No alerts

  • Snyk1mo

    Risk: LOW · No issues

Signed by skilld at 3323bc9. This ties the file your Agent reads to that commit on GitHub. It does not review the instructions.

Last checked against GitHub 2 weeks ago.

Steadyupdated last month
metadata
{
  "version": "3.0.0",
  "reviewed": "2026-09-13"
}
Other metadata
compatibility
File read/write access for drafts; Python 3.10+ for optional local checks. Current journal requirements need their official guide or a supplied dated copy. The checker accepts UTF-8 text/ATX Markdown, not PDF, Word, or LaTeX directly.

README badge

README badge for tristanmanchester/agent-skills/nature-article-writer