---

name: academic-research-suite description: > ARS-Codex research, academic writing, manuscript review, and experiment planning. Use for deep research, literature or systematic reviews, meta-analysis, research questions, paper drafts, revisions, revision roadmaps, abstracts, citations, integrity checks, peer review, and research-to-paper workflows. Korean: 논문 심사, 논문 수정, 초록 작성, 체계적 문헌고찰, 연구부터 논문까지. Español: revisión de literatura, revisar artículo, enmendar mi artículo, escribir resumen, investigación a artículo. Also use for ARS aliases: /ars-plan, /ars-outline, /ars-abstract, /ars-lit-review, /ars-citation-check, /ars-disclosure, /ars-format-convert, /ars-3w, /ars-revision-coach, /ars-revision, /ars-reviewer, /ars-mark-read, /ars-unmark-read, /ars-cache-invalidate, /ars-rebuttal-audit, /ars-full. Role prompts, references, templates, and handoff schemas live under ars/. metadata: version: "3.22.0" upstream_suite: "academic-research-skills" codex_adapter: true allowed-tools: Read, Glob, Grep, WebSearch, Bash(uv *), Bash(python *), Bash(python3 *)

ARS-Codex

This is a Codex adapter for the ARS suite. The vendored ARS content lives under ars/; keep it as source material and route through this file first.

Versioning

This Codex package is version 3.22.0. The repo-root VERSION, this SKILL.md metadata version, and manifest.json adapter_version must match. Starting at 3.22.0, this release number also matches the vendored ARS suite. The exact upstream version, tag, and commit are recorded in manifest.json; historical 0.1.x package releases retain their original numbers.

First Rule

Do not load the whole suite by default. Select one workflow, read that workflow's WORKFLOW.md, then load only the agent, reference, template, or shared files needed for the user's current stage.

The internal workflow entry files are named WORKFLOW.md, not SKILL.md, so Codex registers only this root router skill instead of exposing every vendored upstream workflow as a separate skill.

Workflow Router

Choose the workflow by intent:

| User intent | Read first | |---|---| | Deep research, literature review, systematic review, meta-analysis, fact-checking, research question refinement | ars/deep-research/WORKFLOW.md | | Academic paper writing, paper outline, abstract, revision, citation formatting, AI disclosure, LaTeX/DOCX/PDF formatting guidance | ars/academic-paper/WORKFLOW.md | | Paper review, peer review simulation, editorial decision, reviewer calibration, re-review after revision | ars/academic-paper-reviewer/WORKFLOW.md | | End-to-end research-to-paper pipeline, integrity gate, staged review/revision/finalization workflow | ars/academic-pipeline/WORKFLOW.md | | Experiment planning, code experiment execution plan, human study protocol, statistical interpretation, reproducibility validation | ars/experiment-agent/WORKFLOW.md |

If the request spans multiple workflows, start with ars/academic-pipeline/WORKFLOW.md unless the user clearly asked for a single phase.

Spanish Intent Routing

Use the same intent boundaries as the vendored Spanish trigger phrases:

| Spanish intent | Workflow and mode | |---|---| | revisión de literatura / revisión sistemática / metaanálisis | deep-research: lit-review / systematic-review | | guía mi investigación / ayúdame a razonar | deep-research: socratic | | revisar artículo / revisa este artículo / revisión entre pares | academic-paper-reviewer: full | | enmendar mi artículo / enmienda mi artículo | academic-paper: revision | | recibí comentarios de revisores / ruta de revisión | academic-paper: revision-coach | | escribir resumen / verificar citas / convertir formato | academic-paper: abstract-only / citation-check / format-convert | | artículo de revisión bibliográfica | academic-paper: lit-review | | flujo de trabajo académico / investigación a artículo | academic-pipeline: pipeline |

Keep review and revision intent distinct. Apply topic scoping below to vague paper topics in Spanish too; an explicit research question permits direct planning. These activation phrases do not add supported output-language pairs.

Paper Topic Scoping Override

Apply this override before the general paper/pipeline routing rule and before the Claude-Style Alias Router below. The override applies regardless of whether the user invokes ARS via natural language or via an ars-* alias.

If the user says they want to write a paper, thesis, proposal, article, journal article, or manuscript, but they only provide a broad topic, tentative title, research interest, or "題目/主題/方向" and do not provide a clear, answerable research question, route to ars/deep-research/WORKFLOW.md in socratic mode first. This matches the upstream ARS experience where vague paper-topic requests start with SCR/Socratic narrowing instead of immediate outline or drafting.

Treat these as Socratic triggers even when the wording contains paper-writing intent:

• "I want to write a paper on ..."
• "I have a paper topic/title ..."
• "我想做一篇論文，題目是..."
• "我有一個研究方向/主題，但還不確定問題"
• "幫我想論文題目/收斂研究問題"
• "논문을 쓰고 싶은데 연구 질문이 아직 명확하지 않아"
• "논문 주제/연구 방향은 있지만 무엇을 연구할지 모르겠어"

First response in this path:

1. State that the request is being routed to deep-research socratic mode because the research question is not yet precise.
2. Ask only the material narrowing questions needed now, using socratic_mentor_agent and research_question_agent guidance.
3. Do not produce an outline, draft, literature review, or full pipeline dashboard until the user has converged on at least one candidate RQ.

Route directly to ars/academic-paper/WORKFLOW.md only when the user already has a clear RQ, approved study frame, data/results, literature matrix, draft, or explicitly asks to skip scoping and proceed to outline/drafting. Route to ars/academic-pipeline/WORKFLOW.md only when the user explicitly asks for the full research-to-paper pipeline or says to continue after Socratic scoping.

