mcpField
L
ln-022-researchgraph

ln-022-researchgraph

github.com/levnikolaevichProductivity58470 installsUpdated 2d ago
Repository

About ln-022-researchgraph

ln-022-researchgraph is a skill for querying and auditing project research graphs, aimed at users tracking hypotheses, goals, evidence, and benchmark runs. It routes questions to graph operations and provides a manual file-reading fallback.

Key features

  1. 01Verify or rebuild the research index
  2. 02Inspect hypotheses and goals
  3. 03Find evidence and benchmark runs
  4. 04Trace lineage and goal trees
  5. 05Audit gaps and research drift
  6. 06Export research maps and canvases

Use cases

  1. 01Check hypothesis status and goal readiness
  2. 02Review benchmark evidence and sources
  3. 03Find missing links or project metadata
  4. 04Generate a research graph map

MCP support

Uses hex-research-mcp for indexing and querying research files, with hex-research operations when available. MCP-unavailable workflows fall back to manual file reads.

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/levnikolaevich/claude-code-skills --skill ln-022-researchgraph

After installing, type/ln-022-researchgraphin Claude Code to confirm it loaded.

Bundled filesreferences/researchgraph_mcp_usage.md

Details

From the project README

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

InputRequiredSourceDescription
project_pathyesargs or CWDProject root containing research graph files
commandnoargsSpecific 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 intentTool
live, pending, rejected, mixed, not-started hypothesesfind_hypotheses
inspect H##inspect_hypothesis
inspect G## or goal statusinspect_goal
evidence, sources, benchmark prooffind_evidence
targeted or comprehensive benchmark runsfind_runs
parent/child hypothesis chaintrace_lineage
graph hubs, disconnected nodes, shapeanalyze_topology
missing goals, sources, task gaps, driftaudit_orphans
goal treetrace_goal_tree
goal readiness, derived metrics, and metric coverageinspect_goal, audit_goal_alignment
source quality or evidence depthinspect_hypothesis, find_evidence, analyze_proposed
changed research files and field-level deltas in current diffanalyze_progress
readiness of proposed next hypothesesanalyze_proposed
JSON Canvas exportexport_canvas
generated docs/research-map.md exportexport_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

Comments

Markdown supported