paper writing

Writing Community

Skill notes

Overview

This skill chains five sub-skills into a single automated pipeline: Each phase builds on the previous one's output. The final deliverable is a polished, reviewed paper/ directory with LaTeX source and compiled PDF. In this hybrid pack, the pipeline itself is unchanged, but paper-plan and paper-write use Orchestra-adapted shared references for stronger story framing and prose guidance.

Constants

VENUE = ICLR — Target venue. Options: ICLR, NeurIPS, ICML, CVPR, ACL, AAAI, ACM, IEEE_JOURNAL (IEEE Transactions / Letters), IEEE_CONF (IEEE conferences). Affects style file, page limit, citation format. MAX_IMPROVEMENT_ROUNDS = 2 — Number of review→fix→recompile rounds in the improvement loop. REVIEWER_MODEL = gpt-5.5 — Model used via Codex MCP for plan review, figure review, writing review, and improvement loop.

Inputs

This pipeline accepts one of: NARRATIVE_REPORT.md (best) — structured research narrative with claims, experiments, results, figures Research direction + experiment results — the skill will help draft the narrative first Existing PAPER_PLAN.md — skip Phase 1, start from Phase 2 The more detailed the input (especially figure descriptions and quantitative results), the better the output.

Optional: Style reference (— style-ref: <source>, opt-in)

Lets the user steer structural style (section ordering, theorem density, sentence cadence, figure density, bibliography style) of the generated paper toward a reference paper they admire. Default OFF — when the user does not pass — style-ref, do nothing differently from before. When — style-ref: <source> is in $ARGUMENTS, run the helper FIRST, before Phase 1 (paper-plan): Then forward — style-ref: <source> only to the writer-side sub-skills:

Phase 0: Assurance Setup

Resolve the active assurance level and persist it so Phase 6's external verifier reads the same value. Run once at pipeline start, before Phase 1. Resolution order (first match wins): Explicit — assurance: draft | submission in $ARGUMENTS Derived from — effort:

Fluxly profile Runtime and permissions are inferred by Fluxly static checks, not author declarations or runtime test results.
Domain
Writing
Author-declared agents
No explicit declaration found; this is not inferred or tested compatibility
Static check
88 / 100 · heuristic scan, not runtime safety proof
Runtime evidence
Not run; no isolated runtime test evidence is currently recorded
Author / version / license
@wanshuiyin · no license declared
Token usage
Heavy
Setup complexity
Manual integration
External API key
Required · Gemini
Operating systems
Unspecified (assume cross-platform)
Runtime requirements
No explicit requirements detected
Detected file/system behavior
  • Read-only
  • Write / modify
  • Shell exec
  • Env read
Network behavior
External requests
Install commands
None (reference only)

Heads up: Tool permissions are not declared; actual access depends on the runtime.

01
Phase 0: Assurance Setup

Resolve the active `assurance` level and persist it so Phase 6's external verifier reads the same value. Run once at pipeline start, before Phase 1. Resolution order (first match wins): Explicit `— assurance: draft | submission` in `$ARGUMENTS` Derived from `— effort:`

02
Phase 1: Paper Plan

Invoke `/paper-plan` to create the structural outline: If `— style-ref: <source>` was passed in `$ARGUMENTS` and the helper succeeded above, append `— style-ref: <source>` to the invocation: `/paper-plan "<topic> — style-ref: <source>"`. (Writer-side phase — forwarding is allowed; reviewer/auditor phases below must not see the style ref.) What this does: Parse NARRATIVE_REPORT.md for claims, evidence, and figure descriptions

03
Phase 2: Figure Generation

If `— style-ref: <source>` was passed in `$ARGUMENTS` and the helper succeeded above, append `— style-ref: <source>` to every writer-side sub-skill invocation in this pipeline (Phases 1, 2b, 3, 5). Do not append it to reviewer/auditor invocations (Phases 4.5, 4.7, 5.5, 5.8). Invoke `/paper-figure` to generate data-driven plots and tables: What this does: Read figure plan from PAPER_PLAN.md Generate matplotlib/seaborn plots from JSON/CSV data

04
Phase 3: LaTeX Writing

Invoke `/paper-write` to generate section-by-section LaTeX: If `— style-ref: <source>` was passed in `$ARGUMENTS` and the helper succeeded above, append `— style-ref: <source>` to the invocation: `/paper-write "PAPER_PLAN.md — style-ref: <source>"`. What this does: Write each section following the plan, with proper LaTeX formatting Insert figure/table references from `figures/latex_includes.tex`

05
Phase 4: Compilation

Invoke `/paper-compile` to build the PDF: What this does: `latexmk -pdf` with automatic multi-pass compilation Auto-fix common errors (missing packages, undefined refs, BibTeX syntax) Up to 3 compilation attempts

06
Phase 4.5: Proof Verification (theory papers only)

Skip this phase if the paper contains no theorems, lemmas, or proofs.

07
Phase 4.7: Paper Claim Audit

Skip if no result files exist (e.g., survey/position papers with no experiments).

08
Phase 5: Auto Improvement Loop

Invoke `/auto-paper-improvement-loop` to polish the paper: If `— style-ref: <source>` was passed in `$ARGUMENTS` and the helper succeeded above, append `— style-ref: <source>` to the invocation: `/auto-paper-improvement-loop "paper/ — style-ref: <source>"`. The improvement loop's reviewer sub-agent will still NOT see the style ref (the loop's own SKILL forbids it); only the fix-implementation phase consumes it.

09
Phase 5.5: Final Paper Claim Audit (MANDATORY submission gate)

After `/auto-paper-improvement-loop` finishes, rerun `/paper-claim-audit` before the final report whenever the paper contains numeric claims and machine-readable raw result files exist. Use the same detectors as Phase 4.7: numeric-claim regex over `paper/main.tex` and `paper/sections/*.tex` raw-evidence file search in `results/`, `outputs/`, `experiments/`, and `figures/` for `.json`, `.jsonl`, `.csv`, `.tsv`, `.yaml`, or `.yml`

10
Phase 5.6: Kill-Argument Adversarial Review (theory / scope-heavy papers)

After Phase 5.5 (claim audit) passes, run `/kill-argument` whenever the paper is theory-heavy or makes explicit scope/generality claims in the title or abstract. This is a final adversarial check that complements the claim/citation/proof audits: those verify *local correctness* (numbers match, cites resolve, theorems prove); kill-argument tests *headline-level* survival — whether the paper as a whole answers the worst rejection paragraph a senior area chair would write.

11
Phase 5.8: Citation Audit (submission gate)

After the final paper-claim-audit passes, run `/citation-audit` to verify every `\cite{...}` along three axes: existence, metadata correctness, and context appropriateness. This is the fourth and final layer of the evidence-and-claim assurance stack (`experiment-audit` → `result-to-claim` → `paper-claim-audit` → `citation-audit`).

12
Phase 6: Final Report

Phase 6.0 — Submission Gate Before writing the Final Report, resolve the active assurance level. This uses the same derivation rule as Phase 0 so a run where Phase 0 was skipped or its write failed cannot silently downgrade a `beast` / `max` / `— assurance: submission` invocation back to draft.

Discussion

Powered by GitHub Discussions. Sign in with GitHub to comment, react, or subscribe.