Academic Pipeline v3.21.1 — Full Academic Research Workflow Orchestrator Agent Skill

Orchestrator for the full academic research pipeline: research -> write -> integrity check -> review -> revise -> re-review -> re-revise…

Context cost
166k tokensestimated from the bundle, loaded when it triggers
Bundle
29 files · 664.1 kBtext throughout, nothing executable
Licence
Source-availablethe author’s own terms
Last change
—v3.23.0
Servers it uses
Noneruns standalone

What it does

Orchestrator 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 10-stage workflow with mandatory, coverage-bounded integrity checks, two-stage peer review, and auditable quality-assurance artifacts.

What this skill changes about the agent has not been set out here as a list. Its SKILL.md, shown below, says it in the author’s own words.

productivityresearch

The skill itself

A skill is instructions the model reads, so you can see what you are getting: below is the start of its SKILL.md. The front matter loads with every session, the body loads when the skill triggers, and the whole file comes with the install.

SKILL.md59.2 kB · preview
--- name: academic-pipeline metadata: version: "3.23.0" last_updated: "2026-10-03" depends_on: "deep-research, academic-paper, academic-paper-reviewer" status: active data_access_level: raw task_type: open-ended related_skills: - deep-research - academic-paper - academic-paper-reviewer ---
17# Academic Pipeline v3.23.0 — Full Academic Research Workflow Orchestrator
18
19A lightweight orchestrator that manages the complete academic pipeline from research exploration to final manuscript. It does not perform substantive work — it only detects stages, recommends modes, dispatches skills, manages transitions, and tracks state.
20
21> **Routing discipline (v3.9.2):** plugin and skills-copy installs do not load this repository's .claude/CLAUDE.md, so its routing core is repeated below, identical to shared/references/routing_core.md (#892). If routing has not settled when this skill loads, apply the core before dispatching any agent.
22
23<!-- routing-core:begin -->
24**Step 0 — Escape hatch check (before any classification):** If the user's first message begins with [direct-mode] (case-insensitive byte-0 token, optionally preceded by whitespace/newlines that are stripped on parse), record this fact, strip the prefix and surrounding whitespace from the message, and skip directly to **Step 1 explicit-intent handling** on the stripped content. The literal [direct-mode] is NOT passed through to the dispatched agent. If the stripped message itself has no clear skill named, Step 1 falls through to Step 3 clarification (the escape hatch bypasses cross-phase clarification (Step 2), not all routing). When the token is honored and the named agent or skill needs inputs the message does not supply, read that agent's or skill's file and ask for what it requires, in its terms. A [direct-mode] token after any other non-whitespace character is not the escape hatch, even when the message asks to skip questions: classify the message through Steps 1-3 as if the token were absent, and do not forward the token. Without the byte-0 token, naming an agent is not explicit intent: such a message goes through Steps 1-3 like any other, so cross-phase materials still get Step 2 clarification.
25
26Otherwise, classify the user's input:
27
281. **Explicit clear intent** — user invokes a specific skill via /ars-* slash command, or uses an unambiguous trigger keyword that maps to a single skill (e.g., "lit-review this", "review my paper", "draft an abstract"):
29 → Route directly; no clarification, no orchestrator detour.
30 → The request stays explicit when the mode's usual input is absent or a word in it has other everyday senses. A revision request with no reviewer comments is revision mode's "feel certain sections need improvement" case, and "revisar artículo" is the reviewer's trigger. Route to that mode and let the mode handle what is missing; do not reopen the choice of workflow.
31
322. **Cross-phase materials detected** — user provides artifacts spanning ≥ 2 pipeline phases without naming a specific skill (e.g., pre-written abstract + pre-collected literature; full draft + reviewer comments + bibliography):
33 → **Clarify**. Do NOT auto-route to a single-phase agent. List candidate workflows as a-d options in markdown body (NOT via AskUserQuestion tool). See shared/references/intent_clarification_protocol.md for the message template.
34 → Reason: clarification is the safest action when materials don't unambiguously identify intent. (v3.10 active conductor (#134) will handle this via structured intake; v3.9.2 asks.)
35
This is a preview of SKILL.md. Download or install the skill to get the whole thing.
In the file
SKILL.md8,015 words
Files29
LicenceSource-available
Why you can read it

Nothing in a skill executes. The client loads the text and the model follows it, so a skill can be audited the way a runbook is — by reading it.

