All SkillsGet Started Free
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.
MCP get_skill({ skillId: "ln-022-researchgraph-02dfffb8" })Use this skill with your agent
Create a free account and connect via MCP
> **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
#agile-workflow#code-review#research#synthesishex-research-mcp