nature-polishing
- Repo stars 16,057
- Author updated Live
- Author repo nature-skills
- Domain
- Writing
- Compatible agents
-
- Claude Code
- Cursor
- Cline
- Codex
- Windsurf
- Gemini CLI
- +20
- Trust score
- 92 / 100 · audit passed
- Author / version / license
- @Yuan1z0825 · v6.1.0 · no license declared
- Token usage
- Lean
- Setup complexity
- Plug-and-play
- External API key
- Not required
- Operating systems
- Unspecified (assume cross-platform)
- Runtime requirements
- No special requirements
- Permissions
-
- Read-only
- Write / modify
- Network behavior
- Local-only
- Install commands
- 26 variants
Profile is derived at build time from SKILL.md and install vectors. Subject to drift from author intent.
Heads up: 未限定 allowed-tools，默认拥有全部工具权限。
---
name: nature-polishing
description: This skill is split into two layers: Do not try to apply the polishing logic from memory or from…
category: writing
runtime: no special runtime
---
# nature-polishing output preview
## PART A: Task fit
- Use case: This skill is split into two layers: Do not try to apply the polishing logic from memory or from this router. Always load fragments from disk as described below. Follow these five steps every time the skill is invoked. runs entirely locally. Works with Claude Code, Cursor, Cline and 23 more..
- Inputs: target material, constraints, expected output, and acceptance criteria.
- Evidence boundary: follow “Routing protocol / 1. Load the manifest and the core layer / 2. Detect the axis values for this request” and do not present inference as author intent.
## PART B: Execution result
- **01** The card summarizes the use case; runtime output centers on “This skill is split into two layers: Do not try to apply the polishing logic from memory or from this router. Always load fragments from disk as described below. Follow these five steps every time the skill is invoked. runs entirely locally. Works with Claude Code, Cursor, Cline and 23 more.”.
- **02** When the source has headings, the agent prioritizes “Routing protocol / 1. Load the manifest and the core layer / 2. Detect the axis values for this request” so the result follows the author’s structure.
- **03** Typical output includes task judgment, concrete steps, required commands or file edits, validation, and follow-up options.
- **04** Risk context follows the fingerprint: read files, write/modify files; mostly runs locally; usually needs no extra API key.
## Running Rules
- read files, write/modify files; mostly runs locally; usually needs no extra API key.
- Validate with a small sample before expanding scope.
- Return the result, validation criteria, and next iteration options.The source does not require a stable slash command. After installation, invoke the skill by name and describe the task.
Name target files or source material, expected output, forbidden changes, and whether network or shell access is allowed. Permission fingerprint: read files, write/modify files.
Start with a small task and check whether the result follows “Routing protocol / 1. Load the manifest and the core layer / 2. Detect the axis values for this request”. Inspect diffs, logs, previews, or tests before expanding scope.
Confirm the final output includes a concrete result, evidence, and next action. If it stays generic, tighten inputs, boundaries, and acceptance criteria.
---
name: nature-polishing
description: This skill is split into two layers: Do not try to apply the polishing logic from memory or from…
category: writing
source: Yuan1z0825/nature-skills
---
# nature-polishing
## When to use
- This skill is split into two layers: Do not try to apply the polishing logic from memory or from this router. Always l…
- Use it when the task has clear inputs, repeatable steps, and validation criteria.
## What to provide
- Target material, scope, expected result, and forbidden changes.
- Whether network, commands, file writes, or external services are allowed.
## Execution rules
- Organize steps around “Routing protocol / 1. Load the manifest and the core layer / 2. Detect the axis values for this request” and keep inference separate from source facts.
- read files, write/modify files; mostly runs locally; usually needs no extra API key.
- Validate with a small sample before expanding the task.
## Output requirements
- Return the deliverable, key evidence, validation method, and next action.
- Mark missing information as unknown; do not invent commands, platforms, or dependencies.The author source anchors workflow facts; repository files anchor sources and commands; Fluxly only adds fit, limitations, and quality judgment.
skill "nature-polishing" {
input -> user goal + target files + boundaries + acceptance criteria
context -> Routing protocol / 1. Load the manifest and the core layer / 2. Detect the axis values for this request
rules -> SKILL.md triggers / order / output contract
runtime -> no special runtime | read files, write/modify files | mostly runs locally
guardrails -> usually needs no extra API key + small-sample validation + diff/log review
output -> copyable result + checklist + next iteration
}Nature-Style Academic Polishing — Router
This skill is split into two layers:
- 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). - A dynamic layer (this file plus
manifest.yaml) that detects the request's axes and loads only the fragments needed for the current job.
Do not try to apply the polishing logic from memory or from this router. Always load fragments from disk as described below.
Routing protocol
Follow these five steps every time the skill is invoked.
1. Load the manifest and the core layer
Read manifest.yaml. It declares the axes (paper_type, section, language, journal), the allowed values, and the file paths each value maps to.
Also 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.
2. Detect the axis values for this request
For each axis in the manifest, decide the value using the manifest's detect: hint and the user's input:
paper_type— research / methods / hypothesis / algorithmic / review. Default: research.section— abstract / intro / results / discussion / conclusion / title / methods. May be multiple. Ask the user if it is ambiguous and matters for the polish.language— en or zh-to-en. Detect from the draft itself.journal— nature / nat-comms / generic. Default: generic. If the user names a Nature subjournal, treat it asnature.
State the detected axis values in one short line to the user before proceeding, so they can correct you cheaply.
3. Load the matching fragments
For 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.
Do not read every fragment in static/. Load only what step 2 selected.
4. Polish using the loaded material
Apply 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:
- Paper-type playbook (architecture, writing order).
- Section-specific job and failure modes.
- Journal-specific framing and constraints.
- Language-specific sentence and paragraph rules (apply last).
- Core stance and ethics throughout.
If a paragraph's structural problem cannot be fixed without inventing content, flag it instead of papering over it.
5. Reach for references only when needed
The 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.
Layout/typesetting (排版) requests are different. If the user asks to fix
placement rather than wording — loose/sparse pages, stranded headings, figures
that don't fill the page or split across pages, "Float too large", multi-panel
arrangement, sparse Supplementary Information — skip the prose axes (paper_type,
section, language, journal) and load references/latex-layout.md directly. That
file is self-contained: it carries the diagnosis workflow (render → contact-sheet →
read the log), the float-glue and [H]/\clearpage/placeins patterns, and the
"regenerate wide figures taller at the source" rule. Always compile and visually
inspect rendered pages before and after — never judge layout from the .tex alone.
Why this split
- The static layer is versioned and reviewable. Adding a new journal style or paper type is one new file plus one manifest line.
- The dynamic layer keeps each invocation cheap: only the fragments relevant to this draft enter context, instead of the full 1000-line monolith.
- The router itself is short on purpose. Update fragments, not this file, when adding scope.
Decide Fit First
Design Intent
How To Use It
Boundaries And Review