opentrace/opentrace/graph

Claude Code and agent skill by opentrace/opentrace

Trust tier 2
  • community
LLM review pending
Source check pending

Checking that the SKILL.md file is still in the repository.

Run the full OpenTrace knowledge-graph pipeline over a folder or repo — index, clustering, highlight surfacing, and the markdown / graphml / Obsidian exporters. Use this skill when the user wants more than the bare structural index: when they ask for clusters, highlights, or a navigable artifact to hand to another tool. Triggers on: - "build the knowledge graph", "make a graph of this folder", "graph this" - "what is this codebase about", "give me a map of this project", "what's connected to what" - "find the clusters", "cluster the graph", "what are the architectural hubs?" - any time a user mentions clustering, god nodes, or bridges - when `.opentrace/index.db` is already present in the working directory, an indexed graph exists — prefer answering from it over re-deriving answers from raw files

Install

npx vskill@latest install opentrace/opentrace/graph

SKILL.md

The user wants to build, refresh, or explore the OpenTrace knowledge graph. This skill is the on-ramp — point at the right slash command and run it.

Request

$ARGUMENTS

Routing

Match the user's intent to one of the commands below. When in doubt, default to /build for build / refresh and /interrogate for question-answering.

IntentCommand
Build the graph from scratch on a folder or GitHub URL/build [path or url]
Index only (no clustering / analysis)/index [path]
Re-run clustering/cluster
Surface god nodes, bridges, suggested questions/analyze
Quick exploration of a named component/explore <name>
Read-only Q&A over the graph/interrogate "<question>"
Shortest path between two graph nodes/path <A> <B>
Obsidian vault export/export-obsidian
Browsable markdown report/export-report
GraphML for Gephi / yEd/export-graphml
Counts of indexed nodes by type/graph-status

If the user asked a question the graph could answer directly (e.g. "what's connected to AuthMiddleware?") and .opentrace/index.db exists, run /interrogate yourself rather than asking the user which command to use.

When the graph does not exist yet

If .opentrace/index.db is missing and the user is asking a graph-flavoured question, offer to run /build first, then answer against the freshly built graph.

Conventions

  • Only CALLS edges carry a confidence value — a float from the call

resolver (1.0 for an exact in-scope match, lower for cross-file and heuristic ones). No other edge type has one, so don't report a confidence for edges that don't carry it.

  • After any build, the OpenTrace MCP tools (search_graph, get_node,

traverse_graph, list_nodes, get_stats) read the same .opentrace/index.db the slash commands wrote to. There is one graph, not two.

Security

  • Security scanPassed, 100 of 100Pattern checks on the skill's files.
  • Model reviewNot runA model review is scheduled for the next rescan.

Quality evaluation

  • Task evaluationNot runNo evaluation yet. Run one in Skill Studio.

Source

Popularity

Repository stars
106
Repository forks
10
7-day trend score
23

Stars and forks are for the whole GitHub repository, not this skill alone. Not refreshed yet.

Works with

Any agent vskill installs to: 56 targets in all. These 39 have a page on this site.

  • Claude Code
  • Cursor
  • GitHub Copilot
  • Windsurf
  • Codex
  • Gemini CLI
  • Cline
  • Amp
  • Roo Code
  • Goose
  • Continue
  • Kilo Code
  • Junie
  • Trae
  • OpenHands
  • Qwen Code
  • AI Agent
  • Tabnine Chat
  • Sourcegraph Cody
  • Amazon Q
  • Firebase Genkit
  • Sweep
  • Devin
  • Phind
  • Mentat
  • Claude Desktop
  • Aider
  • GPT Pilot
  • Plandex
  • bolt.new
  • v0
  • Replit Agent
  • Anse
  • TypingMind
  • BetterChatGPT
  • LibreChat
  • Warp AI
  • Pieces
  • Fig AI
Embed badge
vskill VERIFIED badge
[![vskill VERIFIED](https://verified-skill.com/api/v1/skills/opentrace/opentrace/graph/badge)](https://verified-skill.com/skills/opentrace/opentrace/graph)

Something wrong with this skill or its page? Tell us.