Automated summary
This skill scans the docs/adr/ directory, extracts metadata and links from each ADR, and stores them in AgentDB as a hierarchical index with a causal dependency graph.
Strengths
- Extracts precise structured fields (ID, title, status, date, tags) from a known ADR template.
- Builds typed causal edges: supersedes, amends, depends-on, and related.
- Verifies graph integrity and reports dangling references, circular supersedes chains, and status mismatches.
- Mirrors each ADR into a semantically searchable memory namespace (adr-patterns).
Limitations
- Requires the claude-flow MCP server and AgentDB to be available; otherwise no write step can complete.
- Assumes a specific ADR format (# ADR-NNN heading, Status/Date/Tags lines, ## Links section), so off-template files will parse poorly or partially.
- Index-only: it neither authors nor edits ADRs, and it describes a full rebuild rather than incremental updates.
Use it after importing ADRs from another project, when the AgentDB graph is out of sync, or to bootstrap ADR tracking on a codebase that already has ADR files.
Avoid it if your ADRs don't follow the expected template, if claude-flow/AgentDB isn't installed, or if you just want to read a single ADR.
Security analysis
SafeThe skill only reads local ADR markdown files and writes structured metadata to AgentDB and memory tools. It does not execute shell commands, network calls, destructive operations, or exfiltration. Bash is declared but not used in the instructions. No obfuscation or unsafe patterns present.
No concerns found
How this analysis is madeExamples
Rebuild the ADR index from docs/adr/ into AgentDB and tell me about any dangling references or circular supersedes chains.I just imported a batch of ADRs from another repo into docs/adr/ — index them all in AgentDB with their dependency graph.Bootstrap ADR tracking for this repo: scan docs/adr/, store every ADR in AgentDB and the adr-patterns memory namespace, then summarize counts by status.name: adr-index description: Build or rebuild the ADR index and dependency graph in AgentDB argument-hint: "" allowed-tools: mcp__claude-flow__agentdb_hierarchical-store mcp__claude-flow__agentdb_hierarchical-query mcp__claude-flow__agentdb_causal-edge mcp__claude-flow__agentdb_causal-query mcp__claude-flow__memory_store mcp__claude-flow__memory_search Bash Read Grep Glob
ADR Index
Build or rebuild the full ADR index and dependency graph in AgentDB from the docs/adr/ directory.
When to use
After importing ADRs from another project, when the AgentDB graph is out of sync, or when bootstrapping ADR tracking on an existing codebase that already has ADR files.
Steps
-
Scan directory --
Globfordocs/adr/ADR-*.mdto find all ADR files. If no files found, report that no ADRs exist yet. -
Parse each ADR --
Readeach file and extract:- ID: from the filename (e.g.,
ADR-042fromADR-042-use-postgres.md) - Title: from the
# ADR-NNN: <Title>heading - Status: from the
**Status**:line - Date: from the
**Date**:line - Tags: from the
**Tags**:line - Links: from the
## Linkssection (supersedes, amended-by, related)
- ID: from the filename (e.g.,
-
Store in AgentDB -- For each ADR, call
mcp__claude-flow__agentdb_hierarchical-storewith:- path:
adr/<adr-id> - value:
{ "id": "<id>", "title": "<title>", "status": "<status>", "date": "<date>", "tags": "<tags>", "file": "<filepath>" }
- path:
-
Build causal edges -- For each ADR with links:
- "Supersedes ADR-XXX" ->
mcp__claude-flow__agentdb_causal-edgewithfrom: ADR-XXX,to: <current>,relation: supersedes - "Amended by ADR-YYY" ->
mcp__claude-flow__agentdb_causal-edgewithfrom: <current>,to: ADR-YYY,relation: amends - "Related: ADR-ZZZ" ->
mcp__claude-flow__agentdb_causal-edgewithfrom: <current>,to: ADR-ZZZ,relation: related - "Depends on ADR-WWW" ->
mcp__claude-flow__agentdb_causal-edgewithfrom: <current>,to: ADR-WWW,relation: depends-on
- "Supersedes ADR-XXX" ->
-
Store in memory -- For each ADR, call
mcp__claude-flow__memory_storewith:- namespace:
adr-patterns - key:
<adr-id> - value:
<title> — <first paragraph of Context section>This enables semantic search across ADRs.
- namespace:
-
Verify graph -- Call
mcp__claude-flow__agentdb_causal-queryto retrieve all edges and verify:- No dangling references (edges pointing to non-existent ADRs)
- No circular supersedes chains
- All superseded ADRs have status "superseded"
-
Report -- Output a summary:
## ADR Index Summary Total ADRs: N - Proposed: X - Accepted: Y - Deprecated: Z - Superseded: W Relationships: M edges - Supersedes: A - Amends: B - Depends-on: C - Related: D Issues found: (list any dangling refs or status mismatches)
From the file to a first result
The download contains exactly the content displayed on this page. This copy may differ from the latest version in the source repository.
View the source and supporting filesThis download contains SKILL.md only. Any scripts, references, templates and dependencies are not included. Get the required files from the source, preserving their directory structure, before continuing.
1. Download the file
Download SKILL.mdFrom the root of a test project, save the file as .skill-downloads/adr-index-ms47vp3j/SKILL.md, or use the command below. This folder is for inspecting the skill before installation.
Command for macOS/Linux or WSL: requires a POSIX shell and curl. On Windows without WSL, use the download button and create the folder manually.
mkdir -p '.skill-downloads/adr-index-ms47vp3j' && curl --fail --show-error --location 'https://skills-guides.com/api/skills/adr-index-ms47vp3j/download' --output '.skill-downloads/adr-index-ms47vp3j/SKILL.md.part' && mv '.skill-downloads/adr-index-ms47vp3j/SKILL.md.part' '.skill-downloads/adr-index-ms47vp3j/SKILL.md'2. Check prerequisites
Read SKILL.md before using it. If it references scripts or external services, inspect them and prepare the required access in your test environment.
Tools declared by the author (check availability in your agent): mcp__claude-flow__agentdb_hierarchical-store mcp__claude-flow__agentdb_hierarchical-query mcp__claude-flow__agentdb_causal-edge mcp__claude-flow__agentdb_causal-query mcp__claude-flow__memory_store mcp__claude-flow__memory_search Bash Read Grep Glob
No recognized prerequisites section in this file. This does not mean it is self-contained: libraries, tools and access requirements may be mentioned elsewhere in the content or source repository.
The platforms on this page are catalog indications. The paths below follow tool documentation; they do not prove this skill has been run in those tools. No minimum tool version is confirmed for this listing.
3. Load the skill
After inspection, copy the complete folder into your project using one of the commands below, then open a new tool session. The command stops if a folder with the same name already exists: compare the files before replacing it.
Claude Code
test -f '.skill-downloads/adr-index-ms47vp3j/SKILL.md' && test -s '.skill-downloads/adr-index-ms47vp3j/SKILL.md' && mkdir -p '.claude/skills' && test ! -e '.claude/skills/adr-index' && cp -R '.skill-downloads/adr-index-ms47vp3j' '.claude/skills/adr-index'OpenSkills
OpenSkills must already be installed. The local install/read procedure is checked with OpenSkills 1.5.0, which requires Node.js ≥ 20.6.0. Catalog slugs are not resolved automatically.
Official OpenSkills installationopenskills install './.skill-downloads/adr-index-ms47vp3j'openskills read 'adr-index-ms47vp3j'Reading should display the installed file content and its base directory. It does not run the skill or install its dependencies.
For an agent that reads AGENTS.md, then sync the index. This command changes AGENTS.md: review the diff before using it.
openskills syncManual method or another tool: attach SKILL.md to a conversation, or open it in an agent that can read files. Include any required supporting resources. No universal folder is recognized by every tool.
4. Try a first task
Use a short, synthetic input: an API endpoint, a small document or an interface brief. In a new conversation, attach the file or give the agent its path, then adapt this request:
Read .skill-downloads/adr-index-ms47vp3j/SKILL.md and apply its instructions to this example: [describe a test input]. Identify any missing files, dependencies or access. Produce the result requested by the skill without inventing data or running unreviewed scripts.Expected result: output matching the skill instructions, or a precise list of missing prerequisites. A read confirmation alone does not validate a first use. If an external resource is unavailable, that path remains untested.
Supabase Docs Authoring
Documentation
Write, edit, and review Supabase documentation content including guides, tutorials, reference docs, and partials. Follow style guides and MDX/TOML validation rules.
Create Architecture Decision Record
Documentation
Create a new Architecture Decision Record with sequential numbering, register it in the AgentDB graph, and link related ADRs.
Plan update with deep research
Documentation
Updates a plan document by launching parallel subagents to analyze a topic across all compiler passes, then consolidates findings into the plan doc.