zrwangems/dsh-zrwang-plugin / ars/skills/academic-pipeline
academic-pipeline
Flagged学术研究总编排:研究→写作→诚信检查→评审→返修→复审→终检→定稿的十阶段流水线,每阶段停在用户确认点,含材料护照与 7 类 AI 研究失败模式检查。Triggers: academic pipeline, research to paper, full paper workflow, end-to-end paper | 完整论文流程, 从研究到论文, 端到端写论文, 论文流水线。
_shared/policy_data/nature_policy.md
View on GitHub# Nature Portfolio — Canonical AI Policy Source
**Status**: Source of truth for Nature substantive policy content cited by both:
1. `../academic-paper/references/policy_anchor_table.md` — Nature anchor (#108 policy-anchor track, verbatim quotes per 16 fields)
2. `../academic-paper/references/venue_disclosure_policies.md` — Nature venue entry (v3.2 venue track, summary form)
**Provenance**: extracted from the Nature Portfolio AI editorial policy page (`https://www.nature.com/nature-portfolio/editorial-policies/ai`), wayback snapshot `nature:wayback=20260513075542` (sha256 `cf691cba…`). Section structure: `§AI authorship`, `§Generative AI images`, `§AI use by peer reviewers`, `§Editorial use`. ARS author-side matrix covers `§AI authorship` + `§Generative AI images` only.
**G4 invariant** (Decision Doc §4.3): edits to Nature substantive policy content must go through **this file** first; both downstream consumers (policy_anchor_table.md Nature section and venue_disclosure_policies.md Nature entry) re-cite from here. Direct edits to either consumer that change Nature substantive content are non-conformant.
**Dedup lint**: `verify_nature_dedup_with_venue()` in `scripts/check_policy_anchor_table.py` confirms (a) this file exists, (b) both consumers reference the path `_shared/policy_data/nature_policy.md` as their canonical pointer.
---
## Nature substantive policy quotes (verbatim, source-of-truth)
### §AI authorship — text-use policy
> "Large Language Models (LLMs), such as ChatGPT, do not currently satisfy our authorship criteria. Notably an attribution of authorship carries with it accountability for the work, which cannot be effectively applied to LLMs. Use of an LLM should be properly documented in the Methods section (and if a Methods section is not available, in a suitable alternative part) of the manuscript."
> "In all cases, there must be human accountability for the final version of the text and agreement from the authors that the edits reflect their original work."
### §AI authorship — copyediting carve-out
> "The use of an LLM (or other AI-tool) for "AI assisted copy editing" purposes does not need to be declared."
The carve-out predicate (paraphrased policy framing, partial verbatim): AI-assisted improvements to human-generated texts for readability and style — explicitly **excluding** generative editorial work and autonomous content creation.
### §Generative AI images — image-rights regime
> "Springer Nature journals are unable to permit its use for publication."
> "All exceptions must be labelled clearly as generated by AI within the image field."
Carve-outs (per Nature policy text, three categories): figures using AI to enhance or compose existing scientific data; AI-generated images that are themselves the subject of academic study (e.g., AI-art history); image-generation tools used to produce illustrations clearly marked as conceptual rather than scientific.
### §Generative AI images — non-generative ML caption rule
> "should be disclosed in the relevant caption upon submission"
---
## Consumer integration notes
- `policy_anchor_table.md` Nature anchor: extracts these quotes per 16-field matrix (3 explicit-mandate + 2 explicit-recommend + 4 implicit + 7 not-addressed).
- `venue_disclosure_policies.md` Nature entry: summarises the same source as venue-track guidance (Methods placement default, full responsibility statement requirement, no AI authorship).
- Renderer (LLM-prose): when the user selects either `--venue=Nature` or `--policy-anchor=nature`, the renderer cites this file's verbatim quotes in the emitted disclosure paragraph. Both tracks share the substantive policy content; placement (Methods vs anchor-specific) is the track-specific rendering decision.
---
## Related
- Discovery doc §4.5 — Nature anchor matrix with cross-anchor observation
- Decision Doc §2.4 G4 (renderer target) + §4.3 G4 invariant (Nature dedup)
- Impl spec §3 concern #5 resolution (hybrid image output channel)
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| writing-skillsobra/superpowersUse when creating new skills, editing existing skills, or verifying skills work before deployment | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| xlsxanthropics/skillsUse this skill any time a spreadsheet file is the primary input or output. This means any task where the user wants to: open, read, edit, or fix an existing .xlsx, .xlsm, .xltx, .csv, or .tsv file (e.g., adding columns, computing formulas, formatting, charting, cleaning messy data); create a new spreadsheet from scratch or from other data sources; or convert between tabular file formats. Trigger especially when the user references a spreadsheet file by name or path — even casually (like "the xlsx in my downloads") — and wants something done to it or produced from it. Also trigger for cleaning or restructuring messy tabular data files (malformed rows, misplaced headers, junk data) into proper spreadsheets. The deliverable must be a spreadsheet file. Do NOT trigger when the primary deliverable is a Word document, HTML report, standalone Python script, database pipeline, or Google Sheets API integration, even if tabular data is involved. | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |
| shipping-and-launchaddyosmani/agent-skillsPrepares production launches. Use when preparing to deploy to production, or when asking what needs to be in place before shipping. Use when you need a pre-launch checklist, when setting up monitoring, when planning a staged rollout, or when you need a rollback strategy. | Stars: 119k | Updated | Claude CodeCodex | Verified | Install |
| childhoodthedotmack/claude-memBabysit a shipped release after merge, publication, or deployment. Verify published packages, production behavior, installed plugins, and late CI or user reports until the observation window is clean; use babysit for PR readiness before release. | Stars: 118k | Updated | Claude CodeCodex | Verified | Install |