Skip to content
Projects

ARA-Labs/Agent-Native-Research-Artifact

View on GitHub

ARA-Labs/Agent-Native-Research-Artifact has 711 GitHub stars and 55 forks. GitHot measured 0 stars in 24 hours. Last checked 2026-11-15 19:23 UTC. Last push 2026-10-11.

How these counts are measured

Measured star growth

in 24h
0
in 7 days
Collecting history
in 15 days
Collecting history
in 1 month
Collecting history

Net star changes over overlapping periods, not daily totals. Missing measurements are left blank. Stars measure attention, not software quality.

About

Research Artifact Protocol for Rigorous and Trustworthy AI Scientists

Developer Tools

README.md

Original

🔬 Agent-Native Research Lab

The Essential Toolkit to Supercharge Your Autoresearch

Start here

License: MIT Agent Skills arXiv Poster Demo

Autoresearch is blindingly fast, but fundamentally unobservable. When AI agents run experiments, they leave behind a graveyard of overwritten code, scattered logs, and undocumented dead ends. ARA is the essential toolkit that forces your AI scientists to work in a structured, verifiable, and traceable format—so you can actually trust the science they produce without reverse-engineering thousands of lines of terminal output.

ARA Skills Demo


⚡ Start here — the only setup step

Paste this one line into your coding agent, from your project root:

Read https://raw.githubusercontent.com/ARA-Labs/Agent-Native-Research-Artifact/main/wire-ara.md and follow its instructions.

The agent fetches the full wiring prompt, installs the seven skills, and writes a task-routing map into its own context file (CLAUDE.md, AGENTS.md, .cursorrules, or GEMINI.md) — so every future session knows which skill handles which situation to assist your ai-native research. The prompt lives at wire-ara.md.

Using ARA as your conference submission format? Follow the short guide: Using ARA as a Conference Submission Format — set up, record as you research, publish as one link.


Core Design Principles

Instead of leading with layers, the bundle maps directly to how it solves the bottleneck through three core design principles:

The three core design principles: Guardrailing & Verification, Crystallizing Insights, and Total Observability

🛡️ Guardrailing & Verification — every claim wired to ground-truth execution

AI agents require precise constraint boundaries to prevent hallucinated conclusions. The system acts as a strict epistemic anchor, automatically applying formal verification principles to ensure every scientific claim is directly wired to ground-truth execution and falsifiable results.

🧠 Crystallizing Insights — messy trajectories become structured knowledge

Research is rarely a straight line; it is a messy graph of pivots and dead ends. The system forces AI scientists to systematically document their trajectory, crystallizing fleeting, unstructured logs into highly structured, reliable research knowledge that builds compounding value over time.

👁️ Total Observability — high-level oversight without reading terminal output

Supervising AI scientists shouldn't require reading endless terminal outputs. The system translates complex agent behaviors and exploration graphs into a clean, minimalist interface. It lets human researchers maintain high-level oversight, seamlessly stepping in to course-correct or guide the AI's behavior with zero friction.

🛠️ The Toolkit: Seven Core Skills

To operationalize these design principles, ARA provides a suite of seven specialized agent skills. The one-liner above installs all seven automatically; to install manually or pick individual skills:

npx @ara-commons/ara-skills

Auto-detects Claude Code, Cursor, Gemini CLI, OpenCode, Codex, and Hermes, then prompts for skills, agents, and install scope (global vs. local). Full CLI reference: packages/ara-skills/.

Then reach for a skill by what you need:

If you want to… Skill Invoke
Capture research faithfully as you work — decisions, ablations, dead ends, configs research-manager /research-manager (or wire it to run automatically)
Compile an existing paper, repo, or notes into a structured ARA compiler /compiler <path>
Verify an artifact's epistemic rigor before you trust, publish, or submit it rigor-reviewer /rigor-reviewer <dir>
Observe the full research trajectory in an interactive process map — a portable narrated HTML export, or a live local viewer with validation/linting via the official ara CLI research-visualizer /research-visualizer <ara-dir> (add --serve or --check for the live/lint path)
Ask an ARA anything — grounded, falsifiable answers to "what should I try next / why did this work / what if I change X" (demo) research-foresight /research-foresight <ara-dir> "<question>"
Share a file or folder with someone else's agent — one URL they paste, no repo, no zip context-drop /context-drop <path>
Steer any open-ended investigation the way a fuzzer steers inputs — predict before every action, track untried leads and unexplained results, alarm on going-in-circles, gate every conclusion behind a self-refutation attempt (repo) research-fuzzer /research-fuzzer (fire at investigation start, after each batch of results, before any conclusion)

