submission-pipeline
Skill4 starsChanged 6 months agoMITView on GitHub
Pre-submission review battery — runs the peer-reviewer, integrity-reviewer, and fact-checker agents plus the deterministic audits in parallel over the whole manuscript, dedupes, confidence-gates, and saves one go/no-go report.
In this repository24 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- abstractSkill
- citation-auditSkill
- claim-checkSkill
- cover-letterSkill
- gap-finderSkill
- journal-fitSkill
- lit-briefingSkill
- literature-reviewSkill
- lit-ingestSkill
- lit-lintSkill
- manuscript-cycleSkill
- methods-reviewSkill
- noteSkill
- outlineSkill
- peer-reviewSkill
- plain-language-summarySkill
- reference-formatSkill
- response-to-reviewersSkill
- retroSkill
- review-resurfaceSkill
- scorecardSkill
- stats-checkSkill
The file
We split this skill into the rules it gives an agent
5 rules. About 0 are common, 3 are distinctive, and 2 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈3
Distinctive · estimate
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 24
Read MANUSCRIPT_MAP.md (thesis, contribution, venue) and assemble the manuscript file set (main.tex + \input sections).
- Distinctive: line 39
Keep a finding if any of:
- Very specific: line 46
Write the report to reports/submission-review-<date>.md (and surface a summary).
- Distinctive: line 85
Never auto-edits: Every fix to a reported claim is a Protected Claim — the author decides.
- Distinctive: line 86
No silent caps: If coverage is bounded (e.g.
≈ “Common” is an estimate: at least 1 in 5 of the 372,429 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Submission Pipeline
Core Rule
Before submission, run every reviewer lens at once, dedupe across them, keep only findings that survive a confidence gate, and produce a single go/no-go report with a submission checklist. This is breadth-first (the whole manuscript, all lenses) — distinct from /peer-review (one referee report) and /claim-check (depth on each claim). It reports; it does not edit. Fixing a flagged claim is the author's call (and a Protected Claim).
When to Use
Invoke with /submission-pipeline when:
- The manuscript is draft-complete and you want a pre-submission sweep
- You want to pre-empt Reviewer 2 across rigor, integrity, and facts in one pass
- Running headless (
/submission-pipeline mode:headless) to produce a report artifact
Process
Phase 1 — Scope
- Read
MANUSCRIPT_MAP.md(thesis, contribution, venue) and assemble the manuscript file set (main.tex+\inputsections). Note the target venue for/journal-fit.
Phase 2 — Parallel review (run together, don't serialize)
- Dispatch in parallel:
peer-revieweragent — novelty, soundness, claim↔evidence, structure, recommendation.integrity-revieweragent — overclaim, p-hacking/HARKing, citation misuse, missing limitations.fact-checkeragent — claim-by-claim Supported / Overstated / Unsupported / Uncited.
- In parallel, run the deterministic + checklist audits and collect their results:
/citation-audit(dangling/orphan/malformed refs), current compile-gate verdict, figure-orphan state./stats-check(statistical reporting),/methods-review(reproducibility),/journal-fit(venue fit),/gap-finder(uncited/unsupported sweep).
Phase 3 — Dedupe & merge
- Many lenses will flag the same sentence (e.g. an overclaim caught by peer-reviewer, integrity-reviewer, and fact-checker). Merge by
(file, locator, claim)into one finding that records which lenses raised it (agreement = signal).
Phase 4 — Confidence gate
- Keep a finding if any of:
- a deterministic check produced it (dangling
\cite, undefined ref, missing field) — always high-confidence; - ≥2 independent lenses agree on it;
- it is a single-lens finding rated high-severity by that lens (e.g. an unsupported central claim). Drop or mark low-confidence the single-lens, low-severity findings so the report is signal, not noise. Log what was dropped (no silent truncation).
- a deterministic check produced it (dangling
Phase 5 — Report
- Write the report to
reports/submission-review-<date>.md(and surface a summary). Include a go / revise / no-go recommendation tied to the findings, and a submission checklist.
Output Format
# Submission Review — <title> → <venue> (<date>)
Recommendation: GO | REVISE | NO-GO — <one-line reason>
## Blocking (must fix before submission)
- [file:locator] <finding> — lenses: {peer, integrity, fact, deterministic} — fix: <…>
## Should-fix
- ...
## Consider
- ... (low-confidence / single-lens — listed, not emphasized)
## Deterministic status
- citation-gate: <pass/FAIL> compile-gate: <pass/skip/FAIL> figure-orphan: <clean/N>
- citation-audit: <N issues> stats: <N> methods reproducibility: <PASS/GAP list>
## Submission checklist
- [ ] All \cite resolve · compile clean · no orphan floats
- [ ] Limitations section present · no causal overclaim · effect sizes + CIs
- [ ] Venue: length / reference style / display-item limits (confirm in author guidelines)
- [ ] Data/code availability statement · declarations
- [ ] Abstract numbers match the body
## Dropped (low-confidence, for transparency)
- <count> single-lens low-severity findingsPairs With
peer-reviewer / integrity-reviewer / fact-checker agents; /peer-review, /citation-audit, /stats-check, /methods-review, /journal-fit, /gap-finder; the citation-gate / compile-gate / figure-orphan hooks. Research analogue of the code kit's /review-pipeline.
Notes
- Headless (
mode:headless): emits the report artifact toreports/and a short summary; no interactive prompts. - Never auto-edits. Every fix to a reported claim is a Protected Claim — the author decides. The pipeline's job is to find, dedupe, and rank.
- No silent caps. If coverage is bounded (e.g. only changed sections), say so in the report.
- Distinct from
/project-health-style breadth: this is submission-readiness, gated on the venue and the cardinal rule.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