What it costs in context

Skills are not billed by the call. They are paid for in context: every token the instructions occupy is a token your code, your diff and your conversation cannot use. Here is what this one takes and when it takes it.

≈280
always loaded
The name and description, so the model knows the skill exists and when to reach for it.
165,745
on trigger
The instruction body and 28 supporting files, read only when the skill fires.
83.0%
of a 200k window
Ten skills this size would not fit in the window together.
050k100k150k200k context window

166k tokens, estimated from the bundle at four bytes to the token, held for the rest of the session once it triggers. Heavy. Teams tend to install this one per project rather than globally, and load it only when the job comes up.

Servers bill, skills cost

A server charges by the month. A skill charges once per session, in context, and then keeps charging it for as long as the session lives.

Before and after

The same question, put to the same model twice: once as it comes, and once with these instructions loaded.

No worked example has been published for this skill yet.

The procedure it runs

The procedure has not been set out here step by step. It is in the body of its SKILL.md: the start of it is shown above, and the whole file comes with the install.

Prose, not code

These steps are written for a model to follow, not executed by a runtime. It can still be told to skip one, and it will say so when it does.

Servers it uses

None. This skill calls no MCP servers at all.

Everything it needs is in the instructions, so it works in a project with nothing connected — the model reads the file and changes how it works with what it can already reach.

Its SKILL.md does not declare which tools it asks the agent for, so what it touches is whatever the instructions themselves ask for — read them before you install it.

What it asks for
Writes filesnot declared
Network accessnot declared

This SKILL.md carries no allowed-tools line, so neither is declared. A skill grants no permissions of its own — it can only ask for tools your client already has.

What it will not do

Every skill is narrow, and the useful ones say where they stop. These are the jobs this one is the wrong tool for.

What this skill is not for has not been published here. Nothing is implied by that: it is a section the author has not filled in.

What is in the bundle

29 files, 664.1 kB on disk. A bundle is text throughout: the instructions the model reads, plus the templates it fills in. 1 file of its source is not in the download — listed after these, with why.

  • SKILL.md59.2 kB
  • agents/claim_ref_alignment_audit_agent.md45.4 kB
  • agents/collaboration_depth_agent.md10.0 kB
  • agents/integrity_verification_agent.md72.4 kB
  • agents/pipeline_orchestrator_agent.md177.9 kB
  • agents/state_tracker_agent.md27.4 kB
  • examples/full_pipeline_example.md18.1 kB
  • examples/integrity_failure_recovery.md27.5 kB
  • examples/mid_entry_example.md13.7 kB
  • references/ai_research_failure_modes.md16.0 kB
  • references/changelog.md5.9 kB
  • references/claim_audit_calibration_protocol.md14.6 kB
  • references/claim_verification_protocol.md27.8 kB
  • references/external_review_protocol.md6.3 kB
  • references/integrity_review_protocol.md7.3 kB
  • references/literature_corpus_consumers.md12.0 kB
  • references/mode_advisor.md8.0 kB
  • references/passport_as_reset_boundary.md19.1 kB
  • references/pipeline_state_machine.md28.7 kB
  • references/plagiarism_detection_protocol.md13.8 kB
  • references/process_summary_protocol.md16.2 kB
  • references/progress_dashboard_template.md1.5 kB
  • references/reinforcement_content.md1.4 kB
  • references/reproducibility_audit.md2.7 kB
  • references/score_trajectory_protocol.md3.9 kB
  • references/team_collaboration_protocol.md10.3 kB
  • references/two_stage_review_protocol.md3.0 kB
  • templates/pipeline_status_template.md3.8 kB
  • references/adapters/overview.md10.2 kB

Not in the download

Not carried is a type a skill download does not hold. Take it from its source.

  • references/adapters/.gitkeepnot carried
What is not in it

No dependencies and nothing executable: a skill is text the agent reads, so the download is 29 files — not the whole of its source: 1 file is left out. It is listed under the files, with why. The Source-available licence covers the templates and examples as well as the instructions.

Install

Installing copies the bundle into your project. Nothing runs at install time — the files sit on disk until the model reads them.

