Skip to content
Skills Library
Data & analytics · Analysis

explore-network

/explore-network

Explore the graph already open in Gephi through intake, profiling, goal-directed analysis, styling, layout, and an overview. Use when the user has a graph loaded and wants an initial guided exploration without importing a file.

Repository
gephi-ai ↗
Licence
Apache-2.0
Last repository change
12.10.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 12.10.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 the graph already open in Gephi through intake, profiling, goal-directed analysis, styling, layout, and an overview. Use when the user has a graph loaded and wants an initial guided exploration without importing a file.

Original author description

Explore the graph already open in Gephi through intake, profiling, goal-directed analysis, styling, layout, and an overview. Use when the user has a graph loaded and wants an initial guided exploration without importing a file.

How it works

  1. Rules this workflow must keep
  2. Steps
Original SKILL.md headings · 75 lines, 799 words
SKILL.md preview
---
name: explore-network
description: Explore the graph already open in Gephi through intake, profiling, goal-directed analysis, styling, layout, and an overview. Use when the user has a graph loaded and wants an initial guided exploration without importing a file.
---

# Explore

Run the initial exploration on the graph in the current Gephi workspace. This
is the `import-and-explore` workflow without the import step: open the file in Gephi first
(File > Open, or a Data Laboratory import), then run this. No file path is
needed.

Follow the `gephi` skill's rules throughout; this workflow repeats only the ones
it is most likely to break.
Read `../gephi/references/layout-guide.md` before the
layout step and `../gephi/references/change-over-time.md`
when the graph has time data.

**Tell the user what you are doing at each step.** Narrate briefly before each tool call.

## Rules this workflow must keep

- **Asking.** When a step says to ask, ask once. If the person cannot answer, is away, or asked for a finished product, use the default named in that step and remove or overwrite nothing. At the end, give one short line for each choice that changed the result, under "Choices I made"; leave the section out when every step used its obvious default. If there is no input to work on, stop and say what is needed.
- **Session start.** Start with `gephi_health_check`. Then check which workspace is open (`gephi_list_workspaces`) and whether a filter is active (`filter_active` in replies): a filter from an earlier conversation stays on, and exports and checks then see only what it shows.
- **Stability.** Run `gephi_community_stability` before naming, captioning, or colouring by groups, and say how stable they are.
- **Filtering.** `gephi_apply_filter` and `gephi_apply_filters` hide nodes and change nothing; `gephi_reset_filters` shows them again. Pass `dry_run` to count what a filter would hide or remove before running it. The remove and extract tools delete, keep one undo level, and have no redo; for an experiment, duplicate the workspace first.

## Steps

1. **Session start**: Call `gephi_health_check`. If it fails, tell the user to start Gephi and stop. Call `gephi_list_workspaces`; if `filter_active` is true, say so and that the exploration will see only the visible nodes.

2. **Confirm there is a graph**: Call `gephi_get_project_info`. If there is no project or the graph is empty, say so and suggest opening a file in Gephi or using the `import-and-explore` skill with a path; stop.

3. **The intake question** (skip if they already told you): in one friendly
   question, ask what the nodes and connections are and what they hope to
   learn. Their answer sets the vocabulary for everything you present, and
   their expectations become hypotheses to test rather than assumptions.
   Default: use the graph's own column names as the vocabulary and explore
   without prior hypotheses.

4. **Profile**: Call `gephi_profile_graph` (one call, the full quantitative
   picture). Give a short plain-language first reading that combines their
   description with the numbers, then ask the two or three questions the
   profile raises (its `flags` are candidates: isolates, fragmentation, hub
   dominance). Default: keep every node and continue with the whole graph.

5. **Let the intake and profile guide what follows.** Do not run a fixed
   recipe:
   - Time data (`gephi_get_timeline` shows `graph_is_dynamic`) or a date
     column: offer to compare periods (see the change-over-time reference).
     Default: explore the whole period at once.
   - Isolates or fragmentation: ask before removing anything (their "data
     problem" may be their finding). Default: keep them and report how many
     there are.
   - Their stated interest picks the metric (brokers or gatekeepers ->
     betweenness; influence or reach -> degree or PageRank; roles -> the
     similarity layout).
   - If they named an attribute they expect to organize the network, test it
     against the partition baseline before coloring by it; prefer detected
     communities when their attribute fails, and say so plainly.
   - Size and density pick the layout per the layout guide's purpose table.
   - Caption clusters in their vocabulary, not in cluster numbers.

6. **Style the graph** (guided by the above):
   - Communities: `gephi_compute_modularity` (resolution 1.0), then `gephi_community_stability`, and say how stable the groups are.
   - Color by community: `gephi_color_by_partition` with column `"modularity_class"` (or `stable_core` when the stability check warned), leaving `colors` unset so the plugin applies its validated palette, largest group first.
   - Size by degree: `gephi_size_by_ranking` with column `"degree"` and the default sizes (about one to ten on screen).

7. **Layout**: Tell the user: "Running ForceAtlas 2 layout..." Call `gephi_run_layout` with algorithm `"ForceAtlas 2"` in two passes with `sync: true`: first 1500 iterations with properties `{"linLogMode": false, "scalingRatio": 10, "strongGravityMode": true, "gravity": 0.01, "barnesHutOptimization": true}`, then 3000 iterations with `{"linLogMode": true, "scalingRatio": 0.5, "strongGravityMode": true, "gravity": 0.001, "barnesHutOptimization": true}` (see the layout guide). Leave Dissuade Hubs off.

8. **Report**: Summarize:
   - Graph size (nodes, edges)
   - Graph type (directed or undirected)
   - Number of communities found, and how stable they are
   - Number of connected components
   - Average degree
   - Choices I made, one short line per choice that changed the result (leave out if none)
   - Ready for further analysis: suggest next steps (centrality, export, and so on)

Versions

The database has no other skills named explore-network.

Database snapshot: 13.11.2026 · package version 45f44656d412 (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

  • 100analyze-network
    Run a rigorous structural analysis of the loaded Gephi graph, compare centralities, characterize communities, and report what the data does and does not support. Use for comprehensive network analysis or interpretation rather than one claim or a styling-only task.
  • 90visualize-network
    Turn the graph currently open in Gephi into a clean, legible, publication-ready map through a measured layout, visual-QA, inspection, and adjustment loop. Use for visualize, lay out, style, make this readable, or make this publication-ready.
  • 100graph-the-network
    Build an entity-relationship link-analysis graph of an investigation — nodes, typed edges carrying source and confidence, aliases, and temporal validity — to expose shared infrastructure, bridging nodes and the real principal behind a frontman. Covers Maltego, Neo4j and Cypher,…
  • 100explore
    Quick, interactive data exploration without the full pipeline. Trigger on "/explore", "let me explore the data", "browse the data", "show me a sample of the data", "what does the distribution look like?", "explore this table". DISAMBIGUATION: interactive poke-around within a…

Feedback and reports

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