Menu
Analyzes the research repository structure, conventions, and patterns for paper organization, data pipeline layout, and test structure
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Reference for configuring, launching, and monitoring research iteration loops and analysis polish loops
Verifies the analysis pipeline runs end-to-end, outputs match expectations, and LaTeX compiles
Hands-on QA of the research analysis pipeline. Use whenever the user asks to verify the pipeline end-to-end, check output file integrity, validate table and figure generation, test data processing, or verify LaTeX compilation. Triggers on phrases like "test the pipeline", "QA the analysis", "check the outputs", "verify the tables", "run end-to-end", "does the paper compile", or any request to validate a research pipeline.
Define research question, hypotheses, methodology outline, and literature gap
Decompose a research question into cook-it-ready epic beads with methodology specifications
Comprehensive playbook for building rigorous, publication-quality research papers. Covers the full research output sequence from paper structure and statistical reporting through table formatting, figure design, LaTeX conventions, academic writing quality, and pre-submission review.
Based on SOC occupation classification
| name | Research Repository Analyst |
| description | Analyzes the research repository structure, conventions, and patterns for paper organization, data pipeline layout, and test structure |
Analyzes the research repository to understand its structure, coding conventions, and research pipeline patterns. Provides context for planning and decision-making.
src/analysis/, src/data/, paper/, tests/, docs/decisions/paper/ directory properly structured (main.tex, sections/, outputs/tables/, outputs/figures/)?docs/decisions/ follow the ADR template with sequential numbering?src/analysis/ organized by hypothesis or by method?Subagent spawned via the Task tool during the plan and spec-dev phases. Return findings directly to the caller.
Return a structured summary: