agentleFS
takayoshitoyoda05takayoshitoyoda05/claude-ml-template/.claude/skills/paper-writing/SKILL.md

paper-writing

Skill1 starsChanged 2 months agoMITView on GitHub

論文の執筆・推敲・査読対応のとき、「論文をチェックして」「査読対応を手伝って」と言われたときに必ず使う。

38 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use ml-training-recipe, replication and 10 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • getcompanion-aiSkill

    ml-training-recipe

    Find implementable ML training recipes from papers, datasets, docs, and code. Use when the user wants to fine-tune, train, reproduce, or choose a practical ML method, dataset, hyperparameter setup, or benchmark recipe.

    Also in 3 projects that use this

  • getcompanion-aiSkill

    replication

    Plan a replication of a paper, claim, or benchmark, and execute only after an explicit environment choice. Use when the user asks to replicate results, reproduce an experiment, verify a claim empirically, or build a replication package.

    Also in 3 projects that use this

  • brainbytes-devSkill

    alpha-research

    Also in 3 projects that use this

  • JaimeParkerSkill

    paper-code-audit

    Perform three-way cross-validation of a research paper by comparing the original paper text (via Zotero), official code implementation (via Git), and personal Obsidian notes. Use this skill whenever the user wants to "audit a paper", "verify paper claims against code", "cross-check notes with implementation", "triangulate paper + code + notes", "find discrepancies between paper and code", or mentions wanting a deep, structured comparison of a paper's claims against its implementation and their own notes. Also trigger when the user asks to "analyze this paper thoroughly" with code available, or when they want to systematically reconcile what the paper says, what the code does, and what their notes claim.

    Also in 3 projects that use this

  • JimLiuSkill

    pdf-explore

    Use this skill when the user has attached a PDF, paper, report, or other document and the answer needs content from more than one place in it: summarize the methods or any other section, compare sections, find where a topic is discussed, read a value or label off a figure or chart, or find/list/extract every instance of something across the whole document (datasets, benchmarks, citations, figures, table rows, accession numbers — including appendices). Skip it only for a single lookup of 1–4 pages quoted in your very next response — `read_file(pages=[...])` attaches pages as images that are dropped from context after one turn, so multi-section answers end up re-reading the same ranges repeatedly. Parses the PDF once in the Python kernel: `pdf_pages` (pages as persistent text), `pdf_outline` (TOC), `pdf_scan` (rank pages by relevance), `pdf_map`/`pdf_extract` (per-page summary / structured fields via parallel haiku calls). For PDF creation/manipulation, use reportlab/pypdf directly.

    Also in 4 projects that use this

  • Yusong-EnceladusSkill

    research-review

    Get a deep critical review of research from GPT via Codex MCP. Use when user says "review my research", "help me review", "get external review", or wants critical feedback on research ideas, papers, or experimental results.

    Also in 6 projects that use this

  • +1 more from getcompanion-ai

The file

Files
SKILL.md

論文執筆支援

論文の構造チェック・推敲・査読対応を行う。執筆の代行ではなく、 著者(ユーザー)の主張を明確にし、弱点を潰す支援に徹する。

用途1: 構造チェック(主張-根拠-限界)

原稿(またはセクション)を読み、以下を確認する。

観点確認内容
主張の明確さ各段落の主張が1文で言えるか。主張の無い段落は削除候補
根拠の対応各主張に対応する根拠(実験結果・引用・論理)があるか
限界の明示手法の限界・適用範囲が正直に書かれているか
図表との整合本文の数値と図表の数値が一致しているか
論理の飛び「AだからB」のAとBの間に暗黙のステップが無いか

用途2: 引用の実在確認(anti-leakage)

  • 引用文献が literature/ の調査記録に存在するか確認する
  • 引用箇所の主張が、その文献に実際に書かれている内容と一致するか、 調査記録(notes/)の「引用する可能性のある主張」と突合する
  • 突合時は literature-review が記録した確認レベル(アブストのみ / 本文確認済み)を 必ず見る。「アブストのみ」の文献からの引用は「実在確認済み・内容未確認」として 区別し、本文確認をユーザーに促す
  • 記録に無い引用は「未確認」としてユーザーに確認を促す

用途3: 査読対応

査読コメントを受け取ったら、以下の形式で対応表を作る。

#査読コメント(要約)種別対応方針修正箇所
1...誤解 / 妥当な指摘 / 追加実験要求......
  • 「誤解」の場合: 論文のどの記述が誤解を招いたかを特定し、 反論ではなく記述の明確化で対応する方針を提案する
  • 「妥当な指摘」の場合: 素直に認めて修正する文面を提案する

用途4: 推敲

  • 一文一義(1文に主張は1つ)
  • 受動態の多用を避ける(日本語論文では「〜される」の連続を避ける)
  • 曖昧語(「など」「適切に」「効果的に」)を具体的な記述に置き換える

重要なルール

  • 実験結果の数値を勝手に変えない・丸めない
  • ユーザーが書いた主張を、確認なしに強い主張/弱い主張に書き換えない
  • 存在しない実験結果・文献を生成しない
  • スコープ制約: 論文ファイル(papers/ 等)を扱う場合、ユーザーが明示的に 指定したファイルのみを編集する

公開・共有前チェックリスト

公開・共有(handoffの保存、論文原稿の提出、リポジトリの公開など)の前に、 以下を確認する。

  • git 履歴に秘密情報・生データが含まれていないか
  • notebook 出力に生データや個人情報が残っていないか
  • テスト fixture に実データが紛れていないか
  • ログに秘密情報・生データが含まれていないか
  • レポート・evidence に集計値以外の生データが含まれていないか
  • MLflow の記録に生データ・秘密情報が含まれていないか
  • exports 予定物が持ち出し規制(集計値・図・ハッシュのみ)を満たしているか

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.