Skip to content
Skills Library
Data & analytics · Analysis

graph-data-explore

/graph-data-explore

Explore a graph data structure — nodes, edges, statistics, paths, and visualization. Use when working with DOT, GML, GraphML, or Mermaid files.

Licence
Apache-2.0
Last repository change
20.07.2026

Assessment and security

90/ 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.
Content25 / 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 20.07.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

Explore a graph data structure — nodes, edges, statistics, paths, and visualization. Use when working with DOT, GML, GraphML, or Mermaid files.

Arguments

/graph-data-explore <file-path>
Original author description

Explore a graph data structure — nodes, edges, statistics, paths, and visualization. Use when working with DOT, GML, GraphML, or Mermaid files.

How it works

  1. Steps
Original SKILL.md headings · 28 lines, 299 words
SKILL.md preview
---
name: graph-data-explore
description: Explore a graph data structure — nodes, edges, statistics, paths, and visualization. Use when working with DOT, GML, GraphML, or Mermaid files.
allowed-tools: mcp__localdata__connect_database mcp__localdata__get_graph_stats mcp__localdata__get_edges mcp__localdata__get_neighbors mcp__localdata__get_node mcp__localdata__find_path mcp__localdata__export_graph
argument-hint: "<file-path>"
---

# Graph Data Explore

Connect to a graph data file, analyze its structure and key nodes, find paths, and export visualizations.

## Steps

1. **Connect to the graph.** Call `connect_database` with the file path from `$ARGUMENTS`. The tool auto-detects graph formats including DOT, GML, GraphML, and Mermaid. Note the assigned database name.

2. **Get graph statistics.** Call `get_graph_stats` with the database name. Review: node count, edge count, density, whether the graph is directed or undirected, connected components count, and average degree. This gives an overview of the graph's scale and connectivity.

3. **Identify hub nodes.** From the stats, note nodes with the highest degree (most connections). Call `get_neighbors` for the top 3 highest-degree nodes to understand what they connect to. These hubs are often the most important entities in the network.

4. **Explore structure.** Call `get_edges` to retrieve a sample of edges. Look for patterns: are edges weighted? Do they have labels or types? Is the graph sparse or dense? Identify any isolated components or bridges.

5. **Inspect specific nodes.** For nodes of interest (hubs or user-specified), call `get_node` to retrieve node attributes and metadata. Note any labels, types, or properties that provide context.

6. **Find paths.** If there are at least two notable nodes, call `find_path` between them. Review the shortest path length and the intermediate nodes. This reveals how information or relationships flow through the network.

7. **Export a visualization.** Call `export_graph` with a suitable format (DOT for Graphviz rendering, or the original format for round-tripping). For large graphs, suggest filtering to a subgraph around nodes of interest before exporting.

8. **Summarize findings.** Present:
   - Graph type (directed/undirected, weighted/unweighted)
   - Scale: node and edge counts, density
   - Key structural features: hubs, communities, bridges
   - Notable paths or relationships discovered
   - Suggestions for further exploration or subgraph analysis

Versions

The database has no other skills named graph-data-explore.

Database snapshot: 13.11.2026 · package version 326652d81321 (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'',…
  • 85graph
    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…
  • 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.
  • 87explore
    Quick, interactive data exploration without the full pipeline. Use this skill whenever a user wants to explore data, understand what's in a dataset, browse tables or columns, check data distributions, spot patterns, or get familiar with data before analysis. Trigger on phrases…
  • 95render
    Convert Neo4j graph data into Markdown documents with Mermaid diagrams. Use when: render graph, generate docs, or the user says "/nacl:render md". Excalidraw board rendering moved to analyst-tool — see the file body.
  • 100graph-lcb
    Use the `graph` CLI (graph-lcb) to build, validate, and query typed, evidence-backed knowledge graphs stored in a local `.graph/` workspace. Make sure to use this skill whenever the user mentions graph-lcb, the `graph` command, a `.graph/` folder, graph.json, entity or edge…

Feedback and reports

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