xmindify

Original：🇨🇳 Chinese
Translated

XMindify Mind Map Generator, supports scenario-based templates and automatic generation. It is used to create XMindMark files and convert them to XMind/SVG formats. Trigger scenarios: (1) User requests to create a mind map (2) User needs to analyze papers/summarize content/brainstorm (3) User mentions terms like "mind map", "brain map", "structured" etc.

112installs
Sourcephil-fan/xmindify
Added on

NPX Install

npx skill4agent add phil-fan/xmindify xmindify

Tags

Translated version includes tags in frontmatter
mind-map-generatorxmindmarkxmindsvg-conversionscenario-based-templates

SKILL.md Content (Chinese)

View Translation Comparison →

XMindify Mind Map Generator

Workflow

Execution Steps

  1. Determine Scenario - Select preset templates or generate automatically based on user intent
  2. Generate XMindMark - Strictly follow the syntax in SYNTAX.md to create 
    .xmindmark
    files
  3. Syntax Check - Check if the XMindMark file complies with syntax specifications, modify it until it meets the requirements if not
  4. Conversion & Export - Use CLI to convert to XMind and SVG formats

Scenario Routing

Select the appropriate scenario template based on user needs:
User IntentScenario FileTrigger Keywords
Analyze academic paperspaper.mdpaper, academic, research, paper
Summarize long-form contentsummary.mdsummarize, refine, organize, key points
Creative ideation/divergent thinkingbrainstorm.mdbrainstorm, creativity, idea, solution
Problem analysis/decision makinganalysis.mdanalyze, problem, decision, comparison
Project planningproject.mdproject, plan, roadmap, planning
No specific scenarioAutomatic generationIntelligently infer based on content
When user needs do not match preset scenarios:
  1. Extract Central Topic - Identify the core topic from user input
  2. Analyze Content Structure - Recognize key dimensions and hierarchical relationships
  3. Intelligent Organization - Automatically select the best organization method (time, category, priority, etc.) based on content type
  4. Add Visual Elements - Appropriately use boundary grouping, relationship connections, and summary nodes

XMindMark Conversion Commands

Install Xmindmark CLI using npm or pnpm: 
npm install -g xmindmark
Check if Xmindmark CLI is installed:
bash
xmindmark --version
If already installed, use the following scripts to convert and export to XMind and SVG formats:
bash
# Convert to XMind file
xmindmark -f xmind topic.xmindmark

# Convert to SVG image
xmindmark -f svg topic.xmindmark
  • You can use the 
    -o
    parameter to specify the output directory

Global Rules

  1. Comply with Syntax Specifications - Must strictly follow the syntax in SYNTAX.md, check before and after generation, modify until it meets the requirements if not
  2. Conciseness First - Mind maps are for extracting key points, not copying the full text
  3. Clear Hierarchy - Central Topic → Main Branch → Sub-branch → Details
  4. Logical Grouping - Use boundary 
    [B]
    to categorize related concepts
  5. Key Connections - Use only 1-2 relationships to mark the most core logical connections
  6. Summary & Refinement - Use 
    [S]
    to summarize key conclusions or limitations

Relationship Usage Restrictions

  • Maximum 2 connection pairs - i.e., maximum use of 
    [1]
    /
    [^1]
    and 
    [2]
    /
    [^2]
  • Only connect the most important causal relationships (e.g., insight → contribution, challenge → solution)
  • Avoid overusing relationships to keep the mind map clear

Boundary Usage Restrictions

  • Maximum 2 boundaries - i.e., maximum use of 
    [B1]
    /
    [B2]
  • Only use boundaries to group the most important concepts (e.g., concept 1, concept 2, concept 3)
  • Try not to use nested boundaries (e.g., 
    [B1][B2]
    )

Structure Specifications

  • Control each main branch to 3-7 child nodes
  • Hierarchy depth does not exceed 4 levels
  • Use 
    [B]
    to logically group related nodes
  • Use 
    [S]
    to create expandable summary nodes

Syntax Specifications

  • Must strictly follow the syntax in SYNTAX.md, check before and after generation, modify until it meets the requirements if not
  • 1 Tab = 4 spaces
  • No spaces after 
    []
    markers (after topic content)
  • Blank lines between sibling sub-topics will be ignored