pre-submission-reviewlisted

Pre-submission review of a manuscript Heath authored or co-authored, before it goes to a journal or funder. The output is ALWAYS a Google Doc copy of the manuscript with visible inline review markup (red strikethrough for old text + red insertion for new text — both visible side-by-side) plus margin comments. NEVER a journal-style prose review written into a fresh blank doc. Same multi-agent architecture as paper-reviewer (Coordinator → 6 parallel specialists → Synthesizer → Refiner) with three critical inversions: stance is INTERNAL ADVISOR ("find issues so the author can fix them, not so a reviewer can score them"), voice is HEATH'S MANUSCRIPT voice (NOT peer-review voice), output is a marked-up copy via mark_changes_in_google_doc + insert_comment_in_google_doc on a doc made by copy_google_doc. TRIGGER on any phrasing where Heath wants HIS OWN manuscript reviewed before submission. All of these route here: "review my paper before I submit" "pre-submission review" "review the <topic> manuscript" / "review th
coleoguy/tealc · ★ 0 · Code & Development · score 68

Install: claude install-skill coleoguy/tealc

# Pre-Submission Review (TEALC) ## ⚠ FIRST READ — call ONE TOOL, do not assemble the workflow yourself **Use the tool `pre_submission_review(...)`** for ANY pre-submission review request. That single tool deterministically runs the entire 5-specialist + synthesizer + copy + markup + comments pipeline in Python — guaranteed to produce a marked-up Google Doc copy, guaranteed never to fall through to a journal-style prose review. Pass exactly ONE of these source inputs, in order of preference: 1. **`doc_url=<URL or doc_id>`** — fastest. If Heath pasted a `docs.google.com` link, OR you already have the doc_id from a prior tool call, use this. The tool extracts the ID, reads the doc directly via the Drive API, and skips ALL Drive lookups. NO project lookup, NO `find_project_manuscript`, NO `find_resource`, NO `list_research_projects`. Just one call. 2. **`project=<name or fragment>`** — when Heath names a project but didn't share a link. The orchestrator calls `find_project_manuscript(project)` internally to locate the current manuscript at `<project>/manuscript/*Manuscript*.gdoc`. 3. **`manuscript_path=<absolute path>`** — fallback when the project finder picks the wrong file or the manuscript lives outside the standard layout. ``` # Best — Heath just shared a Google Doc link: pre_submission_review( doc_url="https://docs.google.com/document/d/1AOrf6A.../edit", venue="MBE", ) # Same thing with just the bare ID (also accepted): pre_submission