Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
직접 명령은 검토 Prompt를 거치지 않습니다. 실행하기 전에 소스를 확인하세요.
npx skills add https://github.com/KYRIE66nb/codex-omx-public-config --skill paper-writing명령은 한 줄로 유지됩니다. 복사하기 전에 가로로 스크롤해 전체 내용을 확인하세요.
로컬 사본을 원하시나요? SkillsMP에서 현재 제공할 수 있는 파일을 다운로드하세요.
Personalized writing assistant with style transfer, error memory, grammar checking, and long-term writing preferences. Use when users ask for writing polishing, style mimicry, iterative correction, bilingual grammar checks, or persistent writing preferences by domain.
Academic paper AI content detection and rewriting assistant. Analyzes text for AI-generated characteristics, provides detailed rewrite suggestions. Supports .docx files, outputs reports and rewritten documents. Bilingual: Chinese & English.
解释代码、回答技术问题或概念问答时使用。直接给出答案,不启动开发流程。
SOC 직업 분류 기준
SKILL.md 표시 중
| name | paper-writing |
| description | Full paper writing pipeline. |
Orchestrate a complete paper writing workflow for: $ARGUMENTS
This skill chains five sub-skills into a single automated pipeline:
/paper-plan → /paper-figure → /paper-write → /paper-compile → /auto-paper-improvement-loop
(outline) (plots) (LaTeX) (build PDF) (review & polish ×2)
Each phase builds on the previous one's output. The final deliverable is a polished, reviewed paper/ directory with LaTeX source and compiled PDF.
ICLR — Target venue. Options: ICLR, NeurIPS, ICML. Affects style file, page limit, citation format.gpt-5.4 — Model used via a secondary Codex agent for plan review, figure review, writing review, and improvement loop.false to pause and wait for user approval after each phase.true, the improvement loop (Phase 5) pauses after each round's review to let you see the score and provide custom modification instructions. When false (default), the loop runs fully autonomously. Passed through to /auto-paper-improvement-loop.Override inline:
/paper-writing "NARRATIVE_REPORT.md" — venue: NeurIPS, human checkpoint: true
This pipeline accepts one of:
NARRATIVE_REPORT.md (best) — structured research narrative with claims, experiments, results, figuresPAPER_PLAN.md — skip Phase 1, start from Phase 2The more detailed the input (especially figure descriptions and quantitative results), the better the output.
Invoke /paper-plan to create the structural outline:
/paper-plan "$ARGUMENTS"
What this does:
Output: PAPER_PLAN.md with section plan, figure plan, citation scaffolding.
Checkpoint: Present the plan summary to the user.
📐 Paper plan complete:
- Title: [proposed title]
- Sections: [N] ([list])
- Figures: [N] auto-generated + [M] manual
- Target: [VENUE], [PAGE_LIMIT] pages
Shall I proceed with figure generation?
Invoke /paper-figure to generate data-driven plots and tables:
/paper-figure "PAPER_PLAN.md"
What this does:
figures/latex_includes.tex for easy insertionOutput: figures/ directory with PDFs, generation scripts, and LaTeX snippets.
illustration: true)Skip this step entirely if illustration is not set or is false.
If the paper plan includes architecture diagrams, pipeline figures, or method illustrations, invoke /paper-illustration:
/paper-illustration "[method description from PAPER_PLAN.md or NARRATIVE_REPORT.md]"
What this does:
figures/ai_generated/*.png — publication-quality method diagramsGEMINI_API_KEY environment variableWithout
illustration: true: Architecture diagrams must still be created manually (draw.io, Figma, TikZ) and placed infigures/before proceeding — same as before.
Checkpoint: List generated vs manual figures.
📊 Figures complete:
- Data plots (auto): [list]
- AI illustrations (auto): [list, if illustration: true]
- Manual (need your input): [list]
- LaTeX snippets: figures/latex_includes.tex
[If manual figures needed]: Please add them to figures/ before I proceed.
[If all auto]: Shall I proceed with LaTeX writing?
Invoke /paper-write to generate section-by-section LaTeX:
/paper-write "PAPER_PLAN.md"
What this does:
figures/latex_includes.texreferences.bib from citation scaffoldingOutput: paper/ directory with main.tex, sections/*.tex, references.bib, math_commands.tex.
Checkpoint: Report section completion.
✍️ LaTeX writing complete:
- Sections: [N] written ([list])
- Citations: [N] unique keys in references.bib
- Stale files cleaned: [list, if any]
Shall I proceed with compilation?
Invoke /paper-compile to build the PDF:
/paper-compile "paper/"
What this does:
latexmk -pdf with automatic multi-pass compilationpdftotextOutput: paper/main.pdf
Checkpoint: Report compilation results.
🔨 Compilation complete:
- Status: SUCCESS
- Pages: [X] (main body) + [Y] (references) + [Z] (appendix)
- Within page limit: YES/NO
- Undefined references: 0
- Undefined citations: 0
Shall I proceed with the improvement loop?
Invoke /auto-paper-improvement-loop to polish the paper:
/auto-paper-improvement-loop "paper/"
What this does (2 rounds):
Round 1: GPT-5.4 xhigh reviews the full paper → identifies CRITICAL/MAJOR/MINOR issues → Codex implements fixes → recompile → save main_round1.pdf
Round 2: GPT-5.4 xhigh re-reviews with conversation context → identifies remaining issues → Codex implements fixes → recompile → save main_round2.pdf
Typical improvements:
Output: Three PDFs for comparison + PAPER_IMPROVEMENT_LOG.md.
Format check (included in improvement loop Step 8): After final recompilation, auto-detect and fix overfull hboxes (content exceeding margins), verify page count vs venue limit, and ensure compact formatting. Any overfull > 10pt is fixed before generating the final PDF.
# Paper Writing Pipeline Report
**Input**: [NARRATIVE_REPORT.md or topic]
**Venue**: [ICLR/NeurIPS/ICML]
**Date**: [today]
## Pipeline Summary
| Phase | Status | Output |
|-------|--------|--------|
| 1. Paper Plan | ✅ | PAPER_PLAN.md |
| 2. Figures | ✅ | figures/ ([N] auto + [M] manual) |
| 3. LaTeX Writing | ✅ | paper/sections/*.tex ([N] sections, [M] citations) |
| 4. Compilation | ✅ | paper/main.pdf ([X] pages) |
| 5. Improvement | ✅ | [score0]/10 → [score2]/10 |
## Improvement Scores
| Round | Score | Key Changes |
|-------|-------|-------------|
| Round 0 | X/10 | Baseline |
| Round 1 | Y/10 | [summary] |
| Round 2 | Z/10 | [summary] |
## Deliverables
- paper/main.pdf — Final polished paper
- paper/main_round0_original.pdf — Before improvement
- paper/main_round1.pdf — After round 1
- paper/main_round2.pdf — After round 2
- paper/PAPER_IMPROVEMENT_LOG.md — Full review log
## Remaining Issues (if any)
- [items from final review that weren't addressed]
## Next Steps
- [ ] Visual inspection of PDF
- [ ] Add any missing manual figures
- [ ] Submit to [venue] via OpenReview / CMT / HotCRP
Large file handling: If the Write tool fails due to file size, immediately retry using Bash (cat << 'EOF' > file) to write in chunks. Do NOT ask the user for permission — just do it silently.
Don't skip phases. Each phase builds on the previous one — skipping leads to errors.
Checkpoint between phases when AUTO_PROCEED=false. Present results and wait for approval.
Manual figures first. If the paper needs architecture diagrams or qualitative results, the user must provide them before Phase 3.
Compilation must succeed before entering the improvement loop. Fix all errors first.
Preserve all PDFs. The user needs round0/round1/round2 for comparison.
Document everything. The pipeline report should be self-contained.
Respect page limits. If the paper exceeds the venue limit, suggest specific cuts before the improvement loop.
/idea-discovery "direction" ← Workflow 1: find ideas
implement ← write code
/run-experiment ← deploy experiments
/auto-review-loop "paper topic" ← Workflow 2: iterate research
/paper-writing "NARRATIVE_REPORT.md" ← Workflow 3: you are here
submit! 🎉
Or use /research-pipeline for the Workflow 1+2 end-to-end flow,
then /paper-writing for the final writing step.
| Phase | Duration | Can sleep? |
|---|---|---|
| 1. Paper Plan | 5-10 min | No |
| 2. Figures | 5-15 min | No |
| 3. LaTeX Writing | 15-30 min | Yes ✅ |
| 4. Compilation | 2-5 min | No |
| 5. Improvement | 15-30 min | Yes ✅ |
Total: ~45-90 min for a full paper from narrative report to polished PDF.