nature-reader
- Repo stars 16,057
- Author updated Live
- Author repo nature-skills
- Domain
- Data
- Compatible agents
-
- Claude Code
- Cursor
- Cline
- Codex
- Windsurf
- Gemini CLI
- +20
- Trust score
- 92 / 100 · audit passed
- Author / version / license
- @Yuan1z0825 · v2.0.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-reader
description: This skill is split into two layers: Do not try to apply the reading logic from memory or from t…
category: data
runtime: no special runtime
---
# nature-reader output preview
## PART A: Task fit
- Use case: This skill is split into two layers: Do not try to apply the reading 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 source format” 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 reading 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 source format” 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 source format”. 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-reader
description: This skill is split into two layers: Do not try to apply the reading logic from memory or from t…
category: data
source: Yuan1z0825/nature-skills
---
# nature-reader
## When to use
- This skill is split into two layers: Do not try to apply the reading logic from memory or from this router. Always loa…
- 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 source format” 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-reader" {
input -> user goal + target files + boundaries + acceptance criteria
context -> Routing protocol / 1. Load the manifest and the core layer / 2. Detect the source format
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
}Full-Paper Markdown Reader — Router
This skill is split into two layers:
- A static layer under
static/that holds versioned, reusable content fragments (core principles, the reading workflow, the output contract, and per-source-format extraction guidance). - A dynamic layer (this file plus
manifest.yaml) that detects the request's source format and loads only the fragments needed for the current job.
Do not try to apply the reading 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 source_format axis, the allowed values, and the file paths each value maps to.
Also read every file listed under always_load. These hold the core principles, the reading workflow, and the output contract that apply to every reading job, plus the shared Terminology Ledger used to build the recurring-term table.
2. Detect the source format
Decide the source_format value using the manifest's detect: hint and the user's input:
pdf-text— selectable-text PDF. Default.scanned-pdf— image-only or OCR-required PDF.html— publisher or preprint HTML page.doi-arxiv— a bare DOI or arXiv link that must be resolved first.pasted-text— pasted prose or notes with no retrievable original layout.
State the detected value in one short line to the user before processing, so they can correct you cheaply. A source may map to more than one value (for example a DOI that resolves to a PDF); load the resolution fragment first, then the fragment for the resolved artifact.
3. Load the matching fragment(s)
Read the file mapped for the detected source_format. Do not read every fragment in static/. Load only what step 2 selected.
4. Build the reader using the loaded material
Apply the loaded fragments in this priority order:
- Core principles (
core/principles.md) — bilingual reader by default, translate for meaning, never degrade to a summary, copyright caution. - Source-format fragment — how to extract text, figures, and tables for this input.
- Reading workflow (
core/workflow.md) — the six-step source-map-first process. - Output contract (
core/output-contract.md) — required files and the pre-response verification checklist.
Build the Terminology Ledger as you translate (../_shared/core/terminology-ledger.md); it becomes the paper.md recurring-term table and the source_map.json glossary.
If constraints prevent full processing, still create a draft reader and label missing pages, figures, or low-confidence crops in translation_notes.md. Do not switch to summary mode.
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:
- detailed figure/table cropping and placement →
references/figure-extraction.md. - exact field schema for
paper.md/source_map.json→references/output-spec.md. - answering follow-up questions with source citations →
references/grounding-rules.md.
Why this split
- The static layer is versioned and reviewable. Adding a new source format is one new fragment plus one manifest line.
- The dynamic layer keeps each invocation cheap: only the fragment relevant to this input enters context.
- The router itself is short on purpose. Update fragments, not this file, when adding scope.
- This structure mirrors
nature-writingandnature-polishingso shared content lives in_shared/.
Decide Fit First
Design Intent
How To Use It
Boundaries And Review