nature-response
- Repo stars 16,057
- Author updated Live
- Author repo nature-skills
- Domain
- Other
- Compatible agents
-
- Claude Code
- Cursor
- Cline
- Codex
- Windsurf
- Gemini CLI
- +20
- Trust score
- 88 / 100 · community maintained
- Author / version / license
- @Yuan1z0825 · 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-response
description: >- This skill is split into two layers: Do not try to apply the response logic from memory or fr…
category: other
runtime: no special runtime
---
# nature-response output preview
## PART A: Task fit
- Use case: >- This skill is split into two layers: Do not try to apply the response logic from memory or from this router. Always load fragments from disk as described below. Follow these four 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. No content axis — identify mode and language inline” 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 response logic from memory or from this router. Always load fragments from disk as described below. Follow these four 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. No content axis — identify mode and language inline” 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. No content axis — identify mode and language inline”. 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-response
description: >- This skill is split into two layers: Do not try to apply the response logic from memory or fr…
category: other
source: Yuan1z0825/nature-skills
---
# nature-response
## When to use
- >- This skill is split into two layers: Do not try to apply the response logic from memory or from this router. Always…
- 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. No content axis — identify mode and language inline” 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-response" {
input -> user goal + target files + boundaries + acceptance criteria
context -> Routing protocol / 1. Load the manifest and the core layer / 2. No content axis — identify mode and language inline
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 Reviewer Response — Router
This skill is split into two layers:
- A static layer under
static/that holds versioned, reusable content fragments (the default stance and red lines, and the response workflow with output format). - A dynamic layer (this file plus
manifest.yaml) that loads the core every time and reaches for the deeper response references only when a step needs them.
Do not try to apply the response logic from memory or from this router. Always load fragments from disk as described below.
Routing protocol
Follow these four steps every time the skill is invoked.
1. Load the manifest and the core layer
Read manifest.yaml. Then read every file listed under always_load:
static/core/stance.md— the editor-facing purpose, the default stance, the red lines, and the source hierarchy that apply to every response job.static/core/workflow.md— accepted inputs, the ten-step workflow, and the output package format.
2. No content axis — identify mode and language inline
Unlike nature-writing or nature-figure, nature-response has no fragment axis. Its variation is identified at runtime, not by loading different content bodies:
- task mode —
draft/audit/revise/triage-only/appeal-like. - decision type — minor revision, major revision, revise-and-resubmit, transfer after review, or unclear.
- user language — if the user writes Chinese, also produce the 中文核对 block.
Use references/intake-and-routing.md to fix the task mode, minimum inputs, and readiness state before drafting. Route appeal-like cases separately; do not draft an appeal as the default path.
3. Run the workflow
Follow the ten-step workflow in core/workflow.md: identify mode and decision type, extract editor instructions (IDs E.1) then reviewer comments (R1.1, R2.1), classify each item, build a strategy summary, draft point-by-point responses from the preserved comments, map every claimed change to a manuscript location or an explicit placeholder, flag missing author input, run QA, and return the package with a readiness state.
Never invent experiments, citations, line numbers, figure panels, supplementary items, editor instructions, or manuscript changes. Mark anything the author must supply as AUTHOR_INPUT_NEEDED.
4. 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 references/comment-taxonomy.md to classify comments, references/action-mapping.md for tracker fields, references/tone-and-stance.md for disagreement wording, references/difficult-cases.md for impossible experiments / conflicting reviewers / appeal-like cases, references/chinese-author-alignment.md for Chinese author notes, and references/qa-checklist.md before finalizing.
Why this split
- The static layer is versioned and reviewable; the core stays small for a normal response.
- The dynamic layer keeps each invocation cheap: the difficult-case, taxonomy, and QA depth load only when a step needs them.
- The router itself is short on purpose. Update fragments and references, not this file, when adding scope.
- This structure mirrors
nature-writing,nature-polishing,nature-reader,nature-paper2ppt,nature-figure, andnature-citation.
Decide Fit First
Design Intent
How To Use It
Boundaries And Review