This skill should be used when the user asks to "outline my paper", "structure the paper", "design the paper sections", "create a paper outline", "organize my argument", or needs to design or refine paper structure. Generates a section-by-section outline with purpose, key arguments, estimated length, and narrative arc. Adapts to the paper type and venue conventions. Updates .papermill/state.md.
From papermillnpx claudepluginhub queelius/claude-anvil --plugin papermillThis skill uses the workspace's default tool permissions.
Guides Next.js Cache Components and Partial Prerendering (PPR) with cacheComponents enabled. Implements 'use cache', cacheLife(), cacheTag(), revalidateTag(), static/dynamic optimization, and cache debugging.
Migrates code, prompts, and API calls from Claude Sonnet 4.0/4.5 or Opus 4.1 to Opus 4.5, updating model strings on Anthropic, AWS, GCP, Azure platforms.
Configures VPN and dedicated connections like Direct Connect, ExpressRoute, Interconnect for secure on-premises to AWS, Azure, GCP, OCI hybrid networking.
Help the researcher design the structure of their paper. A good outline is the skeleton that determines whether the paper's argument flows logically. Produce a section-by-section plan that is specific to this paper, not a generic template.
Read .papermill/state.md (Read tool) for:
latex, markdown, or rmarkdown (affects section conventions).If .papermill/state.md does not exist, outlining can still proceed — ask the user to describe the thesis and intended contribution type directly. Suggest running /papermill:init afterward to persist the outline.
Also scan existing paper files (Glob/Read tools). If there is already a partial draft, read it to understand what exists.
Different paper types have different conventional structures. Identify which applies:
Ask the user if you are unsure. The structure should match the contribution type.
For each section, specify:
| Field | Description |
|---|---|
| Section title | The heading as it will appear in the paper |
| Purpose | What this section accomplishes for the reader (1 sentence) |
| Key content | Bullet points of what goes here (3-5 items) |
| Estimated length | Approximate page/paragraph count |
| Dependencies | What must be established before this section |
Example:
3. Preliminaries
Purpose: Establish notation and recall the key definitions the reader needs. Key content:
- Series system model (Definition 2.1)
- Masked failure time observation model
- Exponential lifetime assumption and its implications
- Notation table for symbols used throughout
Estimated length: 1.5 pages Dependencies: None (self-contained background)
After drafting the outline, verify the story:
Raise any structural issues with the user. Common problems:
Present the complete outline to the user. Ask:
Does this structure capture the argument you want to make? Would you reorder, merge, or split any sections?
Iterate until the user approves.
Once approved, update .papermill/state.md (Edit tool):
stage to outlining (or drafting if progressing).## Outline heading.Append a timestamped note documenting the outline creation.
Based on what the outline reveals, suggest the most relevant next step:
/papermill:thesis to refine the claim before drafting."/papermill:prior-art/papermill:experiment or /papermill:simulation/papermill:proof