REA
Reverse engineer anything from your terminal or agent with one CLI and MCP server.
Codex-native Academic Research Skills suite for human-in-the-loop academic research workflows
作者の方は、このコードを README に貼れます。バッジはこのページにリンクします。
[](https://mcp.popnx.com/en/skills/imbad0202-academic-research-skills-codex)同じ作業で AI をサービスにつなぐ MCP
Reverse engineer anything from your terminal or agent with one CLI and MCP server.
Codebase intelligence for TypeScript and JavaScript, exposed as structured MCP analysis tools.
MCP server for terminal commands, file operations, and process management
同じ種類の作業。Skill 一覧と同じ並び
| これ academic-research-skills-codex | rea | andrej-karpathy-skills | graphify | MoneyPrinterTurbo | |
|---|---|---|---|---|---|
| 作者 | Imbad0202 | morluto | multica-ai | Graphify-Labs | harry0703 |
| Skill 数 | 1 | 1 | 1 | 1 | 1 |
| GitHub スター | 14,769 | 468,733 | 234,332 | 150,287 | 144,566 |
| 最終コード更新 | 2026年11月6日 | 2026年11月19日 | 2026年4月20日 | 2026年11月18日 | 2026年11月18日 |
| ライセンス | – | MIT | – | Apache-2.0 | MIT |
Imbad0202 による 1 個の Skill(指示セット)。AI が読んでそのとおりに作業します · MCP server ではありません
MCP = 手
AI を外部のサービスやデータにつなぎます(例:Notion を読む、請求書を作る)。プログラムやサーバーが動いている必要があります。
Skill = 手順書
作業のやり方を AI に教えるテキストファイル。どのサービスにもつながりません。
重なる部分もあります。ツールを呼ぶスクリプト付きの Skill や、知識だけを渡す MCP もあります。やりたい作業から選んでください。
Claude CodeClaude (เว็บ/แอป)Codex
提供元の README と repo のフォルダから判断
GitHub account Imbad0202 (person), 3 years old
★ 14,769 stars · code last changed 2026年11月6日
549 scripts that can run on a computer: ars/hooks/run_guard.sh, ars/scripts/adapters/folder_scan.py, ars/scripts/adapters/obsidian.py, ars/scripts/adapters/zotero.py and 545 more
Could not check every script (some are too large); read them first
No hooks or writes to machine settings found
Checked automatically from the repo files at commit 82725ac (read only, nothing was run). Not a safety guarantee: read it and decide for yourself
まず:どの AI を使っていますか
使っているアプリを選ぶと、そのアプリでのインストール方法だけが表示されます
This skill has no license, so we do not hand out a ZIP from our site. Download it from GitHub and arrange the folder yourself, or use "Let the AI install it" above, which is easier
Download from GitHub (whole repo) ↗
Unzip it, then zip only the skills/academic-research-suite folder again. The ZIP must have a academic-research-suite folder with SKILL.md at the top level, no loose files
+Create skillUpload a skillpick academic-research-suite.zip
SettingsCapabilitiesCode execution and file creation
Turn on Code execution and file creation first (newer menus: Create and edit files) · personal plans: Settings → Capabilities · Team/Enterprise: an admin turns it on under Organization settings → Plugins & skills · every plan, including Free
Upload once; it works in claude.ai and Claude Desktop, and in recent Claude Code signed in with a Claude account (not with an API key)
Cowork and cloud sessions use the skills turned on in your claude.ai account, not ~/.claude/skills on your computer (Claude Desktop scheduled tasks run locally and still load it)
Checked against official docs 2026年11月12日 · Source: support.claude.com, support.claude.com, code.claude.com
この文をコピーして Claude Code のチャットに貼り付けます
For one project, paste it into a chat that is open in that project’s folder · The AI always shows you the path before installing
The AI tells you what it will do first and asks your permission at every step
Claude Code を開き直し、/academic-research-suite と入力するか関連する作業を頼むと Claude が自動で使います
Checked against official docs 2026年11月12日 · Source: code.claude.com
Skill は AI が従う指示です。入れる前にファイルを読み、信頼できる提供元のものだけを入れてください。
Mac:Command+スペースで Terminal と入力 · Windows:下のコマンドは PowerShell では動きません。上の「AI にインストールしてもらう」を使ってください
repo を一時フォルダにダウンロードし、SKILL.md のあるフォルダだけをコピーします
git clone --depth 1 https://github.com/imbad0202/academic-research-skills-codex.git /tmp/popnx-skill-imbad0202-academic-research-skills-codex-82725ac && mkdir -p ~/.claude/skills && cp -R '/tmp/popnx-skill-imbad0202-academic-research-skills-codex-82725ac/skills/academic-research-suite' ~/.claude/skills/academic-research-suiteChatGPT デスクトップアプリには Codex が組み込まれていて、Codex は ~/.agents/skills フォルダから Skill を読み込みます
ChatGPT デスクトップアプリで Codex を開き、この文をチャットに貼り付けます
The AI always shows you the path before installing
The AI tells you what it will do first and asks your permission at every step
academic-research-suite フォルダを ~/.agents/skills/academic-research-suite に置きます
~ はホームフォルダ($HOME)です
Skill は AI が従う指示です。入れる前にファイルを読み、信頼できる提供元のものだけを入れてください。
Mac:Command+スペースで Terminal と入力 · Windows:下のコマンドは PowerShell では動きません。上の「AI にインストールしてもらう」を使ってください
repo を一時フォルダにダウンロードし、SKILL.md のあるフォルダだけをコピーします
git clone --depth 1 https://github.com/imbad0202/academic-research-skills-codex.git /tmp/popnx-skill-imbad0202-academic-research-skills-codex-82725ac && mkdir -p ~/.agents/skills && cp -R '/tmp/popnx-skill-imbad0202-academic-research-skills-codex-82725ac/skills/academic-research-suite' ~/.agents/skills/academic-research-suiteChecked against official docs 2026年11月15日 · Source: learn.chatgpt.com
自分でインストールした Skill は使えません。ディレクトリのプラグインに含まれる Skill だけが使えます
この Skill を ChatGPT で使うには、上の方法で ChatGPT デスクトップアプリを使ってください
Checked against official docs 2026年11月15日 · Source: learn.chatgpt.com
この文をコピーして Codex のチャットに貼り付けます · ChatGPT デスクトップアプリ内の Codex、Codex CLI、IDE 拡張機能で使えます
For one project, paste it into a chat that is open in that project’s folder · The AI always shows you the path before installing
The AI tells you what it will do first and asks your permission at every step
Codex は新しくインストールした Skill を自動で見つけます。表示されない場合は Codex を再起動してください · 使い方:ChatGPT では @ を入力して Skill を選びます · Codex CLI や IDE 拡張機能では /skills を実行するか、$ に続けて Skill 名を入力します
Checked against official docs 2026年11月15日 · Source: learn.chatgpt.com
Skill は AI が従う指示です。入れる前にファイルを読み、信頼できる提供元のものだけを入れてください。
Mac:Command+スペースで Terminal と入力 · Windows:下のコマンドは PowerShell では動きません。上の「AI にインストールしてもらう」を使ってください
repo を一時フォルダにダウンロードし、SKILL.md のあるフォルダだけをコピーします
git clone --depth 1 https://github.com/imbad0202/academic-research-skills-codex.git /tmp/popnx-skill-imbad0202-academic-research-skills-codex-82725ac && mkdir -p ~/.agents/skills && cp -R '/tmp/popnx-skill-imbad0202-academic-research-skills-codex-82725ac/skills/academic-research-suite' ~/.agents/skills/academic-research-suiteこの文をコピーして Cursor のチャットに貼り付けます
For one project, paste it into a chat that is open in that project’s folder · The AI always shows you the path before installing
The AI tells you what it will do first and asks your permission at every step
Cursor の Agent チャットで / を入力し academic-research-suite を選ぶ
Checked against official docs 2026年11月12日 · Source: cursor.com
Skill は AI が従う指示です。入れる前にファイルを読み、信頼できる提供元のものだけを入れてください。
Mac:Command+スペースで Terminal と入力 · Windows:下のコマンドは PowerShell では動きません。上の「AI にインストールしてもらう」を使ってください
repo を一時フォルダにダウンロードし、SKILL.md のあるフォルダだけをコピーします
git clone --depth 1 https://github.com/imbad0202/academic-research-skills-codex.git /tmp/popnx-skill-imbad0202-academic-research-skills-codex-82725ac && mkdir -p ~/.cursor/skills && cp -R '/tmp/popnx-skill-imbad0202-academic-research-skills-codex-82725ac/skills/academic-research-suite' ~/.cursor/skills/academic-research-suiteSkill を読めるほかのアプリ向けです。この文には Claude Code、Codex、Cursor のパスが入っていて、AI が使っているアプリに合わせて選びます · Copy this sentence into the app’s chat
For one project, paste it into a chat that is open in that project’s folder · The AI always shows you the path before installing
The AI tells you what it will do first and asks your permission at every step
Checked against official docs 2026年11月12日 · Source: code.claude.com, learn.chatgpt.com, cursor.com
Gemini CLI や GitHub Copilot など Agent Skills 対応の他のアプリはフォルダが違います。そのアプリのガイドを見て、SKILL.md のあるフォルダをコピーしてください。
2026年11月11日 に Claude Code、Codex、Cursor の公式ガイドで skill フォルダを確認
✓ コマンド確認済み 2026年11月16日
以下は提供元の repo の文章で、PopNx MCP の指示ではありません
最初の 8,000 文字を表示 · GitHub で全文を開く
---
name: academic-research-suite
description: >
ARS-Codex research, writing, manuscript review, study screening, and experiments.
Use for deep research, literature or systematic reviews, meta-analysis, research
questions, drafts, revisions, roadmaps, abstracts, citations,
integrity checks, peer review, research-to-paper. Screen records: sr-screener. Citation triggers:
check citations, look over the refs, 檢查引用, 檢查參考文獻, 인용 확인, 인용 형식 검사. 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.
Prompts, references, templates, and contracts live under ars/.
metadata:
version: "3.24.2"
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.24.2`. 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
Apply the routing core before choosing a workflow or dispatching an agent. The
block is copied from `ars/shared/references/routing_core.md`. Its upstream
`shared/` references resolve under this package's `ars/` directory. Apply it to
new requests; after compaction or resume, continue the settled workflow and
perform the run-ledger handoff check instead of routing the active run again.
<!-- routing-core:begin -->
**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.
Otherwise, classify the user's input:
1. **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"):
→ Route directly; no clarification, no orchestrator detour.
→ 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.
2. **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):
→ **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.
→ 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.)
3. **Ambiguous intent, no materials** — user provides no artifacts and no clear request:
→ Clarify per `shared/references/intent_clarification_protocol.md`.
**Screening boundary (sr-screener):** a request to screen records the user already has (database exports, pasted abstracts, full-text PDFs) against a review's eligibility criteria, or to build a screening protocol, pilot the screening, adjudicate screening conflicts, audit exclusions, or report the selection counts, routes to `sr-screener`. A request to write a literature review, or to run a systematic review, meta-analysis, or PRISMA report, does not route to `sr-screener`. Screening starts only when the user asks for it: `deep-research` `systematic-review` mode may mention `sr-screener`, but never hands over to it automatically.
**Anti-pattern (caused #133):** Receiving ambiguous cross-phase materials and silently auto-routing to a single-phase agent based on which phase the materials "look closest to." This bypasses orchestrator-level reconciliation and lets the subagent inherit the full ambiguity without independent oversight.
<!-- routing-core:end -->
Choose the workflow by the settled 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` |
| Explicit study selection: screening protocol, eligibility decisions on supplied records, pilot, conflicts, exclusion audit, screening counts | `ars/sr-screener/WORKFLOW.md` |
| Experiment planning, code experiment execution plan, human study protocol, statistical interpretation, reproducibility validation | `ars/experiment-agent/WORKFLOW.md` |
An explicit end-to-end request selects `academic-pipeline`. Materials spanning
multiple phases without an explicit workflow require clarification using the
core above; they do not by themselves select a pipeline.
### Study Screening Boundary
Use `ars/sr-screener/WORKFLOW.md` only for an explicit screening request. Its
modes are `protocol`, `quick`, `pilot`, `ta-screen`, `ft-screen`, `adjudicate`,
`audit`, and `report`. A whole systematic review, meta-analysis, literature
review, PRISMA report, or the presence of database exports does not activate
screening. `deep-research` may offer screening; `academic-pipeline` never
inserts it as an automatic stage. Accept it質問、コツの共有、使えないことの報告ができます。「役に立った」の多い順です。