openlair/dr-claw/aris-paper-plan

Claude Code and agent skill by openlair/dr-claw

Trust tier 2
  • community
LLM review pending
Source check pending

Checking that the SKILL.md file is still in the repository.

Generate a structured paper outline from review conclusions and experiment results. Use when user says \"写大纲\", \"paper outline\", \"plan the paper\", \"论文规划\", or wants to create a paper plan before writing.

Install

npx vskill@latest install openlair/dr-claw/aris-paper-plan

SKILL.md

The same SKILL.md was published earlier as openlair/dr-claw/aris-paper-plan.

Paper Plan: From Review Conclusions to Paper Outline

Generate a structured, section-by-section paper outline from: $ARGUMENTS

Constants

  • REVIEWER_MODEL = `gpt-5.4` — Model used via Codex MCP for outline review. Must be an OpenAI model.
  • TARGET_VENUE = `ICLR` — Default venue. User can override (e.g., /aris-paper-plan "topic" — venue: NeurIPS). Supported: ICLR, NeurIPS, ICML, CVPR, ACL, AAAI, ACM, IEEE_JOURNAL (IEEE Transactions / Letters), IEEE_CONF (IEEE conferences).
  • MAX_PAGES — Page limit. For ML conferences: main body to Conclusion end (excluding references, appendix). ICLR=9, NeurIPS=9, ICML=8. For IEEE venues: references ARE included in page count. IEEE journal Transactions ≈ 12-14 pages total, Letters ≈ 4-5 pages total; IEEE conference ≈ 5-8 pages total (including references).

Inputs

The skill expects one or more of these in the project directory:

  1. NARRATIVE_REPORT.md or STORY.md — research narrative with claims and evidence
  2. GPT54_AUTO_REVIEW.md — auto-review loop conclusions
  3. Experiment results — JSON files in figures/, screen logs, tables
  4. IDEA_REPORT.md — from idea-discovery pipeline (if applicable)
  5. Compact files (if available): IDEA_CANDIDATES.md, findings.md, EXPERIMENT_LOG.md — preferred over full files when present, saves context window

If none exist, ask the user to describe the paper's contribution in 3-5 sentences.

Orchestra-Guided Writing Overlay

Keep the existing insleep workflow and outputs, but use the shared references below to improve the quality of the story and outline.

  • Read ../ml-paper-writing/references/writing-guide.md when framing the one-sentence contribution, Abstract, Introduction, Related Work, or hero figure.
  • Read ../ml-paper-writing/references/checklists.md before freezing the outline for a specific venue.
  • Only load these references when needed; do not paste their full contents into the working draft.

Workflow

Step 1: Extract Claims and Evidence

First check for `CLAIMS_FROM_RESULTS.md` — if it exists (generated by /aris-result-to-claim at the end of Workflow 2), use it as the starting point for claims. This file contains validated claims already mapped to experiment evidence. Merge with any additional claims from the narrative documents below.

If CLAIMS_FROM_RESULTS.md does not exist, extract claims from scratch:

Read all available narrative documents and extract:

  1. Core claims (3-5 main contributions)
  2. One-sentence contribution (the single sentence that best states what the paper contributes)
  3. Evidence for each claim (which experiments, which metrics, which figures)
  4. Known weaknesses (from reviewer feedback)
  5. Suggested framing (from review conclusions)

Build a Claims-Evidence Matrix:

markdown
| Claim | Evidence | Status | Section |
|-------|----------|--------|---------|
| [claim 1] | [exp A, metric B] | Supported | §3.2 |
| [claim 2] | [exp C] | Partially supported | §4.1 |
Step 2: Determine Paper Type and Structure

Based on TARGET_VENUE and paper content, classify and select structure.

Before committing to a structure, apply the narrative principle from ../ml-paper-writing/references/writing-guide.md:

  • The paper should tell one coherent technical story.
  • By the end of the Introduction, the outline should make the What, Why, and So What explicit.
  • Front-load the most important material: title, abstract, introduction, and hero figure. Reviewers often form a judgment before reading the full method.

IMPORTANT: The section count is FLEXIBLE (5-8 sections). Choose what fits the content best. The templates below are starting points, not rigid constraints.

Empirical/Diagnostic paper:

