Skip to content
Agent Memory
Command

/explore

Explore a component in the OpenTrace knowledge graph.

BOOST
From plugin
opentrace
10916 skills6 agents16 commands1 MCP
Install
> /plugin marketplace add opentrace/opentrace
> /plugin install opentrace-oss@opentrace-oss

How it fires

How this command gets triggered: by you, by Claude, or both.

  • Fires itselfClaude auto-loads it when your prompt matches the work.
  • You can call itInvoke it directly when you want it.
  • Slash command/explore

Context preview

What this command does when you run it.

Explore a component in the OpenTrace knowledge graph.

Command definition

explore.md

Explore a component in the OpenTrace knowledge graph.

The user wants to explore: $ARGUMENTS

Use the OpenTrace MCP tools to investigate this component:

1. **Search**: Use `search_graph` with the query "$ARGUMENTS" to find matching nodes. Use `nodeTypes` to narrow if the query implies a type (e.g. service, class, function). 2. **Inspect**: For the best match, use `get_node` with its ID to get full details including all neighbors. 3. **Present**: Show the component's:

  • Type, name, and key properties
  • Immediate relationships (grouped by type)
  • Connected nodes summary

If the component is a File, Class, or Function and has a `path` property, offer to read the source with the `Read` tool. If it's a Service, show its upstream callers and downstream dependencies using `traverse_graph`.

Keep the output concise but informative — this is a quick exploration, not a deep analysis.

Ships withopentrace

A knowledge graph that maps your codebase structure, service architecture, and system relationships — then exposes it all through MCP so AI tools can understand your systems. Index any repo, any size, in seconds.

Get the whole plugin

Other commands on opentrace.

build
Command

build

Build a knowledge graph over the current folder (or a path / GitHub URL). Runs the native OpenTrace pipeline: index → cluster →…