openlair/dr-claw/aris-paper-plan
Claude Code and agent skill by openlair/dr-claw
- community
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-planSKILL.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:
- NARRATIVE_REPORT.md or STORY.md — research narrative with claims and evidence
- GPT54_AUTO_REVIEW.md — auto-review loop conclusions
- Experiment results — JSON files in
figures/, screen logs, tables - IDEA_REPORT.md — from idea-discovery pipeline (if applicable)
- 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.mdwhen framing the one-sentence contribution, Abstract, Introduction, Related Work, or hero figure. - Read
../ml-paper-writing/references/checklists.mdbefore 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:
- Core claims (3-5 main contributions)
- One-sentence contribution (the single sentence that best states what the paper contributes)
- Evidence for each claim (which experiments, which metrics, which figures)
- Known weaknesses (from reviewer feedback)
- Suggested framing (from review conclusions)
Build a Claims-Evidence Matrix:
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:
Theory + Experiments paper:
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:
Step 3: Section-by-Section Planning
For each section, specify:
Step 4: Figure Plan
List every figure and table:
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:
Citation rules (from claude-scholar + Imbad0202/academic-research-skills):
- NEVER generate BibTeX from memory — always verify via search or existing .bib files
- Every citation must be verified: correct authors, year, venue
- Flag any citation you're unsure about with
[VERIFY] - 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:
Apply feedback before finalizing.
Step 7: Output
Save the final outline to PAPER_PLAN.md in the project root:
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
- SKILL.md in the repositoryCheckingskills/aris-paper-plan/SKILL.md
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
[](https://verified-skill.com/skills/openlair/dr-claw/aris-paper-plan)