ln-022-researchgraph
Indexes and queries project research graphs backed by hex-research MCP. Use for hypotheses, goals, benchmark runs, evidence depth, derived goal metrics, lineage, generated research maps, and graph audits.
What this skill does
> **Paths:** File paths are relative to this skill directory.
# Research Graph
**Type:** Standalone Utility
**Category:** 0XX Dev Environment
Indexes and queries canonical project research files through `hex-research-mcp`: hypotheses, goals, tasks, sources, source library entries, benchmark run manifests, evidence links, derived goal metrics, lineage, generated research maps, and audit gaps.
## Mandatory Read
**MANDATORY READ:** Load `references/researchgraph_mcp_usage.md`
## Inputs
| Input | Required | Source | Description |
|-------|----------|--------|-------------|
| `project_path` | yes | args or CWD | Project root containing research graph files |
| `command` | no | args | Specific action: `audit`, `inspect H##`, `goal G##`, `runs`, `evidence`, `lineage`, `progress`, `proposed`, `canvas` |
## When to Use
Use this skill when the project has any of:
- `docs/hypotheses/*.md`
- `docs/goals/*.md`
- `benchmark/runs/*/manifest.yaml`
Use it when the user asks about research status, live or pending hypotheses, goal readiness, benchmark evidence, source quality, evidence depth, proposal readiness, implementation gaps, drift, field-level changes, or a visual/generated research map.
Do not use this skill for code symbol ownership, call graphs, references, or edit blast radius. Use `ln-021-codegraph` or host `hex-graph` policy for semantic code questions.
## MCP Availability
Use `hex-research` when available. If unavailable, manually read the split research files with `Glob/Grep/Read`, answer from direct file evidence, and mark confidence as degraded.
Treat `STALE` as actionable graph debt or missing project metadata, not as a tool failure. Treat `INVALID` from `verify_index` as diagnostic unless a write/index operation fails.
## Workflow
### Phase 1: Detect Graph Layout
Check for the canonical layout:
- `docs/hypotheses/*.md`
- `docs/goals/*.md`
- `benchmark/runs/*/manifest.yaml`
If none exist, stop and report that the project does not expose a research graph yet. Do not invent hypotheses or goals.
### Phase 2: Verify or Index
Start read-only:
```
verify_index({ path: "{project_path}" })
```
Rebuild only when the index is missing, stale, explicitly requested, or the task requires current graph state:
```
index_hypotheses({ path: "{project_path}" })
```
The local index is stored under `.hex-skills/researchgraph/` in the target project.
### Phase 3: Route Intent
| User intent | Tool |
|-------------|------|
| live, pending, rejected, mixed, not-started hypotheses | `find_hypotheses` |
| inspect `H##` | `inspect_hypothesis` |
| inspect `G##` or goal status | `inspect_goal` |
| evidence, sources, benchmark proof | `find_evidence` |
| targeted or comprehensive benchmark runs | `find_runs` |
| parent/child hypothesis chain | `trace_lineage` |
| graph hubs, disconnected nodes, shape | `analyze_topology` |
| missing goals, sources, task gaps, drift | `audit_orphans` |
| goal tree | `trace_goal_tree` |
| goal readiness, derived metrics, and metric coverage | `inspect_goal`, `audit_goal_alignment` |
| source quality or evidence depth | `inspect_hypothesis`, `find_evidence`, `analyze_proposed` |
| changed research files and field-level deltas in current diff | `analyze_progress` |
| readiness of proposed next hypotheses | `analyze_proposed` |
| JSON Canvas export | `export_canvas` |
| generated `docs/research-map.md` export | `export_research_map` |
### Phase 4: Present Results
Report:
1. tool status (`OK`, `STALE`, `INVALID`, `ERROR`)
2. key hypotheses/goals/runs with IDs
3. actionable graph debt separately from tool failures
4. follow-up tool calls when the graph points to a narrower next question
For `export_canvas` and `export_research_map`, run dry-run first. Write only after dry-run output is useful and the user requested the file. Treat split files as canonical; generated `research-map.md` is not a second manual source of truth.
## Manual Fallback
When MCP is unavailable:
1. Read `docs/goals/*.md` and `docs/hypotheses/*.md` frontmatter first.
2. Read `benchmark/runs/*/manifest.yaml` only after narrowing by H/G IDs or status.
3. Prefer exact IDs (`H04`, `G1`) over broad scans.
4. State that lineage, topology, and drift findings are manual approximations.
## Definition of Done
- [ ] Graph layout detected or absence reported
- [ ] Index verified or rebuilt when needed
- [ ] User intent routed to the smallest relevant tool
- [ ] `STALE` / graph debt separated from MCP/tool failure
- [ ] Manual fallback confidence stated when MCP was unavailable
- [ ] Canvas writes use dry-run before write
---
**Version:** 0.1.0
**Last Updated:** 2026-05-08
Related in AI Agents
skill-development
IncludedComprehensive meta-skill for creating, managing, validating, auditing, and distributing Claude Code skills and slash commands (unified in v2.1.3+). Provides skill templates, creation workflows, validation patterns, audit checklists, naming conventions, YAML frontmatter guidance, progressive disclosure examples, and best practices lookup. Use when creating new skills, validating existing skills, auditing skill quality, understanding skill architecture, needing skill templates, learning about YAML frontmatter requirements, progressive disclosure patterns, tool restrictions (allowed-tools), skill composition, skill naming conventions, troubleshooting skill activation issues, creating custom slash commands, configuring command frontmatter, using command arguments ($ARGUMENTS, $1, $2), bash execution in commands, file references in commands, command namespacing, plugin commands, MCP slash commands, Skill tool configuration, or deciding between skills vs slash commands. Delegates to docs-management skill for official documentation.
reprompter
IncludedTransform messy prompts into well-structured, effective prompts — single or multi-agent. Use when: "reprompt", "reprompt this", "clean up this prompt", "structure my prompt", rough text needing XML tags and best practices, "reprompter teams", "repromptception", "run with quality", "smart run", "smart agents", multi-agent tasks, audits, parallel work, anything going to agent teams. Don't use when: simple Q&A, pure chat, immediate execution-only tasks. See "Don't Use When" section for details. Outputs: Structured XML/Markdown prompt, quality score (before/after), optional team brief + per-agent sub-prompts, agent team output files. Success criteria: Single mode quality score ≥ 7/10; Repromptception per-agent prompt quality score 8+/10; all required sections present, actionable and specific.
adaptive-compaction
IncludedAdaptive add-on policy and recovery layer that decides WHEN to compact, prune, snapshot, or fork -- replacing fixed-percent auto-compaction across Claude Code, Codex, and MCP-capable hosts. Trigger on auto-compact timing or damage: "when should I compact", "is it safe to compact now or start a fresh session", "auto-compact fires too early/mid-task", "switching to an unrelated task but the window still has space", "context rot", "answers get worse the longer the session runs", "the agent forgot the plan or my decisions after it summarized", "add a layer on top that manages context without changing the agent", raising autoCompactWindow to give the policy room, or installing/tuning a cross-tool compaction policy or PreCompact hook -- even when "compaction" is never said but the problem is context-window pressure or post-summarization memory loss. Do NOT use to summarize a conversation, build RAG, write a summarization prompt (decides WHEN not HOW), or answer max-context-length trivia.
agent-skill-creator
IncludedCreate cross-platform agent skills from workflow descriptions. Activates when users ask to create an agent, automate a repetitive workflow, create a custom skill, or need advanced agent creation. Triggers on phrases like create agent for, automate workflow, create skill for, every day I have to, daily I need to, turn process into agent, need to automate, create a cross-platform skill, validate this skill, export this skill, migrate this skill. Supports single skills, multi-agent suites, transcript processing, template-based creation, interactive configuration, cross-platform export, and spec validation.
llm-wiki
IncludedUse when building or maintaining a persistent personal knowledge base (second brain) in Obsidian where an LLM incrementally ingests sources, updates entity/concept pages, maintains cross-references, and keeps a synthesis current. Triggers include "second brain", "Obsidian wiki", "personal knowledge management", "ingest this paper/article/book", "build a research wiki", "compound knowledge", "Memex", or whenever the user wants knowledge to accumulate across sessions instead of being re-derived by RAG on every query.
skill-master
IncludedAgent Skills authoring, evaluation, and optimization. Create, edit, validate, benchmark, and improve skills following the agentskills.io specification. Use when designing SKILL.md files, structuring skill folders (references, scripts, assets), ingesting external documentation into skills, running trigger evals, benchmarking skill quality, optimizing descriptions, or performing blind A/B comparisons. Keywords: agentskills.io, SKILL.md, skill authoring, eval, benchmark, trigger optimization.