skill
cs-nature-paper-skill
研究流程编排与证据追踪 | An Agent Skill and Python runtime for research protocols, artifact provenance and review workflows.
Set up
Skills are installed by placing their folder where your agent loads skills.
The download comes from github.com/KaiserIIII/cs-nature-paper-skill itself, not from our server, so what you get is exactly what its author published.
Install instructions come from the README
README
synced Oct 21, 2026CS Nature Paper V4.1.0
简体中文 · v4.1.0 · MIT License
An Agent Skill and Python runtime for managing computer-science research workflows. It connects research questions, literature, experimental protocols, code, results, figures, manuscript claims, and review findings through explicit provenance records.
System at a glance
flowchart TD
User["Researcher + research question"] --> Director["Research Director / control plane"]
Director --> State["Adaptive research graph + claims / evidence / protocol"]
Director --> Router["Role and provider routing"]
subgraph Team["Built-in team: 13 specialists"]
Discovery["Discovery: literature, prior art, theory, data"]
Research["Research: design, compute, implementation, statistics"]
Publication["Publication: visualization, writing, editor"]
Assurance["Assurance: integrity, adversarial review"]
end
Router --> Discovery
Router --> Research
Router --> Publication
Router --> Assurance
Router --> Providers["PUBLIC_CORE + 6 V4.1 advisory adapters<br/>Optional PRIVATE_ULTRA only when qualified"]
Discovery --> Artifacts["Bounded execution via host tools + Python<br/>Typed artifacts, hashes, provenance"]
Research --> Artifacts
Publication --> Artifacts
Assurance --> Artifacts
Providers --> Artifacts
Artifacts --> Checker["Independent checks for load-bearing work"]
Checker --> State
State --> Gates["Scientific, evidence, publication + reviewer gates"]
Gates -. "reopen / amend / narrow" .-> Director
Gates --> Outputs["Evidence-linked results, figures, manuscript + review"]
Outputs --> Author["Author decides on submission and release"]
The specialist and provider layers produce candidate artifacts; they cannot independently approve scientific claims or authorize external release.
Core capabilities
- Route work through literature, experiment, analysis, writing, and review roles.
- Track dependencies and progress in a research graph with a hash-linked event log.
- Bind artifacts to their inputs, environment, code version, and verification status.
- Separate exploratory results from confirmatory evidence.
- Check scientific validity, evidence sufficiency, publication sufficiency, reviewer completeness, and submission readiness independently.
- Load audited resources from pinned upstream commits, with licenses and source manifests.
V4.1.0 includes six callable offline advisory providers. Their software integration is documented in the release report; formal scientific qualification and the broader system comparison remain incomplete.
Install
Download the v4.1.0 source archive and extract it to a new skill directory. The tag resolves to:
4d5c6d00c6af81705e62e783a0b8cabb34313034
For Codex, the directory is normally ~/.codex/skills/cs-nature-paper/. Keep existing installations with local changes separate, and review the source and dependency records before use.
Use
Use $cs-nature-paper in copilot mode.
Study this research question using the code and data in the workspace.
Start with related work and feasibility, then propose an experiment protocol.
Keep every claim linked to its evidence.
Use review for an existing draft and revision for reviewer feedback. The host session supplies execution tools; the skill supplies routing, contracts, state, and checks.
Architecture
| Area | Location |
|---|---|
| Skill entry point | SKILL.md |
| Python runtime | scripts/ |
| Workflow contracts | references/ |
| Schemas and registries | assets/ |
| Tests | tests/ |
| Dependency provenance | vendor/ |
| Release integrity | SHA256SUMS.txt, release_manifest.json |
Documentation
The runtime checks artifact integrity and workflow state. Scientific judgment and submission decisions remain the author's responsibility; software checks do not establish research novelty or predict acceptance.