Obsidian Canvas Boards
AgriciDaniel/claude-obsidian
Creates, inspects and updates Obsidian JSON Canvas boards in a vault, with text, file, link, group and edge nodes, using safe recoverable edits.
Run the full OpenTrace knowledge-graph pipeline over a folder or repo — index, clustering, highlight surfacing, and the markdown / graphml / Obsidian exporters.
Install Graph
$ npx skills add opentrace/opentrace --skill graph -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install opentrace/opentrace graph --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/opentrace/opentrace.git skills-src && mkdir -p .claude/skills && cp -r skills-src/plugins/claude-code/skills/graph .claude/skills/graph && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "graph" agent skill from https://github.com/opentrace/opentrace/tree/main/plugins/claude-code/skills/graph into .claude/skills/graph/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "graph", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/opentrace/opentrace/tree/main/plugins/claude-code/skills/graphType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add opentrace/opentrace --skill graph -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install opentrace/opentrace graph --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/opentrace/opentrace.git skills-src && mkdir -p .agents/skills && cp -r skills-src/plugins/claude-code/skills/graph .agents/skills/graph && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "graph" agent skill from https://github.com/opentrace/opentrace/tree/main/plugins/claude-code/skills/graph into .agents/skills/graph/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "graph", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add opentrace/opentrace --skill graph -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install opentrace/opentrace graph --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/opentrace/opentrace.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/plugins/claude-code/skills/graph .cursor/skills/graph && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "graph" agent skill from https://github.com/opentrace/opentrace/tree/main/plugins/claude-code/skills/graph into .cursor/skills/graph/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "graph", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/opentrace/opentrace.git --path plugins/claude-code/skills/graph--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add opentrace/opentrace --skill graph -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install opentrace/opentrace graph --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/opentrace/opentrace.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/plugins/claude-code/skills/graph .gemini/skills/graph && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "graph" agent skill from https://github.com/opentrace/opentrace/tree/main/plugins/claude-code/skills/graph into .gemini/skills/graph/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "graph", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install opentrace/opentrace graphInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add opentrace/opentrace --skill graph -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/opentrace/opentrace.git skills-src && mkdir -p .github/skills && cp -r skills-src/plugins/claude-code/skills/graph .github/skills/graph && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "graph" agent skill from https://github.com/opentrace/opentrace/tree/main/plugins/claude-code/skills/graph into .github/skills/graph/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "graph", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add opentrace/opentrace --skill graph -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install opentrace/opentrace graph --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/opentrace/opentrace.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/plugins/claude-code/skills/graph .opencode/skills/graph && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "graph" agent skill from https://github.com/opentrace/opentrace/tree/main/plugins/claude-code/skills/graph into .opencode/skills/graph/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "graph", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
graph- GitHub stars
- 108
- Token cost
- ~746 tokens
- SKILL.md length
- 262 words
- Files
- 1
- Skills in repo
- 2
- Repo updated
- First seen
- Licence
- Apache-2.0
At a glance
Run the full OpenTrace knowledge-graph pipeline over a folder or repo — index, clustering, highlight surfacing, and the markdown / graphml / Obsidian exporters.
- The user wants more than the bare structural index: when they ask for clusters
- SKILL.md covers Request, Routing, When the graph does not exist… and Conventions
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
- A navigable artifact to hand to another tool
What it does
Graph is an agent skill from opentrace/opentrace. 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…
Its SKILL.md is about 750 tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in Knowledge Management, covering Knowledge graphs. It works with Obsidian. The repository describes itself as: OpenTrace is a knowledge graph platform that maps system architecture, code structure, and service relationships giving you a visual, queryable map of how your codebase and… The licence is Apache-2.0.
When your agent uses it
- The user wants more than the bare structural index: when they ask for clusters
- A navigable artifact to hand to another tool
- : - build the knowledge graph
- Make a graph of this folder
Example prompts
- “build the knowledge graph”
- “make a graph of this folder”
- “graph this”
- “/graph”
Requirements
- Pre-approved tools (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
What it can do on your machine
Read from SKILL.md and the folder at commit 4f448b3. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves these tools, so the agent can use them without asking each time:
BashReadWriteAgentmcp__opentrace_oss__search_graphmcp__opentrace_oss__get_nodemcp__opentrace_oss__traverse_graphmcp__opentrace_oss__list_nodesmcp__opentrace_oss__get_stats
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md.
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Graph loads about 746 tokens when it runs. Until then it costs about 205 tokens; SKILL.md has 262 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check: notes
The automated check noted patterns worth knowing about, such as sudo or a known installer.
- NotePre-approves every shell command (allowed-tools: Bash)SKILL.md
allowed-tools: Bash, Read, Write, Agent, mcp__opentrace_oss__search_graph, mcp__opentrace_oss__get_node, mcp__opent
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from opentrace/opentrace at commit 4f448b3, republished under its Apache-2.0 licence (© opentrace). 262 words, ~746 tokens.
Download SKILL.mdSave it as
.claude/skills/graph/SKILL.md (or your agent's skills folder).- 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
CALLSedges carry aconfidencevalue — 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.dbthe slash commands wrote to. There is one graph, not two.
© opentrace, Apache-2.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
Just SKILL.md in plugins/claude-code/skills/graph of opentrace/opentrace.
Open the folder on GitHubat commit 4f448b3
Compare with similar skills
Graph next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Graph this skillopentrace/opentrace | 108 | — | ~746 | Automated safety check: Notes | Apache-2.0 | |
| Obsidian Canvas BoardsAgriciDaniel/claude-obsidian | 15k | — | ~1.4k | Automated safety check: Pass | MIT | |
| Subscription Videos MetadataEfficientStreet/youtube-subscriptions-ingest | 178 | — | ~7.1k | Automated safety check: Notes | MIT | |
| Sage Wikixoai/sage-wiki | 620 | — | ~2.4k | Automated safety check: Pass | MIT | |
| My WikiNimaChu/my-wiki | 124 | — | ~674 | Automated safety check: Pass | MIT | |
| Engraphdevwhodevs/engraph | 171 | — | ~792 | Automated safety check: Pass | MIT |
Similar skills
Subscription Videos Metadata
EfficientStreet/youtube-subscriptions-ingest
Pull metadata from YouTube subscription videos into a second-brain vault as a real cross-linked knowledge graph — not just a flat archive.
Sage Wiki
xoai/sage-wiki
Reference skill for sage-wiki — local-first knowledge graph with MCP server, REST API, compiled wiki, and Obsidian-compatible output.
My Wiki
NimaChu/my-wiki
Work with a local My Wiki knowledge base, Dashboard, and knowledge graph.
Engraph
devwhodevs/engraph
Index and search document collections using hybrid semantic + graph + full-text search.
Obsidian Literature Workflow
Galaxy-Dawn/claude-scholar
Runs a project literature review in an Obsidian vault: paper notes in Sources/Papers feed Knowledge synthesis, a Writing handoff and a default literature canvas.
More from opentrace/opentrace
Explore Code
opentrace/opentrace
Explore code structure, architecture, files, directories, and component relationships using the OpenTrace knowledge graph.
Related
Works with
Categories
Questions about Graph
What does Graph do?
Run the full OpenTrace knowledge-graph pipeline over a folder or repo — index, clustering, highlight surfacing, and the markdown / graphml / Obsidian exporters. Graph is an agent skill from opentrace/opentrace. Run the full OpenTrace knowledge-graph pipeline over a folder or repo — index, clustering, highlight surfacing, and the markdown / graphml / Obsidian exporters.
When should I use Graph?
Graph fits situations like: the user wants more than the bare structural index: when they ask for clusters; A navigable artifact to hand to another tool; : - build the knowledge graph; make a graph of this folder.
How do I install Graph in Claude Code?
Run `npx skills add opentrace/opentrace --skill graph -a claude-code`. Or copy the skill folder (plugins/claude-code/skills/graph in opentrace/opentrace) into .claude/skills/graph in your project. Claude Code loads it when a task matches its description.
How do I install Graph in Codex?
Run `npx skills add opentrace/opentrace --skill graph -a codex`. Or copy the skill folder (plugins/claude-code/skills/graph in opentrace/opentrace) into .agents/skills/graph in your project. Codex loads it when a task matches its description.
Can I use Graph in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add opentrace/opentrace --skill graph -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/graph, .gemini/skills/graph, .github/skills/graph and .opencode/skills/graph in your project.
What does Graph need to run?
SKILL.md names no scripts, command-line tools or credentials: Graph is instructions for the agent only. Its frontmatter pre-approves these 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.
Does Graph access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Graph safe to install?
Our automated static check of SKILL.md found notes only (pre-approves every shell command (allowed-tools: bash)), nothing it rates as a warning. It is not a guarantee. Review the folder before installing.
What licence does Graph use?
Graph is published under the Apache-2.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Graph use?
About 746 tokens (SKILL.md is roughly 3k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Graph?
Skills that share tags, products or a category with Graph: Obsidian Canvas Boards (AgriciDaniel/claude-obsidian, 15k stars), Subscription Videos Metadata (EfficientStreet/youtube-subscriptions-ingest, 178 stars), Sage Wiki (xoai/sage-wiki, 620 stars) and My Wiki (NimaChu/my-wiki, 124 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Graph?
opentrace (a GitHub organization) maintains it in opentrace/opentrace, which has 108 GitHub stars. The repository holds 2 skills in this directory. The repository was last updated on August 12, 2026.
Source: opentrace/opentrace on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.