菜单
Walk the causal graph in AgentDB to explain why two memories are connected, or trace a root cause. Use when the user asks "why did X happen", "what led to Y", or after an incident.
默认使用会先检查来源的 Prompt；你也可以切换为直接命令，或下载本地副本。
决定是否安装前，请先阅读 SKILL.md，以及 SkillsMP 当前展示的配套文件。
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
直接命令不会经过审查 Prompt；运行前请先检查来源。
npx skills add https://github.com/ruvnet/agentdb --skill agentdb-causal-explain命令会保持在同一行。复制前请横向滚动并检查完整内容。
想先保存到本地？可下载 SkillsMP 当前能够提供的文件。
Record a causal relationship between two memories in AgentDB — "X caused Y", "A supersedes B", "patch-foo depends-on patch-bar". Use when the user is documenting cause/effect, dependencies, supersessions, or after-action analysis.
Store memories in tier-aware hierarchical memory — working / short-term / long-term — and recall with tier filters. Use for working-set context that should fade, vs facts that should persist, vs patterns that should be searchable forever.
Initialize an AgentDB Cognitive Container (.rvf file) in the current project. Sets up storage, embedder config, and the agentdb MCP server. Use when the user is starting a new project that needs vector memory, or asks to "set up agentdb" / "init agentdb".
基于 SOC 职业分类
正在显示 SKILL.md
| name | agentdb-causal-explain |
| description | Walk the causal graph in AgentDB to explain why two memories are connected, or trace a root cause. Use when the user asks "why did X happen", "what led to Y", or after an incident. |
Given a target memory (an episode, a failed test, an outgoing change), traverse the causal graph backwards through edges to surface the chain of preceding events that explain it.
agentdb_causal_explain(
targetMemoryId: <id>
maxDepth?: 3
minConfidence?: 0.5
edgeWeights?: 'uplift' | 'confidence' | 'product' // ranking strategy
)
Returns a path or DAG of (node, edge, node) tuples ranked by combined confidence × |uplift|. Each step carries the relation (caused, supersedes, depends-on, etc.) so the explanation reads naturally.
Why did "deploy-2026-05-04 failed migration" happen?
┌─ skill[migrate-add-not-null-column] confidence 0.92
│ ─[supersedes]→ skill[v1: migrate-with-default]
│ ─[caused]→ episode[long-running migration on 50M rows]
│ ─[caused]→ episode[deploy-2026-05-04 failed migration]
│
└─ adr[ADR-046: zero-downtime migration policy] confidence 0.78
─[depends-on]→ skill[migrate-add-not-null-column]
For complex traces, dispatch the agentdb-investigator agent (this plugin) — it walks deeper, cross-references with hierarchical memory, and writes a postmortem-shaped report.
maxDepth > 5 casually — graph fan-out gets exponential and the bandit's confidence weights don't compensate.confidence column. A high-uplift edge with confidence 0.3 is gossip, not evidence.