Skip to content
Skills Library
Data & analytics · Automation

graph

/graph

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

Repository
opentrace ↗
Licence
Apache-2.0
Last repository change
12.08.2026

Assessment and security

85/ 100Class: good
Format25 / 25
Frontmatter with name and description, valid name, description up to 1,024 characters, name matching the folder.
Discoverability25 / 25
Description explains when to use the skill, has a reasonable length and uses third person.
Content20 / 35
At least 150 words and at most 500 lines, headings, step lists, examples or code.
Hygiene15 / 15
No placeholders such as TODO, no Windows paths, with a licence.
Riskno signals detected in the scan
Files in this package
1
Scripts
0
HTML comments
0
URLs in SKILL.md
0
Deprecation

No signals detected. Repository changed on 12.08.2026, without references to retired models or APIs.

Licence

Apache-2.0, otwarta: można używać i zmieniać, z zachowaniem licencji i informacji o zmianach.

What it does and when to use it

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

Triggers from the description

build the knowledge graphmake a graph of this foldergraph thiswhat is this codebase aboutgive me a map of this projectwhat-cluster the graph
Original author description

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

How it works

  1. Request
  2. Routing
  3. When the graph does not exist yet
  4. Conventions
Original SKILL.md headings · 46 lines, 310 words
SKILL.md preview
---
name: graph
description: |
  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
allowed-tools: Bash, Read, Write, Agent, mcp__opentrace_oss__search_graph, mcp__opentrace_oss__get_node, mcp__opentrace_oss__traverse_graph, mcp__opentrace_oss__list_nodes, mcp__opentrace_oss__get_stats
---

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.

| Intent | Command |
|---|---|
| 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.

Versions

RepositoryScoreLicence
This page · opentrace/opentrace85Apache-2.0
renzrollon/interlock100MIT
marfago-labs/paper-research100MIT
darioabc/massimo100MIT
AlicanKaya192/Mindgate100MIT
artemnovitckii/claude-animation-skills100MIT
wszqkzqk/scrinium100GPL-3.0
bartolli/codanna100Apache-2.0
smallnest/goal-workflow100MIT

Database snapshot: 13.11.2026 · package version c05ad46dff2e (SHA-256 digest of the entire package)

Downloads in the last 30 days: 0 · ranking

Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.

Similar skills

  • 91graphify
    Use when the user invokes /graphify or asks to build, update, or query a knowledge graph from a folder of files (code, docs, papers, notes, images). Triggers: ''map this codebase'', ''graph my notes'', ''what is connected across these files'', ''community detection'',…
  • 96kg-build
    Build a knowledge graph of a codebase, a docs folder, notes or a website as glassbrain JSON, saving a snapshot after each step so the build can be replayed and diffed. Use when asked to map, graph or explain the structure of a project, docs or site.
  • 90graph-data-explore
    Explore a graph data structure — nodes, edges, statistics, paths, and visualization. Use when working with DOT, GML, GraphML, or Mermaid files.
  • 100graphify
    Build and query a knowledge graph of a codebase, docs, and mixed media with the graphify CLI. Use when installing graphify via mise, building or updating a code graph, exporting it (GraphML, SVG, Neo4j, Obsidian, call-flow HTML), or querying it with query/path/explain/affected…
  • 100graph-colorize
    Configure Obsidian graph colors by tag, folder, category, or visibility by updating .obsidian/graph.json. Use for graph colorization; preserve other graph settings and back up before changes.
  • 100wiki-export
    Export the Obsidian wiki graph to JSON, GraphML, Neo4j Cypher, Postgres/SQL, HTML, or OKF bundles. Use when transferring or visualizing wiki data in external tools; wiki-import handles the reverse direction.

Feedback and reports

Your message goes to Bartosz Sokoliński. An email address is needed only for a reply. See the privacy policy.