network-text-analysis
Skill0 starsChanged 3 months agoMITView on GitHub
Analyze text, discourse, or knowledge using network/graph thinking. Identifies structural gaps between topic clusters as spaces for novel ideas. Diagnoses discourse state (biased/focused/diversified/dispersal) and steers toward cognitive variability. Use when: (1) analyzing a document/article for blind spots, (2) finding content gaps in SEO or research, (3) diagnosing why a text feels one-sided or scattered, (4) generating research questions from existing knowledge, (5) comparing multiple texts for overlap/differences, (6) building knowledge graphs from notes, (7) improving writing coherence, (8) brainstorming by bridging disconnected idea clusters.
In this repository9 other files it gives its agents.
- belentani-magicSkill
- debugging-wizardSkill
- deep-researchSkill
- graphifySkill
- gsap-animationsSkill
- skill-security-auditorSkill
- token-optimizerSkill
- workflow-orchestratorSkill
- writing-skillsSkill
The file
We split this skill into the rules it gives an agent
6 rules. About 0 are common, 6 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈6
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 62
Read the text. Extract 15-30 key concepts.
- Distinctive: line 89
Check: are ideas clustered or scattered?
- Distinctive: line 90
If dispersed: add transitional concepts between clusters.
- Distinctive: line 91
If biased: develop underrepresented clusters.
- Distinctive: line 92
If focused: check for saturation — diversify.
- Distinctive: line 97
Start with existing knowledge (a text, notes, research).
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Network Text Analysis
Think of any text as a network: words are nodes, co-ocurrences are edges. Apply graph theory to find patterns, gaps, and structure invisible to linear reading.
Core Algorithm (4 Steps)
1. Extract the Network
From any text, extract:
- Nodes: Key concepts (nouns, noun phrases, named entities). Remove stopwords.
- Edges: Co-occurrence within a sentence or sliding window (4-gram). Weight = frequency.
- Output: Adjacency list or edge table:
(concept_a, concept_b, weight)
2. Detect Topical Clusters
Group nodes that co-occur frequently into clusters. Each cluster = a主题/topic.
Heuristic without formal modularity: group nodes that share more edges with each other than with outsiders. Identify 3-7 clusters.
3. Rank by Betweenness Centrality
Nodes that bridge multiple clusters have HIGH betweenness centrality. These are:
- The most "influential" concepts
- Pathways for meaning circulation
- Entry points into the discourse
Simple proxy: count how many clusters a node's neighbors span.
4. Find Structural Gaps
Identify cluster pairs that are distant but could connect. These gaps are:
- Blind spots in the discourse
- Spaces where novel ideas emerge
- Research question generators
A gap exists when two clusters share NO or FEW direct connections but a bridging node could link them.
The 4 Cognitive States
Diagnose the discourse structure to determine which state it's in:
| State | Signature | Problem | Fix |
| Biased | 1 dominant concept, everything orbits it | Tunnel vision, obsession | Introduce perspectives from other clusters |
| Focused | Dense coherent cluster, clear narrative | Saturation, diminishing returns | Surface latent topics, bridge to other clusters |
| Diversified | Multiple distinct clusters with visible gaps | Analysis paralysis | Consolidate around one path OR bridge gaps |
| Dispersed | Weak connections, fragmented, scattered | Incoherence, anxiety | Anchor to highest-betweenness node |
Cycle: Biased → Focused → Diversified → Dispersed → Biased (healthy variability)
Pathological: Dwelling too long in ANY state. Recovery comes from transitions, not persistence.
Practical Workflows
Analyze a Document
- Read the text. Extract 15-30 key concepts.
- Build co-occurrence matrix (which concepts appear together).
- Cluster into 3-5 topic groups.
- Identify the top 3-5 bridging concepts (high betweenness).
- Find gaps: which clusters lack connections?
- Generate 2-3 research questions that bridge the gaps.
- Diagnose state: biased? focused? diversified? dispersed?
Find Content Gaps (SEO/Research)
- Analyze existing content (yours + competitors).
- Map what topics are covered (clusters).
- Identify what's MISSING (gaps between clusters).
- Generate content ideas that bridge those gaps.
- Questions to answer: "What do people search for that nobody covers?"
Compare Two Texts
- Extract networks from both texts.
- Find OVERLAP: shared concepts and clusters.
- Find DIFFERENCE: concepts/clusters unique to each.
- The unique parts = differentiating perspectives.
- The overlap = common ground.
Improve Writing Coherence
- Extract concepts from draft.
- Check: are ideas clustered or scattered?
- If dispersed: add transitional concepts between clusters.
- If biased: develop underrepresented clusters.
- If focused: check for saturation — diversify.
- Goal: diversified state with bridged gaps.
Brainstorm from Gaps
- Start with existing knowledge (a text, notes, research).
- Extract network and find structural gaps.
- For each gap: "What would connect these two clusters?"
- Generate 5 wild ideas per gap.
- Filter: which ideas are novel AND feasible?
Quick Reference
See references/methodology.md for:
- Formal betweenness centrality calculation
- Community detection algorithm details
- Structural gap detection pseudocode
- Cognitive state transition rules
- Network analysis MCP tool catalog (if available)
Key Insight
Most creative insights live in gaps between established patterns. Linear reading hides these gaps. Network analysis reveals them. The goal is not efficiency — it's cognitive variability: the ability to shift between focused depth and exploratory breadth, never dwelling too long in any single mode.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

