XcodeBuildMCP
XcodeBuildMCP provides tools for Xcode project management, simulator management, and app utilities.
[Writing] Claude / Codex skill for drafting abstracts, introductions, methods and experiments in the style of CVPR/ICCV/NeurIPS best papers, distilled from 60 award-winning papers.
作者の方は、このコードを README に貼れます。バッジはこのページにリンクします。
[](https://mcp.popnx.com/en/skills/gulucaptain-best-paper-writing-skill)同じ作業で AI をサービスにつなぐ MCP
XcodeBuildMCP provides tools for Xcode project management, simulator management, and app utilities.
XcodeBuildMCP provides tools for Xcode project management, simulator management, and app utilities.
Puter MCP enables AI tools to interact with Puter: manage files, websites, workers, and more
同じ種類の作業。Skill 一覧と同じ並び
| これ Best-Paper-Writing-Skill | MinerU | watermarks-remover | obsidian-skills | anysearch-skill | |
|---|---|---|---|---|---|
| 作者 | gulucaptain | opendatalab | guillaumemeyer | kepano | anysearch-ai |
| Skill 数 | 1 | 1 | 1 | 5 | 1 |
| GitHub スター | 416 | 83,972 | 27,796 | 53,183 | 6,906 |
| 最終コード更新 | 2026年10月29日 | 2026年11月18日 | 2026年11月17日 | 2026年9月15日 | 2026年11月13日 |
| ライセンス | – | – | MIT | MIT | Apache-2.0 |
gulucaptain による 1 個の Skill(指示セット)。AI が読んでそのとおりに作業します · MCP server ではありません
MCP = 手
AI を外部のサービスやデータにつなぎます(例:Notion を読む、請求書を作る)。プログラムやサーバーが動いている必要があります。
Skill = 手順書
作業のやり方を AI に教えるテキストファイル。どのサービスにもつながりません。
重なる部分もあります。ツールを呼ぶスクリプト付きの Skill や、知識だけを渡す MCP もあります。やりたい作業から選んでください。
Claude CodeClaude (เว็บ/แอป)Codex
提供元の README と repo のフォルダから判断
GitHub account gulucaptain (person), 8 years old
★ 416 stars, few users so far · code last changed 2026年10月29日
12 scripts that can run on a computer: evals/guidance-with-weaker-model/place-files.sh, evals/image-space-motion-prior/place-files.sh, evals/next-scale-autoregressive-images/place-files.sh, evals/participatory-alignment-dataset/place-files.sh and 8 more
No internet calls found in the scripts
No hooks or writes to machine settings found
Checked automatically from the repo files at commit b9eff99 (read only, nothing was run). Not a safety guarantee: read it and decide for yourself
まず:どの AI を使っていますか
使っているアプリを選ぶと、そのアプリでのインストール方法だけが表示されます
This skill has no license, so we do not hand out a ZIP from our site. Download it from GitHub and arrange the folder yourself, or use "Let the AI install it" above, which is easier
Download from GitHub (whole repo) ↗
Unzip it, then zip only the skills/bestpaper-writing folder again. The ZIP must have a bestpaper-writing folder with SKILL.md at the top level, no loose files
+Create skillUpload a skillpick bestpaper-writing.zip
SettingsCapabilitiesCode execution and file creation
Turn on Code execution and file creation first (newer menus: Create and edit files) · personal plans: Settings → Capabilities · Team/Enterprise: an admin turns it on under Organization settings → Plugins & skills · every plan, including Free
Upload once; it works in claude.ai and Claude Desktop, and in recent Claude Code signed in with a Claude account (not with an API key)
Cowork and cloud sessions use the skills turned on in your claude.ai account, not ~/.claude/skills on your computer (Claude Desktop scheduled tasks run locally and still load it)
Checked against official docs 2026年11月12日 · Source: support.claude.com, support.claude.com, code.claude.com
この文をコピーして Claude Code のチャットに貼り付けます
For one project, paste it into a chat that is open in that project’s folder · The AI always shows you the path before installing
The AI tells you what it will do first and asks your permission at every step
Claude Code を開き直し、/bestpaper-writing と入力するか関連する作業を頼むと Claude が自動で使います
Checked against official docs 2026年11月12日 · Source: code.claude.com
Skill は AI が従う指示です。入れる前にファイルを読み、信頼できる提供元のものだけを入れてください。
Mac:Command+スペースで Terminal と入力 · Windows:下のコマンドは PowerShell では動きません。上の「AI にインストールしてもらう」を使ってください
repo を一時フォルダにダウンロードし、SKILL.md のあるフォルダだけをコピーします
コマンドを確認中 · 確認が通るとコピーボタンが出ます
ChatGPT デスクトップアプリには Codex が組み込まれていて、Codex は ~/.agents/skills フォルダから Skill を読み込みます
ChatGPT デスクトップアプリで Codex を開き、この文をチャットに貼り付けます
The AI always shows you the path before installing
The AI tells you what it will do first and asks your permission at every step
bestpaper-writing フォルダを ~/.agents/skills/bestpaper-writing に置きます
~ はホームフォルダ($HOME)です
Skill は AI が従う指示です。入れる前にファイルを読み、信頼できる提供元のものだけを入れてください。
Mac:Command+スペースで Terminal と入力 · Windows:下のコマンドは PowerShell では動きません。上の「AI にインストールしてもらう」を使ってください
repo を一時フォルダにダウンロードし、SKILL.md のあるフォルダだけをコピーします
コマンドを確認中 · 確認が通るとコピーボタンが出ます
Checked against official docs 2026年11月15日 · Source: learn.chatgpt.com
自分でインストールした Skill は使えません。ディレクトリのプラグインに含まれる Skill だけが使えます
この Skill を ChatGPT で使うには、上の方法で ChatGPT デスクトップアプリを使ってください
Checked against official docs 2026年11月15日 · Source: learn.chatgpt.com
この文をコピーして Codex のチャットに貼り付けます · ChatGPT デスクトップアプリ内の Codex、Codex CLI、IDE 拡張機能で使えます
For one project, paste it into a chat that is open in that project’s folder · The AI always shows you the path before installing
The AI tells you what it will do first and asks your permission at every step
Codex は新しくインストールした Skill を自動で見つけます。表示されない場合は Codex を再起動してください · 使い方:ChatGPT では @ を入力して Skill を選びます · Codex CLI や IDE 拡張機能では /skills を実行するか、$ に続けて Skill 名を入力します
Checked against official docs 2026年11月15日 · Source: learn.chatgpt.com
Skill は AI が従う指示です。入れる前にファイルを読み、信頼できる提供元のものだけを入れてください。
Mac:Command+スペースで Terminal と入力 · Windows:下のコマンドは PowerShell では動きません。上の「AI にインストールしてもらう」を使ってください
repo を一時フォルダにダウンロードし、SKILL.md のあるフォルダだけをコピーします
コマンドを確認中 · 確認が通るとコピーボタンが出ます
この文をコピーして Cursor のチャットに貼り付けます
For one project, paste it into a chat that is open in that project’s folder · The AI always shows you the path before installing
The AI tells you what it will do first and asks your permission at every step
Cursor の Agent チャットで / を入力し bestpaper-writing を選ぶ
Checked against official docs 2026年11月12日 · Source: cursor.com
Skill は AI が従う指示です。入れる前にファイルを読み、信頼できる提供元のものだけを入れてください。
Mac:Command+スペースで Terminal と入力 · Windows:下のコマンドは PowerShell では動きません。上の「AI にインストールしてもらう」を使ってください
repo を一時フォルダにダウンロードし、SKILL.md のあるフォルダだけをコピーします
コマンドを確認中 · 確認が通るとコピーボタンが出ます
Skill を読めるほかのアプリ向けです。この文には Claude Code、Codex、Cursor のパスが入っていて、AI が使っているアプリに合わせて選びます · Copy this sentence into the app’s chat
For one project, paste it into a chat that is open in that project’s folder · The AI always shows you the path before installing
The AI tells you what it will do first and asks your permission at every step
Checked against official docs 2026年11月12日 · Source: code.claude.com, learn.chatgpt.com, cursor.com
Gemini CLI や GitHub Copilot など Agent Skills 対応の他のアプリはフォルダが違います。そのアプリのガイドを見て、SKILL.md のあるフォルダをコピーしてください。
2026年11月11日 に Claude Code、Codex、Cursor の公式ガイドで skill フォルダを確認
以下は提供元の repo の文章で、PopNx MCP の指示ではありません
最初の 8,000 文字を表示 · GitHub で全文を開く
---
name: bestpaper-writing
description: Draft or rewrite the title, Abstract, Introduction, Method and Experiments of an ML/CV paper in the style of CVPR/ICCV/NeurIPS best papers, distilled from 60 award papers, and plan and draw its figures (Figure 1, method overview, result figures) with award-paper layout and style. Use when the user either (A) fills in the intake form (assets/intake_form.html JSON) or describes problem, idea, method and results, or (B) pastes an existing abstract (or abstract plus introduction) to make it more convincing. Can write directly into a LaTeX template such as the CVPR author kit. Not for related-work surveys, rebuttals or plain proofreading.
---
# Best-Paper Writing (v1.2): Abstract, Introduction, Method, Experiments, Figures
Turn a description of a research project (or a draft abstract) into an Abstract and Introduction that read like a recent CVPR/ICCV/NeurIPS award paper.
This skill is grounded in a sentence-by-sentence annotation of **55 award papers** (2021–2025; 60 papers are analysed in total, and 5 of them (from 2024) are held out for testing, see `PAPER_LIST.md` in the repository root): what functions their abstracts and introductions contain, in which order, and how they read (`references/corpus-profile.md`). Award papers persuade through:
1. **A sharp motivation** — credit to specific prior work, then a concrete gap (what fails or is missing, when, and why), set up as a tension the paper resolves.
2. **An idea about the problem** — an observation from which the method follows, stated directly; a short handle for the idea when there is one (“next-brick prediction”).
3. **Clear positioning** — the closest work is named and one checkable difference is stated.
4. **Confident, evidenced claims told as a story** — results as claims with one or two headline numbers; the work is promoted where the evidence allows; a stance when the results support one. Weaknesses belong in the Limitations section, not in the Abstract or Introduction (author preference).
5. **Plain, rhythmic prose**. Each claim is stated once. Short, quotable sentences at the pivots (the bottleneck, the cause, the idea); the rest are full sentences (mean 20–24 words) that carry their reasons through *because*, *while*, *by*, *which*, not through trailing “, making …” clauses. Few logical connectors; colons allowed, **no dashes** (author preference). Mechanisms and examples instead of adjectives, short background, no implementation details.
Scope: title, Abstract and Introduction for all eight paper types (L1–L8, `references/routing.md`); also **Method** (`references/method.md`) and **Experiments** (`references/experiments.md`), mainly for method papers (L1/L2); and the **figures** of the paper (`references/figures.md`): a figure plan, Figure 1, the method overview and result figures, drawn where the content is known and left as planned placeholders where results are needed. Write the Abstract and Introduction first; Method, Experiments and figures follow the same claim map.
## Workflow
Do not write prose before Step 4.
### Step 0 — Intake (two input modes)
**Mode A: intake form.** If the user provides an intake JSON (exported from `assets/intake_form.html`, schema `bestpaper-intake/v1`), run `python3 scripts/intake_to_brief.py <file.json> --out brief.md --bib refs.bib` (paths relative to this skill folder) and work from `brief.md`; exit code 2 means a required field is missing. If the user describes the work in free text, load `references/intake-form.md` and map the description onto it. When a user has no material ready, point them to `assets/intake_form.html` (a local, offline form that exports JSON; the form is in Chinese).
**Mode B: complete abstract in.** If the user pastes an existing abstract (optionally with the introduction), do not rewrite it blindly. First reverse-engineer it into the intake fields of `references/intake-form.md` (task, dominant prior approach, gap and its reason, closest work, key insight, method components, results with numbers) and show the user a short table: field, what the draft says, status (present / vague / missing). Facts, numbers and terminology in the draft are the user's and are kept verbatim; never add a result, baseline or reference the draft does not contain. Then handle missing fields as below, and continue with Steps 1–8. In `report.md` add a **change table** (original sentence → revised sentence → reason, citing the award-paper pattern it follows) so the author can accept or reject each change.
In both modes:
- If a **required** field is missing (key idea, concrete gap with its reason, closest work, results with numbers), ask once in a compact list **before drafting**. In the same message, ask for the memorability fields that are empty (efficiency, integration with existing pipelines, supported inputs, applications, a concrete example, what is surprising, the trend it follows, the team’s name for the idea): these, not the prose, are what made award abstracts stand out in our comparisons. If the user cannot answer now, continue with `[TODO: …]` placeholders. Ask in plain text; do not depend on any agent-specific question tool.
- Never invent results, numbers, baselines, datasets or references.
### Step 1 — Claim, tension, handle, stance, headline numbers
Write these for yourself (they go into `report.md`, not the paper):
- **Claim**: `We show that [method/finding] [achieves what] [under which setting], because [key reason].`
- **Tension type**: tradeoff / capability-missing / obvious-fix-too-costly / unexplained-phenomenon / open-question / belief-overturned (`routing.md`).
- **Insight**: the observation about the problem the method follows from, written as a plain statement (not “Our key insight is …”).
- **Handle** (optional): a short phrase naming the idea, distinct from the method’s name. Use the user’s term if they have one; otherwise propose one in the report. When there is a handle, put it in the title.
- **Closest work**: 1–2 works and the checkable difference (mechanism, scope, cost, assumption, input, output, evaluation).
- **Stance** (optional): what the work changes for the field, only if the results support more than “better on benchmark B”.
- **Headline numbers**: the 1–2 results that carry the claim.
### Step 2 — Route
Load `references/routing.md`. Choose the paper type and motivation type; note the abstract arc and introduction plan.
### Step 3 — Claim map
Load `references/claim-calibration.md`. List each claim with its evidence and the **strongest wording the evidence supports**. Use it to make claims confident where supported and scoped where not — never to add disclaimers. Mark headline / supporting / table-only numbers.
### Step 4 — Skeleton
Load `references/introduction.md` and `references/abstract.md`. One line per paragraph (its message = its first sentence); one line per abstract sentence. Check against the award-paper tiers (`introduction.md` §2):
- **always**: credit to specific prior work → gap with reason → method → results;
- **usual**: opening setting or concrete scene; the insight just before the method;
- **for method papers**: a contrast with the closest work after the method;
- **optional**: contributions list, stance (at the end).
The abstract defaults to Setting → Gap → Method → Result (`abstract.md` §3).
Mark the **pivot sentences** (the bottleneck, the cause, the tension, the idea); they will be short and quotable. Then make a **claim index**: list every claim (gap, insight, each advantage, each result, stance) and the one paragraph where it appears. A claim listed under two paragraphs is merged into one. Generic field background gets at most two sentences.
### Step 5 — Draft with exemplars
For each paragraph, read 2–3 award-paper paragraphs with the same function and, if possible, the same paper type: `python3 scripts/find_exemplars.py --para <function> --type <L*>`; for sentences, `python3 scripts/find_exemplars.py <move>` or `--phrases <function>`; 質問、コツの共有、使えないことの報告ができます。「役に立った」の多い順です。