# Academic Pipeline v3.21.1 — Full Academic Research Workflow Orchestrator · 166k tokens when loaded · macOS, Linux mkdir -p .claude/skills && t=$(mktemp -d) && curl -fsSL -o "$t/bundle.tar.gz" https://mcprush.com/api/skills/academic-pipeline-v3-21-1-full-academic-research/bundle.tar.gz && tar -xzf "$t/bundle.tar.gz" -C "$t" && [ -d "$t/academic-pipeline-v3-21-1-full-academic-research" ] && { [ ! -e .claude/skills/academic-pipeline-v3-21-1-full-academic-research ] || { mv .claude/skills/academic-pipeline-v3-21-1-full-academic-research "$t/.previous" && echo "Previous copy moved to $t/.previous"; }; } && mv "$t/academic-pipeline-v3-21-1-full-academic-research" .claude/skills/ && echo "Installed .claude/skills/academic-pipeline-v3-21-1-full-academic-research"
On Windows, or any OS with Node 20+
npx mcprush@latest skill add imbad0202/academic-pipeline-v3-21-1-full-academic-research

Windows PowerShell says 'running scripts is disabled on this system'? Run Set-ExecutionPolicy -Scope CurrentUser RemoteSigned once, or type npx.cmd instead of npx (codex.cmd, gemini.cmd, grok.cmd likewise). PowerShell 7 needs neither. Writes to .claude/skills/academic-pipeline-v3-21-1-full-academic-research/ in the current project. For every project instead, run mkdir -p ~/.claude/skills && t=$(mktemp -d) && curl -fsSL -o "$t/bundle.tar.gz" https://mcprush.com/api/skills/academic-pipeline-v3-21-1-full-academic-research/bundle.tar.gz && tar -xzf "$t/bundle.tar.gz" -C "$t" && [ -d "$t/academic-pipeline-v3-21-1-full-academic-research" ] && { [ ! -e ~/.claude/skills/academic-pipeline-v3-21-1-full-academic-research ] || { mv ~/.claude/skills/academic-pipeline-v3-21-1-full-academic-research "$t/.previous" && echo "Previous copy moved to $t/.previous"; }; } && mv "$t/academic-pipeline-v3-21-1-full-academic-research" ~/.claude/skills/ && echo "Installed ~/.claude/skills/academic-pipeline-v3-21-1-full-academic-research" (macOS, Linux) — or add --global to the npx line. The curl line replaces .claude/skills/academic-pipeline-v3-21-1-full-academic-research/ only after the download succeeds, so files left there by another skill of the same name, or by an older release, do not mix in. A copy already there is moved aside, not deleted, and the line prints where. It appears as academic-pipeline in Gemini CLI, Codex, Copilot and Grok (its own name); Claude Code lists it by the folder name, academic-pipeline-v3-21-1-full-academic-research. Not in this download: 1 file of its source (which one, and why). Take it from its source.

Which clients pick it up on their own

A skill is a folder of text. Most of these read a skills folder and pick it up without being told; the rest take the same folder another way — an upload in the app, a parameter on an API call — and then choose it by its description just the same.

Claude Code.claude/skills/
Claude DesktopCustomize › Skills
ChatGPTSkills › Create › Upload
Cursor.cursor/skills/
VS Code.github/skills/
Codex CLI.agents/skills/
Gemini CLI.gemini/skills/
Grok Build.grok/skills/
Microsoft CopilotSkills › Upload a skill
PerplexityComputer › Skills › Upload a skill
DeepSeek Harness.dsh/skills/
Zed.agents/skills/
Devin Desktop.devin/skills/
Windsurf (legacy).windsurf/skills/
OpenAI Agents SDKInstructions or sandbox Skills
HTTP / APIa request parameter
This release
Version3.23.0
Publishedno release date on file
PriceFree
Referenceimbad0202/academic-pipeline-v3-21-1-full-academic-research

Versions

v3.23.0 is what is on the shelf; no release here carries a date. Instructions change more often than APIs do — a skill can be rewritten entirely without anything it depends on moving.

v3.23.0
  • No earlier releases have been published to the marketplace.
Pinning

The install command always fetches the release that is current the day you run it — v3.23.0 today — and cannot ask for an earlier one. The copy on your disk does not change until you run it again.

Reviews

—no reviews yet

Nobody has reviewed this skill yet. The rating is the mean of the reviews written here, so there is none until somebody writes the first.

Sign in to review it

A review is tied to an account so it can be answered, edited and taken down by the person who wrote it.

Sign in
Who can post

Anybody with an account, one review each. It carries the version that was current when you wrote it, and the publisher may reply once.

Publisher
Servers0
Claim this skill