Explores a component in the OpenTrace knowledge graph: searches matches, inspects details and relationships, summarizes connections, offers source reading or service dependency traversal.
From opentrace-ossnpx claudepluginhub opentrace/opentrace --plugin opentrace-oss/exploreAnalyzes blockchain addresses, transactions, smart contracts, blocks, and tokens, producing structured markdown reports with balances, histories, holdings, and insights.
/exploreExplores codebase to map structure, detect tech stack, patterns, entry points, and CI/CD setup, producing a structured project overview.
/exploreReads planning checklists and related code/files/tests to review and prepare for discussing a codebase area. Provide topic as arguments.
/exploreSearches codebase for keyword in files, code, git history; iteratively refines results interactively or via --auto/--depth, tracks dependencies with graphs and summaries.
/exploreReads planning checklists and related code/files/tests to review and prepare for discussing a codebase area. Provide topic as arguments.
/exploreReads planning checklists and related code/files/tests to review and prepare for discussing a codebase area. Provide topic as arguments.
Explore a component in the OpenTrace knowledge graph.
The user wants to explore: $ARGUMENTS
Use the OpenTrace MCP tools to investigate this component:
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).get_node with its ID to get full details including all neighbors.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.