nature-writing
Подготовка научной статьи и материалов первой подачи
Что получите
Запрошенный научный текст или комплект материалов первой подачи с обозначенными предположениями и недостающими данными.
Что передать
Данные и выводы автора, нужный раздел или комплект материалов, тип статьи и целевой журнал.
Проверен состав файлов. Запуск не тестировался. Что проверено
Оценки пользователей
Как использовать
Помогает исследователям написать или перестроить аргументацию научной статьи на основе предоставленных доказательств. Подходит для отдельных разделов, сокращения основного текста и подготовки материалов первой подачи в журнал.
- Укажите масштаб работы: заголовок, абзац, раздел, вся статья или материалы первой подачи.
- Передайте основные утверждения, подтверждающие результаты и границы выводов; приложите существующий текст, если его нужно перестроить.
- Уточните журнал и язык исходных заметок, чтобы агент выбрал подходящие правила аргументации и изложения.
Условия работы
- Предусмотрены английские исходники и подготовка английского текста из китайских заметок; другие языковые режимы источник не заявляет.
- Недостающие существенные доказательства обозначаются заглушками и списком пробелов; содержание не выдумывается.
- Рекомендации в стиле Nature не являются официальными правилами: действующие требования выбранного журнала имеют приоритет.
- Только языковая правка относится к nature-polishing, переписка после решения журнала — к nature-response; графические аннотации и имитация рецензирования направляются в отдельные скиллы.
Пример запроса после установки
Перестрой обсуждение моей статьи для Nature Communications на основе приложенных результатов: выстрой цепочку выводов, обозначь ограничения и перечисли недостающие доказательства.
Пример составлен по инструкции автора; результат запуска не проверялся.
Основание: инструкция закреплённой версииДля установки
Node.js, npm и Git для команды выше. Подключения и инструменты для работы скилла настраиваются отдельно.
Совместимые агенты
Совместимость указана для инструкций. Запуск в каждом приложении не тестировался; для веб-чата способ подключения может отличаться.
Файлы скилла
GitHubЧитать инструкцию SKILL.md
Исходный текст закреплённой версии.
--- name: nature-writing description: Draft or restructure scientific manuscript arguments, sections, and initial-submission materials from author-provided evidence. Use for 论文写作、章节起草、论证重构、正文压缩、首次投稿材料. Use nature-polishing for language-only edits to existing prose and nature-response for post-decision correspondence. --- # Nature-Style Scientific Writing — Router ## Routing protocol For a new drafting task, follow the routing below. For follow-up edits, reuse established task choices and already loaded guidance; read additional fragments only when the requested scope changes. ### 1. Load the manifest and the core layer Read [manifest.yaml](manifest.yaml). It declares the axes (`task`, `paper_type`, `section`, `language`, `journal`), the allowed values, and the file paths each value maps to. Also read every file listed under `always_load`. These hold the default stance, writing workflow, and output format that apply to every drafting job. ### 2. Detect the axis values for this request For each axis in the manifest, decide the value using the manifest's `detect:` hint and the user's input: - `task` — manuscript / submission-package. Use `submission-package` for first-submission materials, never for revision correspondence. - `paper_type` — research / methods / hypothesis / algorithmic / review. Default: research. - `section` — abstract / intro / related-work / method / experiments / discussion / conclusion / title. May be multiple. Ask the user if it is ambiguous and matters for the draft. - `language` — en or zh-to-en. Detect from the user's notes themselves. - `journal` — nature / nature-family / nat-comms / nat-mach-intell / generic. Default: generic. Use `nature` only for the flagship journal Nature, `nat-comms` for Nature Communications, `nat-mach-intell` for Nature Machine Intelligence (NMI), and `nature-family` for other Nature Portfolio titles or an unspecified Nature-family request. State the detected axis values in one short line to the user before drafting, so they can correct you cheaply. This is a progress update, not an approval gate; continue unless a necessary decision remains unresolved. ### 3. Load the matching fragments For each axis value, Read the file mapped in the manifest. Skip the `section` axis when the task is `submission-package` or when the user explicitly asks for a free-floating argument paragraph with no section context. Do **not** read every fragment in `static/`. Load only what step 2 selected. ### 4. Draft using the loaded material Apply the loaded fragments in this priority order: 1. Core stance + intake (`core/stance.md`) — surface missing claim / evidence / boundary before drafting. 2. Paper-type playbook — argument chain, drafting order. 3. Section-specific drafting rules and structure. 4. Task-specific submission rules when `task=submission-package`. 5. Journal-specific framing and constraints. 6. Language-specific sentence and paragraph rules (apply last). For `task=manuscript`, use `core/workflow.md` at the requested scale. Plan the argument for a new section or substantial restructuring; a title, single paragraph, or local follow-up needs only the applicable evidence, wording, and consistency checks. Complete the requested prose unless a material unresolved decision blocks it or the user requested an outline for approval first. When drafting or restructuring Results, or compressing a full manuscript's main text, also load `../nature-shared/core/main-text-discipline.md` before building the paragraph map. Classify every result by function, allocate it across main text, captions, Methods/source data, and SI, then draft the shortest sufficient evidence chain. Do not equate a complete analysis record with a complete main text. When the target is flagship Nature, Nature Communications, Nature Machine Intelligence, or another Nature Portfolio title, load the matching shared Nature-style corpus guidance for the section being drafted: - Results or Discussion → `../nature-shared/core/nature-results-discussion.md` - Introduction or whole-manuscript narrative → `../nature-shared/core/nature-introduction.md` - Abstract → `../nature-shared/core/nature-abstract.md` Use these files for claim escalation, question-chain alignment, discovery-centred compression, and synthesis. They were initially distilled from published NMI papers and generalized as Nature-style defaults; do not present them as official policy, and let the target journal's current rules override them. For any Discussion drafting, restructuring, or section audit, also load `../nature-shared/core/discussion-argument-language.md`. Use it to select the opening anchor, control the reverse-funnel expansion, distinguish literature positioning from citation decoration, calibrate modal strength to evidence, and turn limitations and future work into claim-specific reasoning. This is general writing guidance rather than an official journal rule. For `task=submission-package`, follow `static/fragments/task/submission-package.md` and `references/submission-package.md` instead. Build the deliverable matrix and readiness audit; do not force manuscript paragraph architecture onto administrative submission materials. If essential evidence or boundary is missing, write a placeholder and list it under `Assumptions or missing inputs:` instead of inventing content. ### 5. Reach for references only when needed The files under `references/` are deep references and the example library, not defaults. Open them on demand per the `references.on_demand` table in the manifest. Typical triggers: - The user asks for a concrete example or template → `references/examples/index.md`. - A section's draft has structural problems that the section fragment alone does not explain → the matching `references/<section>.md`. - The user needs a broad-audience `Nature` abstract opening or asks about a `summary paragraph` → `references/nature-summary-paragraph.md`. - The user asks "does this paragraph flow?" → `references/paragraph-flow.md`. - The user asks for a self-review or rejection-risk audit → `references/paper-review.md`. - The user asks what belongs in the main text, captions, or SI; wants a shorter Results section; or is adding reviewer-driven explanation → `../nature-shared/core/main-text-discipline.md`. - The user requests a complete first-submission package, templates, or a submission-readiness audit → `references/submission-package.md`. - The target is the flagship journal Nature and exact submission or formatting requirements matter → `../nature-shared/journal-formats/nature.md`. - The target is Nature Machine Intelligence and exact content-type, submission, data/code or production requirements matter → `../nature-shared/journal-formats/nature-machine-intelligence.md`. - Any Nature / Nature Portfolio target needs Results claim progression, evidence-bound interpretation, robustness placement, or Discussion synthesis → `../nature-shared/core/nature-results-discussion.md`. - Any target needs a Discussion function chain, evidence-calibrated modal language, claim-specific limitations, non-redundant literature positioning, or uncertainty-driven future work → `../nature-shared/core/discussion-argument-language.md`. - Any Nature / Nature Portfolio target needs an Introduction funnel, exact gap, literature logic, question-first novelty, study roadmap, or alignment with Results → `../nature-shared/core/nature-introduction.md`. - Any Nature / Nature Portfolio target needs abstract evidence-chain, main/supporting-claim, numeric-result, or final-payoff decisions → `../nature-shared/core/nature-abstract.md`. - The work involves regulated or specialist research compliance → `../nature-shared/core/research-compliance.md`. ## Submission boundary - `nature-writing` owns **initial submission** materials prepared before peer review. - `nature-response` owns revision cover letters, rebuttals, point-by-point responses, marked manuscripts, appeals, and other post-decision correspondence. - Route graphical abstracts and TOC graphics to `nature-figure`; route simulated pre-submission peer review to `nature-reviewer`.
Проверка и особенности
Автоматическая проверка источника и файлов
Автоматически сверены публичный репозиторий, лицензия, YAML-заголовок SKILL.md, состав папки и Git-хеш каждого файла. Исполняемые файлы и срабатывания статических правил исключены из этой партии. Ручной аудит всех инструкций и проверка работы не проводились; эта проверка не гарантирует безопасность. Команда закреплена на проверенном коммите.
Интерес к репозиторию оцениваем по звёздам и форкам GitHub. Это показатели всего репозитория, а не числа установок отдельного скилла.
- Проверка состава
- 16.09.2026
- Проверенная версия
2375e0abdf42- Файлы с кодом
- Не указаны в данных проверки
- Изменения на GitHub
- Нужна повторная проверкаПоследняя проверка: 11.10.2026
Репозиторий и лицензия
Это показатели всего репозитория, а не установки скилла. Снимок требует обновления.
- Последняя активность GitHub
- 11.10.2026
- Лицензия
- Apache-2.0
- Добавлен в каталог
- 16.09.2026
Полный текст лицензии
Apache License
Version 2.0, January 2004
http://www.apache.org/licenses/
TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
1. Definitions.
"License" shall mean the terms and conditions for use, reproduction,
and distribution as defined by Sections 1 through 9 of this document.
"Licensor" shall mean the copyright owner or entity authorized by
the copyright owner that is granting the License.
"Legal Entity" shall mean the union of the acting entity and all
other entities that control, are controlled by, or are under common
control with that entity. For the purposes of this definition,
"control" means (i) the power, direct or indirect, to cause the
direction or management of such entity, whether by contract or
otherwise, or (ii) ownership of fifty percent (50%) or more of the
outstanding shares, or (iii) beneficial ownership of such entity.
"You" (or "Your") shall mean an individual or Legal Entity
exercising permissions granted by this License.
"Source" form shall mean the preferred form for making modifications,
including but not limited to software source code, documentation
source, and configuration files.
"Object" form shall mean any form resulting from mechanical
transformation or translation of a Source form, including but
not limited to compiled object code, generated documentation,
and conversions to other media types.
"Work" shall mean the work of authorship, whether in Source or
Object form, made available under the License, as indicated by a
copyright notice that is included in or attached to the work
(an example is provided in the Appendix below).
"Derivative Works" shall mean any work, whether in Source or Object
form, that is based on (or derived from) the Work and for which the
editorial revisions, annotations, elaborations, or other modifications
represent, as a whole, an original work of authorship. For the purposes
of this License, Derivative Works shall not include works that remain
separable from, or merely link (or bind by name) to the interfaces of,
the Work and Derivative Works thereof.
"Contribution" shall mean any work of authorship, including
the original version of the Work and any modifications or additions
to that Work or Derivative Works thereof, that is intentionally
submitted to Licensor for inclusion in the Work by the copyright owner
or by an individual or Legal Entity authorized to submit on behalf of
the copyright owner. For the purposes of this definition, "submitted"
means any form of electronic, verbal, or written communication sent
to the Licensor or its representatives, including but not limited to
communication on electronic mailing lists, source code control systems,
and issue tracking systems that are managed by, or on behalf of, the
Licensor for the purpose of discussing and improving the Work, but
excluding communication that is conspicuously marked or otherwise
designated in writing by the copyright owner as "Not a Contribution."
"Contributor" shall mean Licensor and any individual or Legal Entity
on behalf of whom a Contribution has been received by Licensor and
subsequently incorporated within the Work.
2. Grant of Copyright License. Subject to the terms and conditions of
this License, each Contributor hereby grants to You a perpetual,
worldwide, non-exclusive, no-charge, royalty-free, irrevocable
copyright license to reproduce, prepare Derivative Works of,
publicly display, publicly perform, sublicense, and distribute the
Work and such Derivative Works in Source or Object form.
3. Grant of Patent License. Subject to the terms and conditions of
this License, each Contributor hereby grants to You a perpetual,
worldwide, non-exclusive, no-charge, royalty-free, irrevocable
(except as stated in this section) patent license to make, have made,
use, offer to sell, sell, import, and otherwise transfer the Work,
where such license applies only to those patent claims licensable
by such Contributor that are necessarily infringed by their
Contribution(s) alone or by combination of their Contribution(s)
with the Work to which such Contribution(s) was submitted. If You
institute patent litigation against any entity (including a
cross-claim or counterclaim in a lawsuit) alleging that the Work
or a Contribution incorporated within the Work constitutes direct
or contributory patent infringement, then any patent licenses
granted to You under this License for that Work shall terminate
as of the date such litigation is filed.
4. Redistribution. You may reproduce and distribute copies of the
Work or Derivative Works thereof in any medium, with or without
modifications, and in Source or Object form, provided that You
meet the following conditions:
(a) You must give any other recipients of the Work or
Derivative Works a copy of this License; and
(b) You must cause any modified files to carry prominent notices
stating that You changed the files; and
(c) You must retain, in the Source form of any Derivative Works
that You distribute, all copyright, patent, trademark, and
attribution notices from the Source form of the Work,
excluding those notices that do not pertain to any part of
the Derivative Works; and
(d) If the Work includes a "NOTICE" text file as part of its
distribution, then any Derivative Works that You distribute must
include a readable copy of the attribution notices contained
within such NOTICE file, excluding those notices that do not
pertain to any part of the Derivative Works, in at least one
of the following places: within a NOTICE text file distributed
as part of the Derivative Works; within the Source form or
documentation, if provided along with the Derivative Works; or,
within a display generated by the Derivative Works, if and
wherever such third-party notices normally appear. The contents
of the NOTICE file are for informational purposes only and
do not modify the License. You may add Your own attribution
notices within Derivative Works that You distribute, alongside
or as an addendum to the NOTICE text from the Work, provided
that such additional attribution notices cannot be construed
as modifying the License.
You may add Your own copyright statement to Your modifications and
may provide additional or different license terms and conditions
for use, reproduction, or distribution of Your modifications, or
for any such Derivative Works as a whole, provided Your use,
reproduction, and distribution of the Work otherwise complies with
the conditions stated in this License.
5. Submission of Contributions. Unless You explicitly state otherwise,
any Contribution intentionally submitted for inclusion in the Work
by You to the Licensor shall be under the terms and conditions of
this License, without any additional terms or conditions.
Notwithstanding the above, nothing herein shall supersede or modify
the terms of any separate license agreement you may have executed
with Licensor regarding such Contributions.
6. Trademarks. This License does not grant permission to use the trade
names, trademarks, service marks, or product names of the Licensor,
except as required for reasonable and customary use in describing the
origin of the Work and reproducing the content of the NOTICE file.
7. Disclaimer of Warranty. Unless required by applicable law or
agreed to in writing, Licensor provides the Work (and each
Contributor provides its Contributions) on an "AS IS" BASIS,
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
implied, including, without limitation, any warranties or conditions
of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
PARTICULAR PURPOSE. You are solely responsible for determining the
appropriateness of using or redistributing the Work and assume any
risks associated with Your exercise of permissions under this License.
8. Limitation of Liability. In no event and under no legal theory,
whether in tort (including negligence), contract, or otherwise,
unless required by applicable law (such as deliberate and grossly
negligent acts) or agreed to in writing, shall any Contributor be
liable to You for damages, including any direct, indirect, special,
incidental, or consequential damages of any character arising as a
result of this License or out of the use or inability to use the
Work (including but not limited to damages for loss of goodwill,
work stoppage, computer failure or malfunction, or any and all
other commercial damages or losses), even if such Contributor
has been advised of the possibility of such damages.
9. Accepting Warranty or Additional Liability. While redistributing
the Work or Derivative Works thereof, You may choose to offer,
and charge a fee for, acceptance of support, warranty, indemnity,
or other liability obligations and/or rights consistent with this
License. However, in accepting such obligations, You may act only
on Your own behalf and on Your sole responsibility, not on behalf
of any other Contributor, and only if You agree to indemnify,
defend, and hold each Contributor harmless for any liability
incurred by, or claims asserted against, such Contributor by reason
of your accepting any such warranty or additional liability.
END OF TERMS AND CONDITIONS
APPENDIX: How to apply the Apache License to your work.
To apply the Apache License to your work, attach the following
boilerplate notice, with the fields enclosed by brackets "[]"
replaced with your own identifying information. (Don't include
the brackets!) The text should be enclosed in the appropriate
comment syntax for the file format. We also recommend that a
file or class name and description of purpose be included on the
same "printed page" as the copyright notice for easier
identification within third-party archives.
Copyright [yyyy] [name of copyright owner]
Licensed under the Apache License, Version 2.0 (the "License");
you may not use this file except in compliance with the License.
You may obtain a copy of the License at
http://www.apache.org/licenses/LICENSE-2.0
Unless required by applicable law or agreed to in writing, software
distributed under the License is distributed on an "AS IS" BASIS,
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
See the License for the specific language governing permissions and
limitations under the License.
Ещё в этой категории
Все в категорииОбсуждение
ПравилаПользовались этим скиллом? Делитесь опытом без регистрации. Все комментарии проверяет модератор.
