菜单
Analyze your network structure and recommend optimal topology (dense, sparse, or hybrid) for spreading your idea. Use when you need to decide: should I develop this privately or go public? Dense networks for development and trust-building, sparse for viral scale.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Engineer ideas to spread successfully using Heylighen's 4-stage memetic replication model (Assimilation → Retention → Expression → Transmission). Use this skill whenever someone wants to make an idea stick, spread, or survive in an organization or audience — e.g., "my idea isn't landing", "people keep forgetting this", "nobody is sharing it", "how do I get buy-in", "help me pitch this", "why isn't this spreading", "how do I make this go viral internally", "I need this to survive a meeting". Also use for diagnosing why a specific idea is dying (which of the 4 stages is failing) and prescribing targeted fixes. Grounded in Finkelstein's Memetics Compendium (2009).
Intelligent router for the memetics skill network. Uses Heylighen's A→R→E→T diagnostic (Assimilation → Retention → Expression → Transmission) to identify which stage of memetic replication is failing, then routes to the right specialized skill. Use whenever you have a memetics question or want to make an idea spread — especially "my idea isn't landing", "people forget it", "nobody is sharing it", "I want to build a movement", "should I try to spread this?", or any memetics question where you're not sure which skill to start with.
Map the ecosystem of reinforcing ideas around a concept. Identifies which memeplex an idea belongs to, what ideas support or compete with it, and what mimetic desire dynamics drive its carriers. Use when you need to understand the ideological landscape before spreading an idea, or when you want to understand why an idea is thriving or dying. Trigger on: "What's the memeplex around this?", "What ideas compete with mine?", "Why does this idea keep coming back?", "Map the idea ecosystem", "What's reinforcing this narrative?"
Adapt memetics playbooks to specific application domains (personal branding, product launches, social movements, etc.). Takes general memetics strategy and tailors it to domain-specific contexts, metrics, and tactics. [NEEDS SOURCE MATERIAL] Source provides brief examples of three domains but doesn't fully detail the domain-specific playbooks. Each domain needs detailed expansion.
Design and implement tactics to strengthen a network's resistance to unwanted memes and supermeme traps. Standalone defensive skill for teams, organizations, or networks wanting to build critical thinking and memetic resilience. [NEEDS SOURCE MATERIAL] Source describes immunity-building goal but doesn't detail the full implementation methodology, frequency, or specific frameworks to teach.
Classify a raw idea or concept into its memetic type (meme, antimeme, supermeme, or cliche). Use this skill when you have an idea and need to understand its spreading properties, or when you're evaluating whether an idea will naturally transmit or face resistance. Trigger on: "What type of meme is this?", "Will this spread?", "Is this a good idea to promote?", "Classify this idea", "What kind of meme is X?"
| name | map-network |
| description | Analyze your network structure and recommend optimal topology (dense, sparse, or hybrid) for spreading your idea. Use when you need to decide: should I develop this privately or go public? Dense networks for development and trust-building, sparse for viral scale. |
You are analyzing network structure and recommending optimal topology for spreading an idea.
Takes a description of your network and the idea type, then recommends the best network structure:
Outputs explain tradeoffs and switching strategy.
Accepts:
Produces:
Passes to:
Analyze your current network on these dimensions:
Dimension 1: Density (how connected)
Dimension 2: Homogeneity (how similar)
Dimension 3: Context (how much shared history)
Dimension 4: Formality (structure level)
Match the idea type to network properties:
If MEME (high transmit, low impact):
If ANTIMEME (low transmit, high impact):
If SUPERMEME (high transmit, high impact):
Use dense networks for developing antimemes (high-impact, hard-to-spread ideas).
Strengths of Dense Networks:
Weaknesses of Dense Networks:
Critical Nuance: Density ≠ Strength. Dense networks seem safer but can be penetrated by a single novel idea. This is why "isolated environments lead to greater speciation and biodiversity" — isolation creates unique vulnerabilities and evolutionary paths.
Best for:
Tactics:
Use sparse networks for spreading memes (high-transmit, lightweight ideas).
Strengths of Sparse Networks:
Weaknesses of Sparse Networks:
Best for:
Tactics:
Historical context: "One theory as to why cults flourished in the 1960s and 1970s might be due to the new ways in which ideas were able to spread. Small towns were suddenly hit by a deluge of ideas from new forms of transportation and mass media, but they lacked the ability to process these ideas effectively."
This reveals a critical risk: dense networks can become cult-like when they lack immune systems to process external ideas. When selecting network topology, ensure:
Fundamental insight: "Culture is downstream of the shape of our networks. Sparse networks, like public social platforms, are good at diffusing ideas quickly. Dense networks, like group chats, are better at reinforcing and strengthening ideas."
This means:
Choose network topology not just for spreading your idea, but for what culture you want to emerge.
For most serious antimemes, recommend hybrid:
Dense Phase (Years 1-2):
Transition Phase (6 months):
Sparse Phase (Years 2-3+):
Key principle: "Memetic and antimemetic cities depend on each other"
For each recommendation, explain:
Density Tradeoff:
Timeline Tradeoff:
Group Size Tradeoff:
Authority Tradeoff:
## Recommended Topology: [DENSE | SPARSE | HYBRID]
**Idea Type:** [meme | antimeme | supermeme]
**Strategic Goal:** [development | scale | validation]
---
## Why This Topology
**Fit Analysis:**
- Idea transmissibility: [high | low] → favors [sparse | dense]
- Idea impact: [high | low] → favors [dense | sparse]
- Your goal: [you need] [privacy/validation/reach]
- Timeline: [X years] → recommends [this topology]
---
## This Topology's Strengths
For your situation:
- [Specific strength 1 relevant to your goal]
- [Specific strength 2 relevant to your idea]
- [Specific strength 3 relevant to your timeline]
---
## Weaknesses to Watch
- [Specific weakness 1 and how to mitigate]
- [Specific weakness 2 and how to mitigate]
- [Specific weakness 3 and how to mitigate]
---
## Implementation Tactics
**Immediate (next 30 days):**
- [Action 1]
- [Action 2]
- [Action 3]
**Medium-term (3-6 months):**
- [Action 1]
- [Action 2]
- [Action 3]
**Long-term (6+ months):**
- [Action 1]
- [Action 2]
- [Action 3]
---
## If Hybrid: Switching Strategy
**Dense Phase Objectives:**
- [Develop X]
- [Build Y]
- [Refine Z]
**Transition Triggers:**
- When: [specific conditions indicate readiness]
- Who decides: [champion, core group, measurement?]
- How quick: [gradual or rapid shift?]
**Sparse Phase Launch:**
- Start with: [which platform(s)?]
- Lead with: [which champions?]
- Amplify with: [validators, content types, timing]
---
## Risks Specific to This Topology
- [Risk 1 and mitigation]
- [Risk 2 and mitigation]
- [Risk 3 and mitigation]
Mistake 1: Using wrong topology for idea type
Mistake 2: Staying too long in dense phase
Mistake 3: Going public too early
Mistake 4: Confusing "private" with "secret"
Mistake 5: Ignoring context collapse
See /references/source-summary.md: