Expertise·Learning & Documentation·v6.1.0

Nature-Style Academic Polishing — Router

Polish, restructure, or translate academic prose into Nature-leaning English using writing-strategy principles, curated Nature/Nature…

You say
Buy it · $99 Read it before you buy $99 Written by Yuan1z0825 · unverified publisher
Context cost
11.4k tokensestimated from the bundle, loaded when it triggers
Bundle
12 files · 45.6 kBtext throughout, nothing executable
Licence
Apache-2.0paid listing
Last change
v6.1.0
Servers it uses
Noneruns standalone

What it does

Polish, restructure, or translate academic prose into Nature-leaning English using writing-strategy principles, curated Nature/Nature Communications article patterns, and phrase-level support from Academic Phrasebank. Use whenever the user asks to polish a manuscript paragraph, abstract, introduction, results, discussion, conclusion, title, methods section, or Chinese academic draft for publication-quality English.

Installed, it changes the agent in these ways.

What this skill changes about the agent is not written down here yet. The listing was collected from its source, and the description is in its own SKILL.md.

Expertise

Domain judgement the base model does not have.

contentwriting

The skill itself

This is the whole product. A skill is instructions the model reads, so there is nothing behind the listing you cannot see first — the front matter loads with every session, and the body below it loads when the skill triggers.

SKILL.md4.8 kB · 75 lines
--- name: nature-polishing description: Polish, restructure, or translate academic prose into Nature-leaning English using writing-strategy principles, curated Nature/Nature Communications article patterns, and phrase-level support from Academic Phrasebank. Use whenever the user asks to polish a manuscript paragraph, abstract, introduction, results, discussion, conclusion, title, methods section, or Chinese academic draft for publication-quality English. Also covers LaTeX layout/typesetting (排版) fixes — loose or sparse pages, stranded section headings, figures that don't fill the page or split across pages, "Float too large", multi-panel figure arrangement, and Supplementary Information that looks empty — via references/latex-layout.md. version: 6.1.0 author: Yuan1z skill, refactored into static/dynamic layers ---
8# Nature-Style Academic Polishing — Router
9
10This skill is split into two layers:
11
12- A **static layer** under static/ that holds versioned, reusable content fragments (core principles, paper-type playbooks, per-section guidance, language-specific rules, per-journal style).
13- A **dynamic layer** (this file plus manifest.yaml) that detects the request's axes and loads only the fragments needed for the current job.
14
15Do not try to apply the polishing logic from memory or from this router. Always load fragments from disk as described below.
16
17## Routing protocol
18
19Follow these five steps every time the skill is invoked.
20
21### 1. Load the manifest and the core layer
22
23Read [manifest.yaml](manifest.yaml). It declares the axes (paper_type, section, language, journal), the allowed values, and the file paths each value maps to.
24
25Also read every file listed under always_load. These hold the default stance, failure-mode diagnosis, ethics, and output format that apply to every polish job.
26
27### 2. Detect the axis values for this request
28
29For each axis in the manifest, decide the value using the manifest's detect: hint and the user's input:
30
31- paper_type — research / methods / hypothesis / algorithmic / review. Default: research.
32- section — abstract / intro / results / discussion / conclusion / title / methods. May be multiple. Ask the user if it is ambiguous and matters for the polish.
33- language — en or zh-to-en. Detect from the draft itself.
34- journal — nature / nat-comms / generic. Default: generic. If the user names a Nature subjournal, treat it as nature.
35
36State the detected axis values in one short line to the user before proceeding, so they can correct you cheaply.
37
38### 3. Load the matching fragments
39
40For each axis value, Read the file mapped in the manifest. Skip the section axis only if the user has supplied free-floating prose with no section context.
41
42Do **not** read every fragment in static/. Load only what step 2 selected.
43
44### 4. Polish using the loaded material
45
46Apply the loaded fragments in this priority order, matching the paper type -> section job -> paragraph logic -> claim/evidence/boundary -> sentence polish rule from core/failure-modes.md:
47
481. Paper-type playbook (architecture, writing order).
492. Section-specific job and failure modes.
503. Journal-specific framing and constraints.
514. Language-specific sentence and paragraph rules (apply last).
525. Core stance and ethics throughout.
53
54If a paragraph's structural problem cannot be fixed without inventing content, flag it instead of papering over it.
55
56### 5. Reach for references only when needed
57
58The files under references/ are deep references, not defaults. Open them on demand per the references.on_demand table in the manifest, for example when the user explicitly asks for phrasebank-style alternatives or a stricter style audit.
59
60**Layout/typesetting (排版) requests are different.** If the user asks to fix
61*placement* rather than wording — loose/sparse pages, stranded headings, figures
62that don't fill the page or split across pages, "Float too large", multi-panel
63arrangement, sparse Supplementary Information — skip the prose axes (paper_type,
64section, language, journal) and load references/latex-layout.md directly. That
65file is self-contained: it carries the diagnosis workflow (render → contact-sheet →
66read the log), the float-glue and [H]/\clearpage/placeins patterns, and the
67"regenerate wide figures taller at the source" rule. Always compile and visually
68inspect rendered pages before and after — never judge layout from the .tex alone.
69
70## Why this split
71
72- The static layer is versioned and reviewable. Adding a new journal style or paper type is one new file plus one manifest line.
73- The dynamic layer keeps each invocation cheap: only the fragments relevant to this draft enter context, instead of the full 1000-line monolith.
74- The router itself is short on purpose. Update fragments, not this file, when adding scope.
75
In the file
SKILL.md710 words
Files12
LicenceApache-2.0
Why you can read it

Nothing in a skill executes. The client loads the text and the model follows it, so a skill can be audited the way a runbook is — by reading it.

What it costs in context

Skills are not billed by the call. They are paid for in context: every token the instructions occupy is a token your code, your diff and your conversation cannot use. Here is what this one takes and when it takes it.

≈210
always loaded
The name and description, so the model knows the skill exists and when to reach for it.
11,190
on trigger
The instruction body and 11 supporting files, read only when the skill fires.
5.7%
of a 200k window
Ten skills this size would take about 57% of the window before you open a file.
050k100k150k200k context window

11.4k tokens, estimated from the bundle at four bytes to the token, held for the rest of the session once it triggers. Heavy. Teams tend to install this one per project rather than globally, and load it only when the job comes up.

Servers bill, skills cost

A server charges by the month. A skill charges once per session, in context, and then keeps charging it for as long as the session lives.

Before and after

The same question, put to the same model twice: once as it comes, and once with these instructions loaded.

No worked example has been published for this skill yet.

Adoption
Installsnone yet
Ratingno reviews yet

The procedure it runs

The procedure has not been published here. It is in the skill’s own SKILL.md, which its author has not sent to the marketplace yet.

Prose, not code

These steps are written for a model to follow, not executed by a runtime. It can still be told to skip one, and it will say so when it does.

Servers it uses

None. This skill calls no MCP servers at all.

Everything it needs is in the instructions, so it works in a project with nothing connected — the model reads the file and changes how it works with what it can already reach.

It writes no files and reaches no network. All it changes is how the model reasons and writes.

What it asks for
Writes filesno
Network accessno

Read from the allowed-tools line of this skill’s own SKILL.md. A skill grants no permissions of its own — it can only ask for tools your client already has.

What it will not do

Every skill is narrow, and the useful ones say where they stop. These are the jobs this one is the wrong tool for.

What this skill is not for has not been published here. Nothing is implied by that: it is a section the author has not filled in.

What is in the bundle

12 files, 45.6 kB on disk. A bundle is text throughout: the instructions the model reads, plus the templates it fills in.

  • README.md3.4 kB
  • SKILL.md4.8 kB
  • manifest.yaml3.6 kB
  • references/latex-layout.md9.8 kB
  • references/phrasebank-playbook.md3.7 kB
  • references/published-article-patterns.md4.3 kB
  • references/section-moves.md5.8 kB
  • references/style-guardrails.md2.7 kB
  • references/writing-strategy.md4.4 kB
  • static/core/failure-modes.md0.9 kB
  • static/core/output-format.md0.5 kB
  • static/core/stance.md1.7 kB
What is not in it

No dependencies and nothing executable: a skill is text the agent reads, so the bundle is 12 files you can review in full before installing. The Apache-2.0 licence covers the templates and examples as well as the instructions.

Install

Installing copies the bundle into your project. Nothing runs at install time — the files sit on disk until the model reads them.

$99 once
Nature-Style Academic Polishing — Router · Apache-2.0 · Yuan1z0825
one-time
Price$99 once
LicenceApache-2.0 — the author’s, unchanged by this purchase
Paid throughStripe, once, on the card you add at the checkout
Keeps workingfor good — the files are yours once they are on disk
Updatesevery release of 6.x through this account

You can read the whole bundle before paying — the SKILL.md above is the product, not a preview of it. What the money buys is the delivery: the folder packaged and handed to your machine by key, every update its author ships, and our support if it does not do what this listing says. The terms of use are Apache-2.0, set by the author and unchanged by buying it here.

Payment runs through Stripe, on a page like this one rather than a redirect. Once there is an account it joins the same mcprush invoice as everything else you run, so there is never a second card to enter.

Which clients pick it up on their own

A skill is a folder of text. A client with a skills folder reads it without being told; everywhere else the same text works, it is just handed to the model rather than found.

Claude Code.claude/skills/
Claude Desktop
ChatGPT
Cursor.cursor/skills/
VS Code.github/skills/
Codex CLI.agents/skills/
Gemini CLI.gemini/skills/
Grok.grok/skills/
Zed.agents/skills/
Windsurf.windsurf/skills/
Agent SDK.claude/skills/
HTTP / API
This release
Version6.1.0
Publishedno release date on file
Price$99
Referenceyuan1z0825/nature-style-academic-polishing-router

Versions

v6.1.0 is what is on the shelf; no release here carries a date. Instructions change more often than APIs do — a skill can be rewritten entirely without anything it depends on moving.

v6.1.0
  • No earlier releases have been published to the marketplace.
Pinning

Put yuan1z0825/nature-style-academic-polishing-router@6.1.0 in the install command to hold this exact version. Without the suffix you get whatever is current the day you install, and nothing moves under you afterwards.

Reviews

no reviews yet · no installs yet

Nobody has reviewed this skill yet. The rating is the mean of the reviews written here, so there is none until somebody writes the first.

Who can post

Only accounts that have had the skill installed for fourteen days, so a review is written after living with it rather than after reading it. Publishers may reply once.

Who wrote it

YU
Yuan1z0825

Publishes on mcprush.

0 servers listed4 skills listednot claimed
Profile
Publisher
Servers0