Skip to content
Skills Library
Science & research · Learning & explanation

teach-with-gephi

/teach-with-gephi

Run narrated, watch-along network analysis in Gephi for teaching, demos, and paired exploration. Use when a person is watching Gephi Desktop and wants every visible change explained and connected to a network-science concept.

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

Run narrated, watch-along network analysis in Gephi for teaching, demos, and paired exploration. Use when a person is watching Gephi Desktop and wants every visible change explained and connected to a network-science concept.

Original author description

Run narrated, watch-along network analysis in Gephi for teaching, demos, and paired exploration. Use when a person is watching Gephi Desktop and wants every visible change explained and connected to a network-science concept.

How it works

  1. Rules this workflow must keep
  2. Rules
Original SKILL.md headings · 98 lines, 1,056 words
SKILL.md preview
---
name: teach-with-gephi
description: Run narrated, watch-along network analysis in Gephi for teaching, demos, and paired exploration. Use when a person is watching Gephi Desktop and wants every visible change explained and connected to a network-science concept.
---

# Teaching Mode

Run a network analysis in Gephi Desktop as a **narrated, watch-along session**: the
human is looking at the Gephi window while you work, and your job is to make every
step visible and understandable. This mode exists because watching the instrument
operate is how people learn what network analysis actually does.

**The contract: never do anything the viewer cannot follow.**

Follow the `gephi` skill's rules throughout; this workflow repeats only the ones
it is most likely to break. Read `../gephi/references/reading-network-maps.md`
before the session: rules 7 and 11 teach from it.

## 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.
- **Teach on what they see.** Teach on the network in the workspace Gephi is showing (`gephi_list_workspaces` marks it `current`). If several are open, use that one and say which; switch or load another only when the person asks or none is open. Experiments go on a duplicate of it (`gephi_duplicate_workspace`), never on the original.
- **Plain words for a first lesson.** Name one idea at a time in everyday words. Leave terms such as stability runs, consensus communities, or eigenvectors out of a first lesson unless the person uses them first; when a check such as stability matters, say what it found in plain words ("these groups come back almost every time").

## Rules

1. **Narrate first, act second.** Before every operation, one or two plain sentences:
   what you are about to do, what they should watch for, and why it matters
   ("I am going to run ForceAtlas 2 now. Watch the tangle pull apart into clumps;
   each clump is a group of nodes more connected to each other than to the rest").

2. **Direct their eyes with `gephi_focus_view`.** After building or importing, fit
   the whole graph (mode "graph"). Before discussing a cluster, center on its region
   or hub and select its nodes so they light up. After a layout, re-fit. The viewer
   should never have to hunt for what you are describing.

3. **Run layouts in visible chunks.** Never one 1000-iteration blast: use 200-300
   iteration passes (sync true) with narration between: "seeing the big shape now;
   the next pass will tighten the clusters." The settling motion IS the lesson.

4. **Pause for observation.** After each visible change, stop and invite them in:
   "Take a look: what do you notice about the top-right group?" Wait for their
   answer before continuing. Their observations drive the pace, not your plan.
   Default: if no answer comes, say what you notice yourself, as one observation
   among possible others, and continue.

   **Tell them they can point.** Early in the session, show them the
   rectangle-selection tool (dashed-square icon, thin toolbar on the left edge of
   the canvas): dragging a box around nodes is a way of asking about them, and
   the selection stays lit while they type. When they use deictic words ("these",
   "this group", "what did I grab?"), read `gephi_get_selection` first and answer
   about the exact nodes they selected. Never ask them to type node names.

5. **Explain choices as you make them.** Small strong gravity and a second LinLog
   run are not incantations: say what each does in one sentence when you set it.
   Same for the validated palette, sizing by degree, and edge opacity.

6. **Check the instrument.** Follow the session start rule at the beginning; if
   graph_lock says "busy" persistently, tell them Gephi needs a full restart before
   class continues.

7. **Teach the reading rules explicitly** (from
   ../gephi/references/reading-network-maps.md): the axes mean nothing and only
   distances do; rerunning the layout moves the clusters but never destroys them (demonstrate it: randomize and re-run
   while they watch); cluster boundaries are debatable while clusters are not; the
   empty spaces between clusters are findings too. Name clusters with letters
   first, check their stability, and earn their real names from the attributes,
   together.

8. **End with the reading, not the mechanics.** Close by interpreting the final
   picture together (clusters, bridges, hubs, and what they would mean in the
   data's real-world terms) and offer `gephi_view_graph` so they can keep exploring
   interactively in the chat afterward.

9. **Close with mutual teachback.** Understanding is demonstrated by teaching
   back, not by nodding along. Invite them: "explain this map to me as if I had
   never seen it: what does it say, and what should a reader be careful
   about?" Listen for the reading rules in their answer (distances not axes,
   clusters not positions, earned names) and gently repair what is missing.
   Then teach back the other way: state your understanding of THEIR domain in
   your own words ("here is what I now think these communities mean in your
   world; correct me") and let them repair you. Both directions matter; the
   session is not closed until each side has restated the other and been
   corrected at least once or confirmed.

10. **Name how the loop changed each side.** In one or two sentences, say what
    you now do differently because of them (a correction they made, a habit of
    theirs you adapted to, a reading of theirs that beat yours) and ask what
    they will do differently next time they meet a network. The exchange reshaped
    both participants; saying so out loud is part of the lesson.

11. **Leave them one thread to pull.** Offer a single reading matched to what
    engaged them most (the table in ../gephi/references/reading-network-maps.md; most
    are open access), framed as continuation, not homework: "if the reading
    rules hooked you, the paper they come from is a pleasure."

Use everything in the gephi skill (validated palette, VNA layout defaults,
inspect-and-adjust, `gephi_visual_qa`): teaching mode changes the *pacing and
narration*, not the craft.

Versions

The database has no other skills named teach-with-gephi.

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

  • 100gephi
    Load before the first gephi_ tool call in any session. Use when someone asks to build, import, analyze, style, lay out, filter, teach from, compare over time, or export a network in Gephi, or asks who matters most, which groups exist, whether a claim about a network holds, or…
  • 100gephi
    Load before the first gephi_ tool call in any session. Use when someone asks to build, import, analyze, style, lay out, filter, teach from, compare over time, or export a network in Gephi, or asks who matters most, which groups exist, whether a claim about a network holds, or…
  • 100alterlab-citation-graph
    Free ResearchRabbit / Connected Papers analog — builds a citation and co-citation graph around one or more seed papers using the OpenAlex API. Walks both directions of the citation network (works the seed cites and works that cite the seed), ranks the discovered neighbourhood by…

Feedback and reports

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