本文へ移動
cccskills
無料GitHub で公開

remote-sensing-nature-polishing

Polish, restructure, or translate academic prose into Nature-leaning English using writing-strategy principles, curated Nature/Nature Communications article patterns, and phrase-level support from Academic Phrasebank. Use whenever the user asks to polish a manuscript paragraph, abstract, introduction, results, discussion, conclusion, title, methods section, or Chinese academic draft for publication-quality English. Also covers LaTeX layout/typesetting (排版) fixes — loose or sparse pages, stranded section headings, figures that don't fill the page or split across pages, "Float too large", multi-panel figure arrangement, and Supplementary Information that looks empty — via references/latex-layout.md. Also trigger on general academic/scientific writing requests even without the word "Nature", including academic writing, scientific writing, SCI/paper writing, English manuscript polishing, language editing, proofreading, and Chinese phrasings such as 学术写作、科研写作、论文润色、写paper、SCI写作、英文论文润色、语言润色、润色、改写、学术英语、英文写作.

インストール方法を見る

含まれるファイル(29)

  • SKILL.md5.1 KB
  • manifest.yaml3.6 KB
  • references/latex-layout.md9.5 KB
  • references/phrasebank-playbook.md3.6 KB
  • references/published-article-patterns.md4.2 KB
  • references/section-moves.md5.8 KB
  • references/style-guardrails.md2.6 KB
  • references/writing-strategy.md4.3 KB
  • static/core/failure-modes.md883 B
  • static/core/output-format.md487 B
  • static/core/stance.md1.6 KB
  • static/fragments/journal/generic.md741 B
  • static/fragments/journal/nat-comms.md2.2 KB
  • static/fragments/journal/nature.md1.2 KB
  • static/fragments/language/en.md1.2 KB
  • static/fragments/language/zh-to-en.md1.2 KB
  • static/fragments/paper_type/algorithmic.md953 B
  • static/fragments/paper_type/hypothesis.md765 B
  • static/fragments/paper_type/methods.md806 B
  • static/fragments/paper_type/research.md785 B
  • static/fragments/paper_type/review.md994 B
  • static/fragments/section/abstract.md679 B
  • static/fragments/section/conclusion.md512 B
  • static/fragments/section/discussion.md875 B
  • static/fragments/section/intro.md649 B
  • static/fragments/section/methods.md815 B
  • static/fragments/section/results.md933 B
  • static/fragments/section/title.md645 B
  • USAGE.md2.1 KB

SKILL.md(原文)

インストールする前に、エージェントに与えられる指示の中身を確認できます。

Nature-Style Academic Polishing — Router

This skill is split into two layers:

  • A static layer under static/ that holds versioned, reusable content fragments (core principles, paper-type playbooks, per-section guidance, language-specific rules, per-journal style).
  • A dynamic layer (this file plus manifest.yaml) that detects the request's axes and loads only the fragments needed for the current job.

Do not try to apply the polishing logic from memory or from this router. Always load fragments from disk as described below.

Routing protocol

Follow these five steps every time the skill is invoked.

1. Load the manifest and the core layer

