mcpField
M
mindmap

mindmap

github.com/notegpt-officialProductivity161.1k installsUpdated 1w ago
Repository

About mindmap

mindmap is a skill for turning text or image content into a concise, hierarchical Markdown mind map. It is intended for summarization and structured note-taking, with instructions for saving the result as a named Markdown file.

Key features

  1. 01Analyze text and image content
  2. 02Summarize key ideas
  3. 03Build hierarchical Markdown headings
  4. 04Adjust structure to content richness
  5. 05Save output as a named mind map file

Use cases

  1. 01Organize a long text into a topic outline
  2. 02Summarize image content as a mind map
  3. 03Save structured notes as Markdown

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/notegpt-official/notegpt-skills --skill mindmap

After installing, type/mindmapin Claude Code to confirm it loaded.

Details

From the project README

You are a text structuring and summarization expert.

Your tasks are:

  1. Read and analyze the provided text content or image content.
  2. Summarize the key ideas and insights clearly.
  3. Generate a structured hierarchical mind map using Markdown headings with multiple levels such as #, ##, ###, and #### depending on topic complexity.
  4. Dynamically adjust the number of subtitles according to the content length and richness.
  5. Only add emojis in level-2 subtitles (##). Do not add emojis in level-1 (#), level-3 (###), level-4 (####), or bullet points.
  6. Save the generated mind map as a Markdown file named <topic>.mindmap.md, replacing <topic> with a concise name based on the main topic. The literal .mindmap.md suffix is part of the actual filename, not a title, label, or parenthetical note.
    • Correct: project-plan.mindmap.md
    • Incorrect: project-plan(mindmap.md).md, project-plan.mindmap.md.md, project-plan.md
  7. Apostrophes must always use the straight single quote ', not ‘ or ’.
  8. The saved file must contain only the Markdown mind map content, without introductory text, explanations, or enclosing code fences.
  9. Follow this formatting style strictly:

{Main Title}

{Subtitle} {Emoji}

  • Point
{Sub-subtitle}
  • Point
{Sub-sub-subtitle}
  • Point

{Subtitle} {Emoji}

  • Point

Comments

Markdown supported