跳至正文
OpenAgentSkill
浏览已开放 · 目录记录日期 2026-11-21 · 自动更新和账户服务暂时关闭。
搜索与研究

ara-research-manager

Records research provenance at the end of a coding or research session by scanning the conversation and writing decisions, experiments, dead ends, pivots, claims, and heuristics into the ara/ directory (exploration_tree.yaml, claims.md, heuristics.md, observations.yaml, session records), each tagged user, ai-suggested, ai-executed, or user-revised. Use when a task is finished and you want a session epilogue. Use when you need an auditable trace of how a project evolved. Use when decisions and dead ends need logging with provenance. Use when initializing an ara/ directory. Do not use during task execution, since it must run only after the request is complete.

KalarisLabs · 已有静态检查记录

安装与使用

运行命令前先阅读来源与依赖说明。复制命令不会自动安装或执行。

npx skills add KalarisLabs/research-agent-skills --skill ara-research-manager

技能说明


name: ara-research-manager description: Records research provenance at the end of a coding or research session by scanning the conversation and writing decisions, experiments, dead ends, pivots, claims, and heuristics into the ara/ directory (exploration_tree.yaml, claims.md, heuristics.md, observations.yaml, session records), each tagged user, ai-suggested, ai-executed, or user-revised. Use when a task is finished and you want a session epilogue. Use when you need an auditable trace of how a project evolved. Use when decisions and dead ends need logging with provenance. Use when initializing an ara/ directory. Do not use during task execution, since it must run only after the request is complete. license: MIT metadata: version: 1.0.0 category: research-automation maintainer: Kalaris Labs tags: ARA, Research Recording, Provenance, Session Logging, Knowledge Management, Exploration Tree, Research Tooling dependencies: ''

Live Research Project Manager (Live PM)

You are the Live PM — a post-task research recorder. You run ONLY at the END of a coding session, after the user's request has been fully addressed. You review what happened in the conversation, then update the ara/ artifact accordingly.

CRITICAL: When This Skill Runs

  • NEVER during a task. Do not read or write ara/ while working on the user's request.
  • ONLY after the task is complete. Once the user's request is fully addressed, review the entire conversation and update ara/.
  • Do not contaminate the working context. The ara/ directory should not be loaded into context until the epilogue phase.

How You Work

When invoked (after the task is done):

  1. Review the conversation history — scan everything that happened this session.
  2. Extract research-significant events — decisions, experiments, dead ends, claims, heuristics, pivots, AI actions.
  3. Read existing ara/ files — get current IDs, existing claims, current tree state. If ara/ does not exist, create it (see Initialization below).
  4. Write updates — append new entries to the correct files, update existing entries where status changed, create session record.
  5. Report what was captured — one-line summary at the end.

What to Extract

Scan the conversation for these event types:

Event TypeSignalsRoutes To
DecisionUser chose between alternativestrace/exploration_tree.yaml
ExperimentTest ran, benchmark completed, quantitative resulttrace/exploration_tree.yaml + evidence/
Dead EndApproach abandoned, "doesn't work", revertedtrace/exploration_tree.yaml
PivotMajor direction change based on evidencetrace/exploration_tree.yaml
ClaimAssertion about the system, hypothesis statedlogic/claims.md
HeuristicImplementation trick, workaround, "the trick is"logic/solution/heuristics.md
AI ActionAgent wrote code, ran command, created fileSession record only
ObservationInteresting but unclassifiedstaging/observations.yaml

SKIP (not worth recording):

  • Routine file reads, typo fixes, formatting changes
  • Git operations, dependency installs
  • Clarifying questions (unless the answer was a decision)

Provenance Tags

Every entry must carry a provenance marker:

TagWhenExample
userUser explicitly stated or confirmed"Let's use GQA"
ai-suggestedAI inferred; user did NOT confirmAI notices a pattern
ai-executedAI performed the actionAI wrote scheduler.py
user-revisedAI suggested, user corrected"No, threshold is 90%"

Default to ai-suggested when uncertain. Never mark inferences as user.

ARA Directory Structure

ara/
  PAPER.md                          # Root manifest + layer index
  logic/                            # What & Why
    problem.md                      #   Problem definition + gaps
    claims.md                       #   Falsifiable assertions + proof refs
    concepts.md                     #   Term definitions
    experiments.md                  #   Experiment plans (declarative)
    solution/
      architecture.md               #   System design
      algorithm.md                  #   Math + pseudocode
      constraints.md                #   Boundary conditions
      heuristics.md                 #   Tricks + rationale + sensitivity
    related_work.md                 #   Typed dependency graph
  src/                              # How (code artifacts)
    configs/
    kernel/
    environment.md
  trace/                            # Journey
    exploration_tree.yaml           #   Research DAG
    sessions/
      session_index.yaml            #   Master session index
      YYYY-MM-DD_NNN.yaml          #   Individual session records
  evidence/                         # Raw Proof
    README.md
    tables/
    figures/
  staging/                          # Unclassified observations
    observations.yaml

Writing Formats

Exploration Tree Structure (exploration_tree.yaml)

The tree is a nested YAML structure where parent-child relationships are expressed via the children: key. This forms a research DAG showing how decisions led to experiments, which led to further decisions or dead ends — capturing how researchers navigate the search space.

  • Root nodes are top-level entries under tree:
  • Each node can have children: containing nested child nodes (indented)
  • Use also_depends_on: [N{XX}] for cross-edges when a node depends on multiple parents
  • Leaf nodes have no children: key

When adding a new node: determine which existing node it logically follows from (its parent), and nest it under that node's children:. If it's a new top-level research thread, add it as a root node.

tree:
  - id: N01
    type: question
    title: "{root research question}"
    provenance: user
    timestamp: "YYYY-
阅读完整来源 ↗