See each skill's SKILL.md for the full specification: research-manager · compiler · rigor-reviewer · research-visualizer · research-foresight · context-drop · research-fuzzer


Under the hood — the artifact anatomy

The four pillars all read and write one structure. An ARA organizes research into four interlocking layers:

example_artifact/
  PAPER.md                    # Root manifest + layer index (~200 tokens)
  logic/                      # Cognitive layer — What & Why
    claims.md                 #   Falsifiable assertions with proof refs
    experiments.md            #   Declarative experiment plans
    solution/
      architecture.md         #   System design + component graph
      algorithm.md            #   Math + pseudocode
      constraints.md          #   Boundary conditions
    related_work.md           #   Typed dependency graph
  src/                        # Physical layer — How
    configs/                  #   Hyperparameters with rationale
    environment.md            #   Dependencies, hardware, seeds
  trace/                      # Exploration graph — Journey
    exploration_tree.yaml     #   Research DAG with typed nodes + dead ends
  evidence/                   # Raw proof
    tables/                   #   Exact result tables
    figures/                  #   Extracted data points

Cross-layer bindings

Cross-layer forensic bindings thread claims in /logic to code in /src and evidence in /evidence. Dead-end nodes (×) in the exploration graph preserve failure modes so no agent re-walks them.

Key structural principles

  • Progressive disclosure — PAPER.md (~200 tokens) tells an agent whether the artifact is relevant; deeper files load on demand.
  • Cross-layer binding — claims reference experiments, experiments reference evidence, heuristics reference code. Everything resolves.
  • Dead ends preserved — failed approaches and rejected alternatives are first-class nodes in the exploration graph, not noise to drop.
  • Provenance tracking — every entry is tagged (user, ai-suggested, ai-executed, user-revised), distinguishing human-confirmed facts from AI inferences.

Why it works

The supervision gap is not hand-waving — it shows up as measurable cost. Across benchmarks, an ARA beats a strong PDF + repo baseline on the three things agents do with research (understand, reproduce, extend), most dramatically on recovering the failure knowledge a narrative drops. For the full argument — the two structural taxes, the benchmark results, and the case for agent-native research — read the writeup:

→ The Last Human-Written Paper: Agent-Native Research Artifacts

This paper practices what it proposes — its own ARA lives at examples/the-ara-of-ara.


Compatibility

These skills follow the Agent Skills open standard and work with:


Citation

If you use ARA in your research, please cite:

@misc{liu2026humanwrittenpaperagentnativeresearch,
      title={The Last Human-Written Paper: Agent-Native Research Artifacts},
      author={Jiachen Liu and Jiaxin Pei and Jintao Huang and Chenglei Si and Ao Qu and Xiangru Tang and Runyu Lu and Lichang Chen and Xiaoyan Bai and Haizhong Zheng and Carl Chen and Zhiyang Chen and Haojie Ye and Yujuan Fu and Zexue He and Zijian Jin and Zhenyu Zhang and Shangquan Sun and Maestro Harmon and John Dianzhuo Wang and Jianqiao Zeng and Jiachen Sun and Mingyuan Wu and Baoyu Zhou and Chenyu You and Shijian Lu and Yiming Qiu and Fan Lai and Yuan Yuan and Yao Li and Junyuan Hong and Ruihao Zhu and Beidi Chen and Alex Pentland and Ang Chen and Mosharaf Chowdhury and Zechen Zhang},
      year={2026},
      eprint={2604.24658},
      archivePrefix={arXiv},
      primaryClass={cs.LG},
      url={https://arxiv.org/abs/2604.24658},
}

Contributing

See CONTRIBUTING.md for how to add or improve skills.

License

MIT