Claude-Style Alias Router

Codex does not install Claude slash commands, but this package emulates their intent. If the user's request starts with a slash alias (/ars-plan) or a plain alias (ars-plan), treat it as a mode shortcut, strip the alias token from the task text, read the matching ars/commands/ars-*.md prompt recipe, then route to the workflow WORKFLOW.md below.

The model: field in command frontmatter is a Claude routing hint only. Codex does not translate it into an Opus/Sonnet model pin. Apply the Codex model policy below and preserve explicit user or runtime model choices.

| Alias | Read command recipe | Then route to | |---|---|---| | /ars-plan, ars-plan | ars/commands/ars-plan.md | ars/academic-paper/WORKFLOW.md in plan mode | | /ars-outline, ars-outline | ars/commands/ars-outline.md | ars/academic-paper/WORKFLOW.md in outline-only mode | | /ars-abstract, ars-abstract | ars/commands/ars-abstract.md | ars/academic-paper/WORKFLOW.md in abstract-only mode | | /ars-lit-review, ars-lit-review | ars/commands/ars-lit-review.md | ars/academic-paper/WORKFLOW.md in lit-review mode; if the user wants source discovery and synthesis instead, route to ars/deep-research/WORKFLOW.md in lit-review mode | | /ars-3w, ars-3w | ars/commands/ars-3w.md | ars/deep-research/WORKFLOW.md in three-way-scan mode | | /ars-citation-check, ars-citation-check | ars/commands/ars-citation-check.md | ars/academic-paper/WORKFLOW.md in citation-check mode | | /ars-disclosure, ars-disclosure | ars/commands/ars-disclosure.md | ars/academic-paper/WORKFLOW.md in disclosure mode | | /ars-format-convert, ars-format-convert | ars/commands/ars-format-convert.md | ars/academic-paper/WORKFLOW.md in format-convert mode | | /ars-revision-coach, ars-revision-coach | ars/commands/ars-revision-coach.md | ars/academic-paper/WORKFLOW.md in revision-coach mode | | /ars-revision, ars-revision | ars/commands/ars-revision.md | ars/academic-paper/WORKFLOW.md in revision mode | | /ars-rebuttal-audit, ars-rebuttal-audit | ars/commands/ars-rebuttal-audit.md | ars/academic-paper/WORKFLOW.md in rebuttal-audit mode; requires both reviewer comments and an existing response draft | | /ars-reviewer, ars-reviewer | ars/commands/ars-reviewer.md | ars/academic-paper-reviewer/WORKFLOW.md in full mode unless another reviewer mode is explicit | | /ars-mark-read, ars-mark-read | ars/commands/ars-mark-read.md | Record a user-attested read declaration against the active Material Passport; every new mark requires a user-owned read_scope, with locators allowed only for sections scope | | /ars-unmark-read, ars-unmark-read | ars/commands/ars-unmark-read.md | Rescind a prior human-read mark against the active Material Passport | | /ars-cache-invalidate, ars-cache-invalidate | ars/commands/ars-cache-invalidate.md | Invalidate cached verification entries for one citation key | | /ars-full, ars-full | ars/commands/ars-full.md | ars/academic-pipeline/WORKFLOW.md |

If the request body after the alias is a vague topic, tentative title, research direction, or "題目/主題/方向" without a clear research question, defer to the Paper Topic Scoping Override above before routing to the alias's target mode. This applies to ars-plan, ars-outline, ars-abstract, ars-lit-review, and ars-full.

If the Codex client reserves slash-prefixed input before it reaches the model, tell the user to use the plain alias form, for example ars-plan my topic.

Model and Execution Policy

Use GPT-6 Astra (gpt-6-astra) for new Codex research sessions and supported explicit dispatches. Preserve an explicit user/runtime model choice. A skill cannot change an already-running session; report the actual model when known and never present a planned model as observed execution. Read codex/model-runtime-policy.md when configuring models, delegating roles, or running a long research/review task.

Complete the authorized deliverable through its requested stopping point. Resolve routine implementation choices from context and continue independent work while material questions are pending. Reuse existing authorization; a checkpoint display alone is not a new permission request. Keep the actual ARS author-decision, review-criteria, consent, and institution-owned authority gates. If a skill requirement blocks work, identify the exact file and rule and explain which missing decision it needs.

Use task-appropriate reasoning, concise progress updates, and the native tool orchestration surface. Batch independent reads/searches, keep dependent work ordered, and judge completion from source evidence and final artifacts. Increase effort or add a reviewer to resolve a concrete uncertainty; avoid generic self-scoring, repeated unchanged checks, fixed retry rituals, and unrequested extra deliverables. Preserve useful state and the user's latest steering across long runs or context compaction.

Codex Runtime Mapping

The upstream ARS files were written for Claude Code. Apply these mappings when using them in Codex:

| Upstream wording | Codex behavior | |---|---| | Agent Team, agent, dispatch, handoff | Read the referenced agents/*.md as a scoped role contract. Execute inline or delegate independent work using the native runtime, as described below. | | Agent tool, Task tool, subagent | Delegate bounded, independent work when native collaboration is available and it improves quality or time. Continue useful local work while it runs; respect user limits and available slots. Use codex/agents/*.md for role boundaries. Fixed planner topologies remain optional. | | AskUserQuestion | Ask concise clarification questions, or use Codex's structured user-input tool when available in the active mode. | | WebSearch | Use Codex web browsing fo