brycewang-stanford/Auto-Empirical-Research-Skills / skills/24-Imbad0202-academic-research-skills/academic-pipeline
academic-pipeline
VerifiedOrchestrator for the full academic research pipeline: research -> write -> integrity check -> review -> revise -> re-review -> re-revise -> final integrity check -> finalize. Coordinates deep-research, academic-paper, and academic-paper-reviewer into a seamless 9-stage workflow with mandatory integrity verification, two-stage peer review, and reproducible quality gates. Triggers on: academic pipeline, research to paper, full paper workflow, paper pipeline, end-to-end paper, research-to-publication, complete paper workflow.
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 41.5 KB |
| agents/integrity_verification_agent.md | markdown | 22.3 KB |
| agents/pipeline_orchestrator_agent.md | markdown | 21.5 KB |
| agents/state_tracker_agent.md | markdown | 15.5 KB |
| examples/full_pipeline_example.md | markdown | 16.8 KB |
| examples/integrity_failure_recovery.md | markdown | 26.4 KB |
| examples/mid_entry_example.md | markdown | 12.3 KB |
| references/claim_verification_protocol.md | markdown | 2.7 KB |
| references/mode_advisor.md | markdown | 7.8 KB |
| references/pipeline_state_machine.md | markdown | 13.1 KB |
| references/plagiarism_detection_protocol.md | markdown | 13.5 KB |
| references/team_collaboration_protocol.md | markdown | 8.9 KB |
| templates/pipeline_status_template.md | markdown | 3.7 KB |
templates/pipeline_status_template.md
View on GitHub# Pipeline Status Dashboard Template
This template defines the output format for the Progress Dashboard. Switch between language versions based on user language.
---
## English Version
```
+=========================================+
| Academic Pipeline Status |
+=========================================+
| Topic: {topic} |
+-----------------------------------------+
Stage 1 RESEARCH [{status_icon}] {status_text}
{mode_line}
{outputs_line}
Stage 2 WRITE [{status_icon}] {status_text}
{mode_line}
{outputs_line}
Stage 3 REVIEW [{status_icon}] {status_text}
{mode_line}
{decision_line}
Stage 4 REVISE [{status_icon}] {status_text}
{revision_round_line}
{addressed_line}
Stage 3' RE-REVIEW [{status_icon}] {status_text}
{loop_count_line}
Stage 5 FINALIZE [{status_icon}] {status_text}
{format_line}
+-----------------------------------------+
| Materials: |
| [{icon}] RQ Brief |
| [{icon}] Methodology Blueprint |
| [{icon}] Bibliography |
| [{icon}] Synthesis Report |
| [{icon}] Paper Draft |
| [{icon}] Review Reports |
| [{icon}] Revision Roadmap |
| [{icon}] Revised Draft |
| [{icon}] Response to Reviewers |
| [{icon}] Final Paper |
+-----------------------------------------+
| Revision History: |
| {revision_history} |
+-----------------------------------------+
| Next Step: {next_step_suggestion} |
+=========================================+
```
---
## Field Definitions
### status_icon
| Status | Icon |
|--------|------|
| completed | `v` |
| in_progress | `..` |
| pending | ` ` (space) |
| skipped | `--` |
### status_text
| Status | Text |
|--------|------|
| completed | Completed |
| in_progress | In Progress |
| pending | Pending |
| skipped | Skipped |
### mode_line
Format: `Mode: {mode_name}`
- Only displayed when status is completed or in_progress
- If mode switched (e.g., plan -> full), display the full path
### outputs_line
Format: `Outputs: {output_1}, {output_2}, ...`
- Only displayed when status is completed
- List all deliverables for that stage
### decision_line
Format: `Decision: {Accept/Minor Revision/Major Revision/Reject}`
- Only displayed when Stage 3 or Stage 3' is completed
### revision_round_line
Format: `Revision Round: {current}/{max}`
- Only displayed when Stage 4 is in_progress
### addressed_line
Format: `Addressed: {count}/{total} required revisions`
- Only displayed when Stage 4 is in_progress
### loop_count_line
Format: `Loop: {count}/2`
- Only displayed for Stage 3'
### material icon
| Status | Icon |
|--------|------|
| available | `v` |
| missing | ` ` (space) |
### revision_history
One line per round:
```
Round {n}: {decision} | {addressed}/{total} items addressed
Pending: {pending_items_summary}
```
If no revision history, display "(No revision history yet)".
### next_step_suggestion
Auto-generated suggestion based on current state:
- Stage 1 completed: "Recommend proceeding to Stage 2 (WRITE) using {recommended_mode} mode"
- Stage 3 completed (Major): "Need to enter Stage 4 (REVISE), {N} required items"
- Stage 4 completed: "Recommend proceeding to Stage 3' (RE-REVIEW) to confirm revision quality"
- Stage 3' completed (Accept): "Congratulations! Proceed to Stage 5 (FINALIZE) to produce final version"
- Pipeline completed: "Pipeline complete! Final paper is ready."
---
## Simplified Version (Auto-appended after stage completion)
One-line progress bar:
```
Pipeline: [v]RESEARCH -> [v]WRITE -> [..]REVIEW -> [ ]REVISE -> [ ]FINALIZE
```
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| writing-skillsobra/superpowersUse when creating new skills, editing existing skills, or verifying skills work before deployment | Stars: 323k | Updated | Claude CodeCodex | Verified | Install |
| xlsxanthropics/skillsUse this skill any time a spreadsheet file is the primary input or output. This means any task where the user wants to: open, read, edit, or fix an existing .xlsx, .xlsm, .xltx, .csv, or .tsv file (e.g., adding columns, computing formulas, formatting, charting, cleaning messy data); create a new spreadsheet from scratch or from other data sources; or convert between tabular file formats. Trigger especially when the user references a spreadsheet file by name or path — even casually (like "the xlsx in my downloads") — and wants something done to it or produced from it. Also trigger for cleaning or restructuring messy tabular data files (malformed rows, misplaced headers, junk data) into proper spreadsheets. The deliverable must be a spreadsheet file. Do NOT trigger when the primary deliverable is a Word document, HTML report, standalone Python script, database pipeline, or Google Sheets API integration, even if tabular data is involved. | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |
| shipping-and-launchaddyosmani/agent-skillsPrepares production launches. Use when preparing to deploy to production, or when asking what needs to be in place before shipping. Use when you need a pre-launch checklist, when setting up monitoring, when planning a staged rollout, or when you need a rollback strategy. | Stars: 119k | Updated | Claude CodeCodex | Verified | Install |
| childhoodthedotmack/claude-memBabysit a shipped release after merge, publication, or deployment. Verify published packages, production behavior, installed plugins, and late CI or user reports until the observation window is clean; use babysit for PR readiness before release. | Stars: 118k | Updated | Claude CodeCodex | Verified | Install |