nature-writing · galaxy-dawn — скилл для Claude Code: установка
Скилл nature-writing помогает писать и перестраивать научные тексты в стиле Nature из тезисов, результатов, рисунков и заметок. Подходит для рукописи, раздела или плана статьи.
MIT 306 установок ★ 6 082 обновлён 2026-10-19
npx skills add Galaxy-Dawn/claude-scholar --skill nature-writing -a claude-codeЧто делает nature-writing
nature-writing помогает создать или перестроить заголовок, абстракт, введение, результаты, обсуждение, заключение или всю аргументацию рукописи. Он сначала выделяет основной тезис, доказательства и границы вывода, затем раскладывает текст по ролям абзацев и держит утверждения рядом с подтверждающими данными.
Внутри есть рабочий процесс для выбора структуры раздела, проверки связности абзацев и согласования тезисов с доказательствами. Скилл учитывает заметки, результаты, рисунки и черновики на китайском языке. Без чётких core claim, evidence или boundary он должен оставить заполнитель либо запросить недостающие сведения, а не додумывать результаты, методы или ссылки.
Для дополнительных рекомендаций используются файлы из references/: отдельные материалы посвящены абстракту, введению, методам, экспериментам, заключению, обзору литературы и самопроверке статьи.
Какие задачи решает
- собрать план научной статьи из заметок и результатов
- перестроить введение вокруг исследовательского пробела
- написать абстракт по тезису и доказательствам
- связать утверждения в Results с рисунками и сравнениями
- проверить границы выводов перед отправкой рукописи
Примеры запросов агенту
- Перестрой введение статьи по моим тезисам, результатам и рисункам, сохрани границы утверждений.
- Составь абстракт в стиле Nature из этого черновика и укажи места, где не хватает доказательств.
- Проверь связность раздела Results и предложи структуру абзацев без добавления новых результатов.
Как установить nature-writing
1Через Skills CLI (Vercel)
npx skills add Galaxy-Dawn/claude-scholar --skill nature-writing -a claude-code2Вручную: положить файлы
~/.claude/skills/nature-writing/SKILL.mdПапка скилла целиком; для одного проекта — .claude/skills/nature-writing/
1Через Skills CLI (Vercel)
npx skills add Galaxy-Dawn/claude-scholar --skill nature-writing -a codex2Вручную: положить файлы
.agents/skills/nature-writing/SKILL.mdДля всех проектов — ~/.agents/skills/
1Через Skills CLI (Vercel)
npx skills add Galaxy-Dawn/claude-scholar --skill nature-writing -a cursor2Вручную: положить файлы
.cursor/skills/nature-writing/SKILL.mdCursor читает и .agents/skills/, и .claude/skills/
1GitHub CLI
gh skill install Galaxy-Dawn/claude-scholar skills/nature-writing2Вручную: положить файлы
.github/skills/nature-writing/SKILL.md1Через Skills CLI (Vercel)
npx skills add Galaxy-Dawn/claude-scholar --skill nature-writing -a gemini-cli2Командой платформы
gemini skills install https://github.com/Galaxy-Dawn/claude-scholar --path skills/nature-writingВручную: положить файлы
.devin/skills/nature-writing/SKILL.mdСтарый путь .windsurf/skills/ тоже читается
Через Skills CLI (Vercel)
npx skills add Galaxy-Dawn/claude-scholar --skill nature-writing -a opencodeClaude.ai
Упакуйте папку в zip и загрузите в Settings → Capabilities → Skills
По шагам, с командами для каждой платформы: Как установить скилл в Claude Code: пять способов
Вопросы о nature-writing
Как установить nature-writing в Claude Code?
Выполните npx skills add Galaxy-Dawn/claude-scholar --skill nature-writing -a claude-code, затем проверьте файл ~/.claude/skills/nature-writing/SKILL.md.
Что делает nature-writing?
Скилл создаёт и перестраивает разделы научной рукописи: от заголовка и абстракта до результатов, обсуждения и заключения. Он связывает аргумент с предоставленными доказательствами и ограничивает неподтверждённые выводы.
Какие материалы нужны для работы nature-writing?
Можно передать тезисы, результаты, рисунки, заметки или черновик на китайском языке. Для ключевого аргумента нужны core claim, evidence и boundary; при пробеле скилл использует заполнитель или просит уточнение.
Исходный текст
SKILL.md · MIT
--- name: nature-writing description: Draft, restructure, or plan Nature-style manuscript sections from author-provided claims, results, figures, notes, or Chinese drafts. Use when the user wants to write or rebuild an abstract, introduction, results narrative, discussion, conclusion, title, or full manuscript argument rather than only polish finished prose. version: 0.2.0 author: Community contribution based on curated Nature/Nature Communications writing patterns and open research-writing notes --- # Nature-Style Scientific Writing Use this skill when the user needs help creating or rebuilding manuscript prose, not merely polishing existing sentences. ## Core stance - Author evidence comes first. Do not invent results, mechanisms, references, methods, novelty, sample sizes, statistics or limitations. - Write the argument before writing the sentences. - Make the paper easy to judge: relevance, novelty, trust, reuse and meaning. - Use ambitious but bounded claims. - If essential evidence is missing, write a placeholder or ask for the missing input instead of filling the gap. ## Mined writing memory Before drafting or restructuring academic prose, check the active installed `skills/ml-paper-writing/references/knowledge/paper-miner-writing-memory.md` under the current client's skill home. Read only entries relevant to this paper's section, article type, and venue. Use mined patterns for structure and wording ideas, while grounding every claim in the author's evidence and the target journal's requirements. Do not copy source phrasing. If the memory is absent or has no relevant entries, continue with this skill's references. ## When to open extra files | File | Open when | |---|---| | [references/article-architecture.md](references/article-architecture.md) | You need section-level structure, argument order, or published-article writing patterns | | [references/abstract.md](references/abstract.md) | Drafting or revising an abstract, especially challenge-contribution and challenge-insight-contribution forms | | [references/introduction.md](references/introduction.md) | Drafting or revising an Introduction, task framing, technical challenge, contribution framing, or teaser/pipeline logic | | [references/related-work.md](references/related-work.md) | Rebuilding Related Work as topic synthesis instead of a paper-by-paper list | | [references/method.md](references/method.md) | Writing Method sections, pipeline modules, module motivation, technical advantages, or implementation details | | [references/experiments.md](references/experiments.md) | Planning or writing Experiments/Results around baselines, ablations, metrics, tables, figures, and claim support | | [references/conclusion.md](references/conclusion.md) | Writing a bounded conclusion with contribution, evidence, impact, limitation, and future direction | | [references/paragraph-flow.md](references/paragraph-flow.md) | User asks whether a paragraph flows, makes sense, or is clear; use reverse outlining and paragraph-message checks | | [references/paper-review.md](references/paper-review.md) | Final manuscript self-review, rejection-risk audit, claim-evidence alignment, or reviewer-facing critique | | [references/chinese-author-workflow.md](references/chinese-author-workflow.md) | The user's notes are Chinese, mixed Chinese-English, or organized as lab notes rather than manuscript prose | | [references/examples/index.md](references/examples/index.md) | You need concrete abstract, introduction, or method examples after choosing the relevant guide | ## Intake Before drafting, identify: - manuscript section: title, abstract, introduction, results, discussion, conclusion, significance paragraph or full outline - paper type: mechanism, method, resource, device, model, clinical, materials, computational or interdisciplinary - core claim: what the paper actually demonstrates - evidence: figures, measurements, comparisons, datasets, statistics or examples - boundary: where the claim stops - target journal or word limit, if provided If any of `core claim`, `evidence` or `boundary` is absent, expose the gap before drafting. You may still produce a scaffold with explicit placeholders. ## Writing workflow 1. Build a one-sentence argument: `In [system/problem], we show [advance] using [approach], supported by [evidence], with [boundary].` 2. Choose the section architecture from `references/article-architecture.md`. 3. Map each paragraph to one job: context, gap, approach, result, comparison, mechanism, implication or limitation. 4. Draft from evidence outward. Keep claims near the data that support them. 5. Calibrate verbs: `show`, `demonstrate`, `suggest`, `indicate`, `enable`, `may`, `could`. 6. Remove unsupported novelty and universal claims. 7. Run a paragraph-flow check: one paragraph, one message, with a clear first sentence and explicit sentence-to-sentence relation. 8. Return prose plus concise notes on assumptions and missing inputs. ## Section defaults ### Abstract Default Nature pattern: `context/problem -> gap -> approach -> key result -> implication -> boundary` For technical AI, ML, CV or method-heavy manuscripts, open `references/abstract.md` and choose one of: - `challenge -> contribution` - `challenge -> insight -> contribution` - `multiple contributions` Keep it compact. Include quantitative or comparative detail when the user provided it. End with what the work enables, not generic importance. ### Introduction Use: `field scale -> bottleneck -> prior attempts -> unresolved gap -> present study` For method-heavy papers, open `references/introduction.md` and reason backward from the technical challenge and contribution before drafting forward. Do not summarize all results. The final paragraph should state what this paper does and how it addresses the gap. ### Results narrative Use an evidence ladder: `system/workflow -> validation -> main result -> baseline comparison -> mechanism/diagnostic analysis -> application or generalization` Each subsection should have a claim-first opening and then data support. For ML/conference-style experiment sections, open `references/experiments.md` and make sure each major claim is backed by comparison, ablation, or stress-test evidence. ### Related Work Use: `topic scope -> representative methods -> limitation tied to this paper -> distinction` Group prior work by technical topic and mechanism, not by publication year. ### Discussion Use: `central advance -> evidence meaning -> relation to prior work -> constraints -> future use` This is where interpretation and limitations belong. Do not repeat the Results section figure by figure. ### Conclusion Use: `contribution -> decisive evidence -> implication -> boundary` No new data. No unsupported promises. ### Title Prefer concrete titles that combine: `system/object + action/capability + application or consequence` Avoid slogan titles, grant-style aims and overbroad field claims. ## Output format Default output: 1. `Draft:` with the requested prose. 2. `Section outline:` with `3-7` compact bullets when the task involves a full section. 3. `Assumptions or missing inputs:` with only material issues. 4. `Claim-evidence map:` for major claims, using `Claim: ... | Evidence: ... | Status: supported/needs evidence`. 5. `Why this structure:` with `2-4` short bullets. For Chinese author notes, provide polished English first, then brief Chinese notes explaining major structural choices.
© Community contribution based on curated Nature/Nature Communications writing patterns and open research-writing notes · MIT · Galaxy-Dawn/claude-scholar
Похожие скиллы
Все скиллы по теме «Наука и исследования» →Сначала — nature-writing от других авторов.