ara-research-manager

Records research decisions, experiments, and claims into a provenance-tagged ara/ directory after sessions.

13.0k|930|Updated Nov 3, 2025
One-click install
npx skills add https://github.com/Orchestra-Research/AI-research-SKILLs --skill ara-research-manager-orchestra-research
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: ara-research-manager
Source: https://github.com/Orchestra-Research/AI-research-SKILLs/tree/main/22-agent-native-research-artifact/research-manager
Command: npx skills add https://github.com/Orchestra-Research/AI-research-SKILLs --skill ara-research-manager-orchestra-research

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Research and coding sessions generate decisions, experiments, dead ends, and hypotheses that are quickly forgotten, leaving no auditable record of how a project actually evolved or which ideas came from the user versus the AI. ## Core Features & Use Cases - Post-Session Epilogue Recording: Scans conversation history only after a task completes, extracting decisions, experiments, dead ends, pivots, claims, and heuristics without contaminating the working context. - Provenance Tagging: Labels every entry as user, ai-suggested, ai-executed, or user-revised so reviewers can trace each assertion to its source. - Structured ARA Artifact: Maintains an exploration tree YAML, claims log, heuristics log, session records, evidence folders, and a staging area with automatic maturity promotion. - Use Case: After a long ML experimentation session where you tried FP16 training (failed), switched to GQA (worked), and formed a hypothesis about gradient instability, invoke this Skill to capture all of it into ara/ with correct provenance before closing the session. ## Quick Start Ask the AI to run the research manager epilogue to capture this session's decisions, experiments, and claims into the ara directory.

Frequently Asked Questions about ara-research-manager

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I record research decisions from an AI coding session?▼

Invoke this Skill as a post-task epilogue after the session's work is complete. It scans the conversation history, classifies events like decisions, experiments, and dead ends, and appends them to the ara/ directory with provenance tags.

What is the ara directory structure for research tracking?▼

The ara/ directory contains logic/ for claims and heuristics, trace/ for the exploration tree and session records, evidence/ for tables and figures, and staging/ for unclassified observations. It is auto-initialized on first use if missing.

How does provenance tagging distinguish user ideas from AI suggestions?▼

Each entry carries a tag: user for explicitly stated input, ai-suggested for unconfirmed AI inferences, ai-executed for AI actions, and user-revised for corrected suggestions. AI suggestions are never auto-upgraded without explicit user confirmation.

Can this Skill run during an active coding task?▼

No. The Skill explicitly runs only as a session epilogue after the user's request is fully addressed. Running during execution would contaminate the working context by loading ara/ files prematurely.

What happens to unclassified observations in the staging area?▼

Observations accumulate in staging/observations.yaml until a maturity tracker promotes them: three or more on the same topic become claims or heuristics, evidence-backed ones move to evidence/, and stale entries are flagged.