- name
SKILL.md
Die Skill-Datei bleibt im Repository des Herausgebers.
Fügen Sie den kopierten Befehl in ein Terminal ein. Er installiert diese SKILL.md in dem jeweiligen Agenten.
npx skills add Light0305/Light-Science --skill light-write -a cursor -yFügen Sie den kopierten Befehl in ein Terminal ein. Er installiert diese SKILL.md in dem jeweiligen Agenten.
npx skills add Light0305/Light-Science --skill light-write -a claude-code -yFügen Sie den kopierten Befehl in ein Terminal ein. Er installiert diese SKILL.md in dem jeweiligen Agenten.
npx skills add Light0305/Light-Science --skill light-write -a codex -yFügen Sie den kopierten Befehl in ein Terminal ein. Er installiert diese SKILL.md in dem jeweiligen Agenten.
npx skills add Light0305/Light-Science --skill light-write -a grok -ySenden Sie die kopierte Nachricht in einem Grok Bot-Chat. Der Bot ruft diese SKILL.md von GitHub ab und fügt sie den Skills hinzu, die alle Ihre Bots gemeinsam nutzen.
Install this skill: https://github.com/Light0305/Light-Science/tree/HEAD/light-writeVom Herausgeber
需要落盘或继续已有项目时,先读 项目目录约定,按其中的本阶段位置、版本与关联规则保存;用户指定路径和旧项目优先。包内资源相对本 skill,研究产物相对真实项目,二者不要混用。只做局部讨论时无需初始化目录。
Write or revise scientific manuscripts so that each claim is clear, useful, and supported by the material available. Treat the author's scientific meaning and evidence boundaries as invariants. Select only the workflow needed for the request.
First select the requested task and scale. Resolve every package path relative to the directory containing this SKILL.md, including paths mentioned inside reference or module files.
A local sentence or paragraph normally needs only its task guide and the relevant integrity checks. Do not load every reference by default. For substantial work, use article-type routing before selecting section patterns; empirical Results allocation rules do not automatically apply to theory or review papers.
Choose from the actual user request. If the user asks only for an edit, do not draft unrelated sections. Preserve the requested output language and format. Chinese input does not by itself mean the user wants English output; translate only when asked or clearly required by the deliverable.
For manuscript drafting and typeset file delivery, read references/latex-output.md.
Default delivery is editable LaTeX source plus a compiled, visually inspected
PDF. A user-supplied LaTeX or Word template takes precedence; follow its native
format and structure. Preserve an existing project's adopted template/layout.
Without either, use the bundled generic double-column or single-column LaTeX
template. If the user has not specified the column count, ask them to choose
double or single column before drafting, and wait for the choice. Do not
silently assume double column, generate both, or repeat a settled choice on
each revision. Explicit text/Markdown-only requests, local wording edits,
outlines, and check-only tasks do not require this layout question or a build.
For substantial work, read references/module-routing.md and select applicable field guidance from modules/catalog.json. Compose task → evidence form/domain → article type → section → exact venue, rather than imposing a publisher's prose style on every field. Local edits need field modules only when domain meaning or inference is at stake.
All bundled field modules are draft starting guides, not expert-reviewed or performance-validated modules. No exact venue profiles are currently bundled. For an unrepresented field, fall back to the general core and use author-supplied conventions; do not invent a module or claim specialist authority. For interdisciplinary work, combine only the relevant rules from matching modules. A ranking category or publisher family is not a venue style.
Use the author's stated article type. If unclear, infer provisionally only when the materials make it safe; ask only if the type changes the structure materially. Read references/article-types.md for empirical research, methods/technical work, reviews/syntheses, theory/hypothesis papers, and protocols. Hybrids may combine approaches.
Scale the workflow:
Ledgers need not be shown as large tables unless useful or requested. A request to save a manuscript or continue work in its project authorizes the necessary in-scope file updates; do not request the same permission again. A chat-only edit needs no project files.
references/project-integration.md. Distinguish author-provided information from externally verified information, inference, and missing support.Before delivery, check the requested language, number of sentences/paragraphs,
edit scope, and both ends of any length range. English word counts and Chinese
character counts are different: follow the specified convention, and do not
count Latin abbreviations, numerals, or punctuation as Chinese characters when
the request explicitly specifies Han characters. Aim inside the range rather
than at a boundary. Use a counting tool when available and permitted; otherwise
revise conservatively and do not claim an exact verified count. Add substantive,
supported reasoning to reach a minimum; remove repetition before cutting
meaning-bearing content to reach a maximum. The optional scripts/text_metrics.py
counts a supplied UTF-8 passage using --unit han or --unit whitespace_words
and inclusive --min/--max bounds. Select the requested prose scope first;
it does not parse markup or implement a journal's counting policy.
[Evidence needed: provide the independent validation cohort and primary metric] for essential missing information. List material placeholders; never silently fill them.light-chart or light-diagram; preserve their source files.For a full section draft, include a concise outline and a claim–evidence map for major claims when useful. For local edits, provide the revised passage and only material notes. For a consistency audit, report issue, location, why it matters, and a concrete suggested fix; do not rewrite the whole paper unless requested. For substantial Results restructuring, provide a compact allocation/change audit when useful. Follow the user's requested format over these defaults.
references/integrity-and-evidence.md — source fidelity, claims, citations, numerical integrity, missing inputs, and compression safeguards.references/drafting.md — evidence-led drafting and argument reconstruction.references/argument-and-prose.md — argument progression, manuscript voice, and scoped conclusions.references/polishing.md — editing, translation, tightening, and revision reporting.references/sections.md — operational prompts for common manuscript sections.references/article-types.md — genre-specific argument loads and structure cautions.references/working-ledgers.md — source, claim, terminology, and numerical-fact ledgers.references/results-allocation.md — finding classification, placement, and compression audits.references/consistency-check.md — cross-section terminology, numbers, claims, and references.references/journal-adaptation.md — optional target-journal adaptation and official-requirement checks.references/latex-output.md — user-template priority, required column selection, bundled LaTeX templates, compilation, and PDF inspection.references/examples.md — synthetic examples for ledger-to-prose and evidence allocation.references/project-integration.md — project recovery, native upstream checks, source changes, and manuscript/figure/review loops.references/manuscript-packet.md — optional local revision receipt and narrowly scoped file/text checks.Draft, restructure, polish, translate, shorten, or consistency-check scientific manuscripts from author-provided evidence. Use for academic writing, paper drafts, manuscript editing, 中英文论文写作、论文润色、学术翻译
---name: light-writedescription: Draft, restructure, polish, translate, shorten, or consistency-check scientific manuscripts from…---# light-write/SKILL.mdÜbersicht
Draft, restructure, polish, translate, shorten, or consistency-check scientific manuscripts from author-provided evidence. Use for academic writing, paper drafts, manuscript editing, 中英文论文写作、论文润色、学术翻译、论文结构修改、全文一致性检查. Does not create or edit figures.
FAQ
Laden Sie light-write/SKILL.md vom Herausgeber herunter oder kopieren Sie den Pfad und öffnen Sie das Repository. PlugMCP listet den Skill und hostet die Datei nicht.
Der Herausgeber pflegt es unter https://github.com/Light0305/Light-Science.
Claude, Cursor, Codex und Grok Build können eine SKILL.md lesen, die Sie aus dem Repository des Herausgebers hinzufügen. Grok Bot installiert sie, wenn Sie den Link zum GitHub-Ordner des Skills in einem Chat senden.