1. Introduction (1.5 pages)
2. Related Work (1 page)
3. Method / Setup (1.5 pages)
4. Experiments (3 pages)
5. Analysis / Discussion (1 page)
6. Conclusion (0.5 pages)

Theory + Experiments paper:

1. Introduction (1.5 pages)
2. Related Work (1 page)
3. Preliminaries & Modeling (1.5 pages)
4. Experiments (1.5 pages)
5. Theory Part A (1.5 pages)
6. Theory Part B (1.5 pages)
7. Conclusion (0.5 pages)
— Total: 9 pages

Theory papers often need 7 sections (splitting theory into estimation + optimization, or setup + analysis). The total page budget MUST sum to MAX_PAGES.

Theory papers should:

  • Include proof sketch locations (not just theorem statements)
  • Plan a comparison table of prior theoretical bounds vs. this paper's bounds
  • Identify which proofs go in appendix vs. main body

Method paper:

1. Introduction (1.5 pages)
2. Related Work (1 page)
3. Method (2 pages)
4. Experiments (2.5 pages)
5. Ablation / Analysis (1 page)
6. Conclusion (0.5 pages)
Step 3: Section-by-Section Planning

For each section, specify:

markdown
### §0 Abstract
-**What we achieve**: [the paper's specific contribution, not field-level background]
-**Why it matters / is hard**: [why this problem is important and non-trivial]
-**How we do it**: [approach in one sentence]
-**Evidence**: [what supports the claim]
-**Most remarkable result**: [strongest quantitative or theoretical result]
-**Estimated length**: 150-250 words
-**Self-contained check**: can a reader understand this without the paper?
### §1 Introduction
-**Opening hook**: [1-2 sentences that motivate the problem]
-**Gap / challenge**: [what's missing in prior work, and why prior work is insufficient]
-**One-sentence contribution**: [the main takeaway of the paper]
-**Approach overview**: [what we do differently]
-**Key questions**: [the research questions this paper answers]
-**Contributions**: [2-4 numbered bullets, specific and falsifiable, matching Claims-Evidence Matrix]
-**Results preview**: [the strongest result or comparison to surface early]
-**Hero figure**: [describe what Figure 1 should show — MUST include clear comparison if applicable]
-**Estimated length**: 1.5 pages
-**Key citations**: [3-5 papers to cite here]
-**Front-loading check**: [would a skim reader know the main claim before reaching the method?]
### §2 Related Work
-**Subtopics**: [2-4 categories of related work]
-**Positioning**: [how this paper differs from each category]
-**Minimum length**: 1 full page (at least 3-4 paragraphs with substantive synthesis)
-**Organization rule**: organize by methodological family / assumption / question, not paper-by-paper
-**Must NOT be just a list** — synthesize, compare, and position
### §3 Method / Setup / Preliminaries
-**Notation**: [key symbols and their meanings]
-**Problem formulation**: [formal setup]
-**Method description**: [algorithm, model, or experimental design]
-**Formal statements**: [theorems, propositions if applicable]
-**Proof sketch locations**: [which key steps appear here vs. appendix]
-**Estimated length**: 1.5-2 pages
### §4 Experiments / Main Results
-**Figures planned**:
-Fig 1: [description, type: bar/line/table/architecture, WHAT COMPARISON it shows]
-Fig 2: [description]
-Table 1: [what it shows, which methods/baselines compared]
-**Data source**: [which JSON files / experiment results]
### §5 Conclusion
-**Restatement**: [contributions rephrased, not copy-pasted from intro]
-**Limitations**: [honest assessment — reviewers value this]
-**Future work**: [1-2 concrete directions]
-**Estimated length**: 0.5 pages
Step 4: Figure Plan

List every figure and table:

markdown
## Figure Plan
| ID | Type | Description | Data Source | Priority |
|----|------|-------------|-------------|----------|
| Fig 1 | Hero/Architecture | System overview + comparison | manual | HIGH |
| Fig 2 | Line plot | Training curves comparison | figures/exp_A.json | HIGH |
| Fig 3 | Bar chart | Ablation results | figures/ablation.json | MEDIUM |
| Table 1 | Comparison table | Main results vs. baselines | figures/main_results.json | HIGH |
| Table 2 | Theory comparison | Prior bounds vs. ours | manual | HIGH (theory papers) |

CRITICAL for Figure 1 / Hero Figure: Describe in detail what the figure should contain, including:

  • Which methods are being compared
  • What the visual difference should demonstrate
  • Caption draft that clearly states the comparison
  • Why the figure helps a skim reader understand the paper before reading the full method
Step 5: Citation Scaffolding

For each section, list required citations:

markdown
## Citation Plan
-§1 Intro: [paper1], [paper2], [paper3] (problem motivation)
-§2 Related: [paper4]-[paper10] (categorized by subtopic)
-§3 Method: [paper11] (baseline), [paper12] (technique we build on)

Citation rules (from claude-scholar + Imbad0202/academic-research-skills):

  1. NEVER generate BibTeX from memory — always verify via search or existing .bib files
  2. Every citation must be verified: correct authors, year, venue
  3. Flag any citation you're unsure about with [VERIFY]
  4. Prefer published versions over arXiv preprints when available
Step 6: Cross-Review with REVIEWER_MODEL

Send the complete outline to GPT-5.4 xhigh for feedback:

mcp__codex__codex:
model: gpt-5.4
config: {"model_reasoning_effort": "xhigh"}
prompt: |
Review this paper outline for a [VENUE] submission.
[full outline including Claims-Evidence Matrix]
Score 1-10 on:
1. Logical flow — does the story build naturally?
2. Claim-evidence alignment — every claim backed?
3. Missing experiments or analysis
4. Positioning relative to prior work
5. Page budget feasibility (MAX_PAGES = main body to Conclusion end, excluding refs/appendix)
6. Front-matter strength — are the abstract, introduction, and hero figure plan strong enough for skim-reading reviewers?
For each weakness, suggest the MINIMUM fix.
Be specific and actionable — "add X" not "consider more experiments".

Apply feedback before finalizing.

Step 7: Output

Save the final outline to PAPER_PLAN.md in the project root:

markdown
# Paper Plan
**Title**: [working title]
**One-sentence contribution**: [single-sentence statement of the paper's core takeaway]
**Venue**: [target venue]
**Type**: [empirical/theory/method]
**Date**: [today]
**Page budget**: [MAX_PAGES] pages (main body to Conclusion end, excluding references & appendix)
**Section count**: [N] (must match the number of section files that will be created)
## Claims-Evidence Matrix
[from Step 1]
## Structure
[from Step 2-3, section by section]
## Figure Plan
[from Step 4, with detailed hero figure description]
## Citation Plan
[from Step 5]
## Reviewer Feedback
[from Step 6, summarized]
## Next Steps
-[ ] /aris-paper-figure to generate all figures
-[ ] /aris-paper-write to draft LaTeX
-[ ] /aris-paper-compile to build PDF

This is the start of the file. Read the full SKILL.md on GitHub.

Security

  • Security scanPassed, 96 of 100Pattern checks on the skill's files.
  • Model reviewNot runA model review is scheduled for the next rescan.

Quality evaluation

  • Task evaluationNot runNo evaluation yet. Run one in Skill Studio.

Source

Popularity

Repository stars
1,200
Repository forks
144
Repository npm downloads, 7 days
25
7-day trend score
44

Stars and forks are for the whole GitHub repository, not this skill alone. Downloads are for the repository's npm package. Refreshed 21 May 2026, 6 months ago.

Works with

Any agent vskill installs to: 56 targets in all. These 39 have a page on this site.

  • Claude Code
  • Cursor
  • GitHub Copilot
  • Windsurf
  • Codex
  • Gemini CLI
  • Cline
  • Amp
  • Roo Code
  • Goose
  • Continue
  • Kilo Code
  • Junie
  • Trae
  • OpenHands
  • Qwen Code
  • AI Agent
  • Tabnine Chat
  • Sourcegraph Cody
  • Amazon Q
  • Firebase Genkit
  • Sweep
  • Devin
  • Phind
  • Mentat
  • Claude Desktop
  • Aider
  • GPT Pilot
  • Plandex
  • bolt.new
  • v0
  • Replit Agent
  • Anse
  • TypingMind
  • BetterChatGPT
  • LibreChat
  • Warp AI
  • Pieces
  • Fig AI
Embed badge
vskill VERIFIED badge
[![vskill VERIFIED](https://verified-skill.com/api/v1/skills/openlair/dr-claw/aris-paper-plan/badge)](https://verified-skill.com/skills/openlair/dr-claw/aris-paper-plan)

Something wrong with this skill or its page? Tell us.