Read manifest.yaml. It declares the axes (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, failure-mode diagnosis, ethics, and output format that apply to every polish 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:

  • paper_type — research / methods / hypothesis / algorithmic / review. Default: research.
  • section — abstract / intro / results / discussion / conclusion / title / methods. May be multiple. Ask the user if it is ambiguous and matters for the polish.
  • language — en or zh-to-en. Detect from the draft itself.
  • journal — nature / nat-comms / generic. Default: generic. If the user names a Nature subjournal, treat it as nature.

State the detected axis values in one short line to the user before proceeding, so they can correct you cheaply.

3. Load the matching fragments

For each axis value, Read the file mapped in the manifest. Skip the section axis only if the user has supplied free-floating prose with no section context.

Do not read every fragment in static/. Load only what step 2 selected.

4. Polish using the loaded material

Apply the loaded fragments in this priority order, matching the paper type -> section job -> paragraph logic -> claim/evidence/boundary -> sentence polish rule from core/failure-modes.md:

  1. Paper-type playbook (architecture, writing order).
  2. Section-specific job and failure modes.
  3. Journal-specific framing and constraints.
  4. Language-specific sentence and paragraph rules (apply last).
  5. Core stance and ethics throughout.

If a paragraph's structural problem cannot be fixed without inventing content, flag it instead of papering over it.

5. Reach for references only when needed

The files under references/ are deep references, not defaults. Open them on demand per the references.on_demand table in the manifest, for example when the user explicitly asks for phrasebank-style alternatives or a stricter style audit.

Layout/typesetting (排版) requests are different. If the user asks to fix placement rather than wording — loose/sparse pages, stranded headings, figures that don't fill the page or split across pages, "Float too large", multi-panel arrangement, sparse Supplementary Information — skip the prose axes (paper_type, section, language, journal) and load references/latex-layout.md directly. That file is self-contained: it carries the diagnosis workflow (render → contact-sheet → read the log), the float-glue and [H]/\clearpage/placeins patterns, and the "regenerate wide figures taller at the source" rule. Always compile and visually inspect rendered pages before and after — never judge layout from the .tex alone.

Why this split

  • The static layer is versioned and reviewable. Adding a new journal style or paper type is one new file plus one manifest line.
  • The dynamic layer keeps each invocation cheap: only the fragments relevant to this draft enter context, instead of the full 1000-line monolith.
  • The router itself is short on purpose. Update fragments, not this file, when adding scope.

レビュー

まだレビューはありません。使ってみた感想をお寄せください。

同じリポジトリのスキル

概要と使いどころ

Remote-sensing literature search, citation verification, sensor/platform/dataset query strategy, citation file management (.ris/.bib/.enw conversion), and reference management (BibTeX, related articles, DOI/arXiv lookup) across CrossRef, arXiv, Scopus, ScienceDirect, Semantic Scholar, and domain web sources. Use when the user needs coordinated multi-step literature workflows for remote sensing, Earth observation, geospatial AI, GIScience, photogrammetry, SAR, hyperspectral imaging, LiDAR, satellite missions, benchmark datasets, land-cover mapping, change detection, object detection, segmentation, retrieval, or multimodal remote-sensing foundation models. Also trigger on general literature-search needs during academic writing even without the word "Nature", such as searching for papers/literature, doing a literature review, verifying a citation, converting citation files, and Chinese phrasings like 文献检索、查文献、找文献、 文献综述检索、查论文、引文核对、参考文献管理、文献去重.

日本語の概要は準備中です。原文の説明を表示しています。

thislzm/SKILL82026年6月6日 更新

Submission-grade remote-sensing Nature/high-impact journal figure workflow for Python or R. Use whenever the user asks to create, revise, audit, or polish manuscript figures, multi-panel scientific plots, map-led composites, remote-sensing image plates, sensor/product workflow figures, validation/error/uncertainty panels, or journal-ready SVG/PDF/TIFF outputs, especially for Nature-family, Remote Sensing of Environment, ISPRS, IEEE TGRS, or other high-impact venues. Before plotting, define the figure's conclusion, evidence logic, export needs, and review risks. If the user has not chosen Python or R, ask "Python or R?" and stop. Use only the selected backend for figure generation, previewing, exporting, and QA. Supports matplotlib/seaborn and ggplot2/patchwork/ComplexHeatmap. Not for dashboards or Illustrator/Figma-first infographics. Also trigger on general academic-writing figure needs even without the word "Nature", such as making figures/plots for a paper, scientific/academic plotting, data visualization for a manuscript, and Chinese phrasings like 遥感论文配图、学术写作配图、科研绘图、科研作图、地图出图、论文图表、可视化.

日本語の概要は準備中です。原文の説明を表示しています。

thislzm/SKILL82026年6月6日 更新

Build a complete but efficient Nature-style Chinese PPTX presentation from a remote-sensing, Earth-observation, geospatial AI, or broader scientific paper, preprint, PDF, article text, abstract, figure legends, or reading notes. Use this skill whenever the user asks to make slides/PPT/PPTX for journal club, group meeting, paper sharing, thesis seminar, lab meeting, department report, or academic presentation from a remote-sensing research paper. It identifies the paper type and argument, selects only the figures needed for the story, writes Chinese slide content and speaker notes, creates the actual .pptx deck, and runs an explicit self-review/corrective revision loop focused on figure quality, text overflow prevention, and non-template visual design before delivery. Also trigger on general academic-presentation requests even without the word "Nature", such as turning a paper into slides, building an academic talk deck, conference/defense presentations, and Chinese phrasings like 论文做PPT、遥感论文汇报、组会PPT、文献汇报、学术汇报、做幻灯片、讲paper、读书报告PPT.

日本語の概要は準備中です。原文の説明を表示しています。

thislzm/SKILL82026年6月6日 更新

Build full-paper Chinese-English side-by-side, figure/table-aware, source-grounded Markdown readers for journal or conference papers from PDF, DOI, arXiv, publisher HTML, or pasted text. Use whenever the user asks to translate or read a paper, make 中英文对照/原文对照/全文翻译解读, extract figures or tables into the right positions, preserve figure/table placement near relevant prose, or keep exact source anchors for every block. This skill must not degrade into a summary-only output unless the user explicitly asks for a summary. Also trigger on general paper-reading and translation requests even without the word "Nature", such as reading/translating an academic paper, literature reading, understanding a paper, and Chinese phrasings like 读论文、精读论文、论文翻译、文献翻译、文献阅读、学术阅读、帮我读这篇文章、翻译这篇paper.

日本語の概要は準備中です。原文の説明を表示しています。

thislzm/SKILL82026年6月6日 更新

Simulate a Nature-style reviewer assessment from the referee perspective rather than an author rebuttal. Use when the user wants a pre-submission review, reviewer report, peer-review style critique, novelty/significance/technical soundness assessment, reviewer-style manuscript evaluation, 审稿人视角评估, 预审稿意见, or Nature reviewer report. Return 3 reviewer reports plus a cross-review synthesis, grounded only in the local Nature reviewer source basis. Also trigger on general pre-submission review requests during academic writing even without the word "Nature", such as getting a mock peer review for any journal, critiquing a draft as a reviewer would, assessing novelty/rigor before submission, and Chinese phrasings like 审稿人视角、模拟审稿、预审、帮我审一下论文、投稿前自审、审稿意见模拟、找论文问题.

日本語の概要は準備中です。原文の説明を表示しています。

thislzm/SKILL82026年6月6日 更新

thislzm のスキルをすべて見る

このスキルの問題を報告する