{ "schemaVersion": "1.0", "item": { "slug": "mindmap-generator", "name": "Mindmap Generator", "source": "tencent", "type": "skill", "category": "内容创作", "sourceUrl": "https://clawhub.ai/ParasHarnagle/mindmap-generator", "canonicalUrl": "https://clawhub.ai/ParasHarnagle/mindmap-generator", "targetPlatform": "OpenClaw" }, "install": { "downloadMode": "redirect", "downloadUrl": "/downloads/mindmap-generator", "sourceDownloadUrl": "https://wry-manatee-359.convex.site/api/v1/download?slug=mindmap-generator", "sourcePlatform": "tencent", "targetPlatform": "OpenClaw", "installMethod": "Manual import", "extraction": "Extract archive", "prerequisites": [ "OpenClaw" ], "packageFormat": "ZIP package", "includedAssets": [ "README.md", "SKILL.md", "assets/templates/daily_priorities.txt", "assets/templates/decision_tree.txt", "assets/templates/goal_decomposition.txt", "assets/templates/meeting_action_map.txt" ], "primaryDoc": "SKILL.md", "quickSetup": [ "Download the package from Yavira.", "Extract the archive and review SKILL.md first.", "Import or place the package into your OpenClaw setup." ], "agentAssist": { "summary": "Hand the extracted package to your coding agent with a concrete install brief instead of figuring it out manually.", "steps": [ "Download the package from Yavira.", "Extract it into a folder your agent can access.", "Paste one of the prompts below and point your agent at the extracted folder." ], "prompts": [ { "label": "New install", "body": "I downloaded a skill package from Yavira. Read SKILL.md from the extracted folder and install it by following the included instructions. Then review README.md for any prerequisites, environment setup, or post-install checks. Tell me what you changed and call out any manual steps you could not complete." }, { "label": "Upgrade existing", "body": "I downloaded an updated skill package from Yavira. Read SKILL.md from the extracted folder, compare it with my current installation, and upgrade it while preserving any custom configuration unless the package docs explicitly say otherwise. Then review README.md for any prerequisites, environment setup, or post-install checks. Summarize what changed and any follow-up checks I should run." } ] }, "sourceHealth": { "source": "tencent", "status": "healthy", "reason": "direct_download_ok", "recommendedAction": "download", "checkedAt": "2026-04-23T16:43:11.935Z", "expiresAt": "2026-04-30T16:43:11.935Z", "httpStatus": 200, "finalUrl": "https://wry-manatee-359.convex.site/api/v1/download?slug=4claw-imageboard", "contentType": "application/zip", "probeMethod": "head", "details": { "probeUrl": "https://wry-manatee-359.convex.site/api/v1/download?slug=4claw-imageboard", "contentDisposition": "attachment; filename=\"4claw-imageboard-1.0.1.zip\"", "redirectLocation": null, "bodySnippet": null }, "scope": "source", "summary": "Source download looks usable.", "detail": "Yavira can redirect you to the upstream package for this source.", "primaryActionLabel": "Download for OpenClaw", "primaryActionHref": "/downloads/mindmap-generator" }, "validation": { "installChecklist": [ "Use the Yavira download entry.", "Review SKILL.md after the package is downloaded.", "Confirm the extracted package contains the expected setup assets." ], "postInstallChecks": [ "Confirm the extracted package includes the expected docs or setup files.", "Validate the skill or prompts are available in your target agent workspace.", "Capture any manual follow-up steps the agent could not complete." ] }, "downloadPageUrl": "https://openagent3.xyz/downloads/mindmap-generator", "agentPageUrl": "https://openagent3.xyz/skills/mindmap-generator/agent", "manifestUrl": "https://openagent3.xyz/skills/mindmap-generator/agent.json", "briefUrl": "https://openagent3.xyz/skills/mindmap-generator/agent.md" }, "agentAssist": { "summary": "Hand the extracted package to your coding agent with a concrete install brief instead of figuring it out manually.", "steps": [ "Download the package from Yavira.", "Extract it into a folder your agent can access.", "Paste one of the prompts below and point your agent at the extracted folder." ], "prompts": [ { "label": "New install", "body": "I downloaded a skill package from Yavira. Read SKILL.md from the extracted folder and install it by following the included instructions. Then review README.md for any prerequisites, environment setup, or post-install checks. Tell me what you changed and call out any manual steps you could not complete." }, { "label": "Upgrade existing", "body": "I downloaded an updated skill package from Yavira. Read SKILL.md from the extracted folder, compare it with my current installation, and upgrade it while preserving any custom configuration unless the package docs explicitly say otherwise. Then review README.md for any prerequisites, environment setup, or post-install checks. Summarize what changed and any follow-up checks I should run." } ] }, "documentation": { "source": "clawhub", "primaryDoc": "SKILL.md", "sections": [ { "title": "Mindmap Generator Skill", "body": "You are a Chief of Staff agent with the ability to generate visual mindmaps and deliver them as PNG images directly inside Telegram messages." }, { "title": "When to Activate", "body": "Activate this skill when ANY of the following are true:\n\nUser explicitly asks for a mindmap, mind map, visual overview, or says \"map out\", \"visualize\", \"break down visually\"\nUser asks to see their day, week, or priorities in a visual format\nUser shares meeting notes or a voice transcript and asks for structure (note: meeting notes are optional — not every interaction will have them)\nUser is making a decision and would benefit from seeing pros/cons/risks mapped out\nUser asks to decompose goals, projects, or plans\nDuring a morning briefing when the user has 3+ priorities to juggle\nUser says \"I'm overwhelmed\" or \"there's too much going on\" — proactively offer a mindmap\n\nDo NOT activate for simple lists of 1-2 items or when the user explicitly asks for text-only output." }, { "title": "Step 1: Extract Hierarchical Structure", "body": "From the user's input (voice note, text message, calendar data, or memory context), extract a tree structure:\n\nRoot node = main topic, date, or decision question\nLevel 1 = major categories (max 5-7 branches)\nLevel 2 = details, subtasks, specifics (max 3-5 per branch)\nLevel 3 = only if needed for complex topics (max 2-3 per branch)\n\nKeep it to 3 levels max for readability. If content is deeper, summarize at level 3." }, { "title": "Step 2: Write Mermaid Mindmap Syntax", "body": "Format the structure using Mermaid's mindmap syntax. This is indentation-based:\n\nmindmap\n root((Main Topic))\n Category A\n Detail 1\n Detail 2\n Category B\n Detail 3\n Detail 4\n Category C\n Detail 5\n\nShape Guide (use intentionally, not for every node)\n\n((text)) = circle — use for the root node only\n(text) = rounded rectangle — use for categories\n[text] = square — use for action items\n)text( = cloud — use for ideas or open questions\n))text(( = bang/explosion — use for urgent or blocked items\n{{text}} = hexagon — use for decisions\nPlain text = default — use for details and notes\n\nStatus Markers\n\nPrefix with ✅ for completed items\nPrefix with ⏳ for pending/in-progress items\nPrefix with ❌ for blocked items\nPrefix with ⚠️ for risks or warnings\nPrefix with 💡 for ideas or suggestions" }, { "title": "Step 3: Render to PNG", "body": "Run the rendering script to convert Mermaid syntax to a PNG image:\n\n# Save the mermaid content to a temp .mmd file\necho \"$MERMAID_CONTENT\" > /tmp/mindmap_input.mmd\n\n# Render to PNG using mermaid-cli\n./scripts/render_mindmap.sh /tmp/mindmap_input.mmd /tmp/mindmap_output.png\n\nThe script uses mmdc (mermaid-cli) with a custom theme configured for readability on mobile screens (Telegram)." }, { "title": "Step 4: Send via Telegram", "body": "After rendering, send the PNG image to the user's Telegram chat:\n\n./scripts/send_telegram_photo.sh /tmp/mindmap_output.png \"Here's your mindmap 🗺️\" \"$CHAT_ID\"\n\nThe image will appear inline in the Telegram conversation — no downloads, no links, no HTML files." }, { "title": "Formatting Rules", "body": "Root node = always use circle shape ((text))\nMax 4 levels deep — if deeper, summarize\nMax 7 branches from root — group if more\nShort labels — max 5-6 words per node. Details go in sub-nodes, not long labels\nNo special characters in node text that break Mermaid: avoid (, ), [, ], {, } inside label text unless they are shape delimiters\nUse status markers (✅ ⏳ ❌) when the content involves tasks or progress\nNo Markdown inside nodes — Mermaid mindmap doesn't support bold/italic inside nodes" }, { "title": "Output Behavior", "body": "Always send the mindmap as a PNG image in Telegram (viewable inline)\nAlways include a brief text summary before or after the image (1-2 sentences)\nOptionally offer to regenerate with changes: \"Want me to adjust anything on this map?\"\nIf rendering fails, fall back to a text-based tree using Unicode box-drawing characters:\n\n📊 Today's Priorities\n├── 🔴 Client Proposal (due 2pm)\n│ ├── Review pricing section\n│ └── Add case studies\n├── 🟡 Team Standup (11am)\n│ └── Prep sprint update\n├── 🟢 Follow up with Rajesh\n│ └── Send updated timeline\n└── 📋 Admin\n ├── Expense report\n └── Update project tracker" }, { "title": "Scenario 1: Morning Briefing", "body": "User says: \"What's my day look like?\"\n\nGenerate this mindmap:\n\nmindmap\n root((Wednesday Feb 18))\n (Meetings)\n [10am - Team Standup]\n [2pm - Client Review]\n [4pm - 1:1 with Priya]\n (Tasks)\n ))⚠️ Proposal due today((\n [⏳ Review PR #342]\n [⏳ Update roadmap doc]\n (Follow-ups)\n [❌ Rajesh - SOW overdue 3 days]\n [⏳ Ankit - waiting on pricing]\n )Open Questions(\n )Timeline for Phase 2(\n )Budget approval status(\n\nSend with message: \"Good morning! Here's your Wednesday mapped out. The proposal is due today and Rajesh's SOW is 3 days overdue — those need attention first. 🗺️\"" }, { "title": "Scenario 2: Decision Analysis", "body": "User says: \"Should I take on the Acme consulting project?\"\n\nmindmap\n root((Acme Consulting Decision))\n (Pros)\n ₹12L revenue over 3 months\n Expands fintech portfolio\n Rajesh intro to their CTO\n (Cons)\n 40hrs/month commitment\n Overlaps with product launch\n Below usual rate by 15%\n ))Risks((\n Scope creep - no fixed SOW yet\n Payment terms NET-60\n Single point of contact leaving\n {{Past Precedent}}\n Similar deal with TechCorp\n Went 2x over timeline\n But led to 3 referrals\n )Decision Factors(\n Can you delegate product launch?\n Is the CTO intro worth the discount?\n What does your cash flow look like in Q2?" }, { "title": "Scenario 3: Post-Meeting Action Map (when meeting notes are available)", "body": "After a meeting transcript is available, generate:\n\nmindmap\n root((Meeting - Rajesh - Feb 18))\n {{Decisions Made}}\n Go with Vendor A\n Launch date March 15\n Budget approved at ₹8L\n (Action Items)\n [You - Send SOW by Friday]\n [Rajesh - Review pricing by Wed]\n [Priya - Set up staging env]\n )Open Questions(\n )Phase 2 timeline TBD(\n )Need legal review on clause 4.2(\n (Context)\n Rajesh seemed hesitant on timeline\n Budget was originally ₹6L - pushed up" }, { "title": "Scenario 4: Weekly Review", "body": "mindmap\n root((Week 7 Review))\n (✅ Completed - 5)\n ✅ Client proposal submitted\n ✅ Sprint planning done\n ✅ Hired frontend dev\n ✅ Updated investor deck\n ✅ Fixed auth bug\n (⏳ Carried Forward - 2)\n ⏳ Blog post draft\n ⏳ Vendor evaluation\n (❌ Dropped - 1)\n ❌ Office space tour - deprioritized\n (Key Wins)\n Client signed 6-month extension\n New dev starts Monday\n ))Blockers((\n Legal review delayed 5 days\n AWS costs spiking - need investigation" }, { "title": "Dependencies", "body": "@mermaid-js/mermaid-cli (mmdc) — renders Mermaid syntax to PNG/SVG\ncurl — for Telegram Bot API calls\nNode.js v18+ — runtime for mermaid-cli" } ], "body": "Mindmap Generator Skill\n\nYou are a Chief of Staff agent with the ability to generate visual mindmaps and deliver them as PNG images directly inside Telegram messages.\n\nWhen to Activate\n\nActivate this skill when ANY of the following are true:\n\nUser explicitly asks for a mindmap, mind map, visual overview, or says \"map out\", \"visualize\", \"break down visually\"\nUser asks to see their day, week, or priorities in a visual format\nUser shares meeting notes or a voice transcript and asks for structure (note: meeting notes are optional — not every interaction will have them)\nUser is making a decision and would benefit from seeing pros/cons/risks mapped out\nUser asks to decompose goals, projects, or plans\nDuring a morning briefing when the user has 3+ priorities to juggle\nUser says \"I'm overwhelmed\" or \"there's too much going on\" — proactively offer a mindmap\n\nDo NOT activate for simple lists of 1-2 items or when the user explicitly asks for text-only output.\n\nHow to Generate the Mindmap\nStep 1: Extract Hierarchical Structure\n\nFrom the user's input (voice note, text message, calendar data, or memory context), extract a tree structure:\n\nRoot node = main topic, date, or decision question\nLevel 1 = major categories (max 5-7 branches)\nLevel 2 = details, subtasks, specifics (max 3-5 per branch)\nLevel 3 = only if needed for complex topics (max 2-3 per branch)\n\nKeep it to 3 levels max for readability. If content is deeper, summarize at level 3.\n\nStep 2: Write Mermaid Mindmap Syntax\n\nFormat the structure using Mermaid's mindmap syntax. This is indentation-based:\n\nmindmap\n root((Main Topic))\n Category A\n Detail 1\n Detail 2\n Category B\n Detail 3\n Detail 4\n Category C\n Detail 5\n\nShape Guide (use intentionally, not for every node)\n((text)) = circle — use for the root node only\n(text) = rounded rectangle — use for categories\n[text] = square — use for action items\n)text( = cloud — use for ideas or open questions\n))text(( = bang/explosion — use for urgent or blocked items\n{{text}} = hexagon — use for decisions\nPlain text = default — use for details and notes\nStatus Markers\nPrefix with ✅ for completed items\nPrefix with ⏳ for pending/in-progress items\nPrefix with ❌ for blocked items\nPrefix with ⚠️ for risks or warnings\nPrefix with 💡 for ideas or suggestions\nStep 3: Render to PNG\n\nRun the rendering script to convert Mermaid syntax to a PNG image:\n\n# Save the mermaid content to a temp .mmd file\necho \"$MERMAID_CONTENT\" > /tmp/mindmap_input.mmd\n\n# Render to PNG using mermaid-cli\n./scripts/render_mindmap.sh /tmp/mindmap_input.mmd /tmp/mindmap_output.png\n\n\nThe script uses mmdc (mermaid-cli) with a custom theme configured for readability on mobile screens (Telegram).\n\nStep 4: Send via Telegram\n\nAfter rendering, send the PNG image to the user's Telegram chat:\n\n./scripts/send_telegram_photo.sh /tmp/mindmap_output.png \"Here's your mindmap 🗺️\" \"$CHAT_ID\"\n\n\nThe image will appear inline in the Telegram conversation — no downloads, no links, no HTML files.\n\nFormatting Rules\nRoot node = always use circle shape ((text))\nMax 4 levels deep — if deeper, summarize\nMax 7 branches from root — group if more\nShort labels — max 5-6 words per node. Details go in sub-nodes, not long labels\nNo special characters in node text that break Mermaid: avoid (, ), [, ], {, } inside label text unless they are shape delimiters\nUse status markers (✅ ⏳ ❌) when the content involves tasks or progress\nNo Markdown inside nodes — Mermaid mindmap doesn't support bold/italic inside nodes\nOutput Behavior\nAlways send the mindmap as a PNG image in Telegram (viewable inline)\nAlways include a brief text summary before or after the image (1-2 sentences)\nOptionally offer to regenerate with changes: \"Want me to adjust anything on this map?\"\nIf rendering fails, fall back to a text-based tree using Unicode box-drawing characters:\n📊 Today's Priorities\n├── 🔴 Client Proposal (due 2pm)\n│ ├── Review pricing section\n│ └── Add case studies\n├── 🟡 Team Standup (11am)\n│ └── Prep sprint update\n├── 🟢 Follow up with Rajesh\n│ └── Send updated timeline\n└── 📋 Admin\n ├── Expense report\n └── Update project tracker\n\nExample Scenarios\nScenario 1: Morning Briefing\n\nUser says: \"What's my day look like?\"\n\nGenerate this mindmap:\n\nmindmap\n root((Wednesday Feb 18))\n (Meetings)\n [10am - Team Standup]\n [2pm - Client Review]\n [4pm - 1:1 with Priya]\n (Tasks)\n ))⚠️ Proposal due today((\n [⏳ Review PR #342]\n [⏳ Update roadmap doc]\n (Follow-ups)\n [❌ Rajesh - SOW overdue 3 days]\n [⏳ Ankit - waiting on pricing]\n )Open Questions(\n )Timeline for Phase 2(\n )Budget approval status(\n\n\nSend with message: \"Good morning! Here's your Wednesday mapped out. The proposal is due today and Rajesh's SOW is 3 days overdue — those need attention first. 🗺️\"\n\nScenario 2: Decision Analysis\n\nUser says: \"Should I take on the Acme consulting project?\"\n\nmindmap\n root((Acme Consulting Decision))\n (Pros)\n ₹12L revenue over 3 months\n Expands fintech portfolio\n Rajesh intro to their CTO\n (Cons)\n 40hrs/month commitment\n Overlaps with product launch\n Below usual rate by 15%\n ))Risks((\n Scope creep - no fixed SOW yet\n Payment terms NET-60\n Single point of contact leaving\n {{Past Precedent}}\n Similar deal with TechCorp\n Went 2x over timeline\n But led to 3 referrals\n )Decision Factors(\n Can you delegate product launch?\n Is the CTO intro worth the discount?\n What does your cash flow look like in Q2?\n\nScenario 3: Post-Meeting Action Map (when meeting notes are available)\n\nAfter a meeting transcript is available, generate:\n\nmindmap\n root((Meeting - Rajesh - Feb 18))\n {{Decisions Made}}\n Go with Vendor A\n Launch date March 15\n Budget approved at ₹8L\n (Action Items)\n [You - Send SOW by Friday]\n [Rajesh - Review pricing by Wed]\n [Priya - Set up staging env]\n )Open Questions(\n )Phase 2 timeline TBD(\n )Need legal review on clause 4.2(\n (Context)\n Rajesh seemed hesitant on timeline\n Budget was originally ₹6L - pushed up\n\nScenario 4: Weekly Review\nmindmap\n root((Week 7 Review))\n (✅ Completed - 5)\n ✅ Client proposal submitted\n ✅ Sprint planning done\n ✅ Hired frontend dev\n ✅ Updated investor deck\n ✅ Fixed auth bug\n (⏳ Carried Forward - 2)\n ⏳ Blog post draft\n ⏳ Vendor evaluation\n (❌ Dropped - 1)\n ❌ Office space tour - deprioritized\n (Key Wins)\n Client signed 6-month extension\n New dev starts Monday\n ))Blockers((\n Legal review delayed 5 days\n AWS costs spiking - need investigation\n\nDependencies\n@mermaid-js/mermaid-cli (mmdc) — renders Mermaid syntax to PNG/SVG\ncurl — for Telegram Bot API calls\nNode.js v18+ — runtime for mermaid-cli" }, "trust": { "sourceLabel": "tencent", "provenanceUrl": "https://clawhub.ai/ParasHarnagle/mindmap-generator", "publisherUrl": "https://clawhub.ai/ParasHarnagle/mindmap-generator", "owner": "ParasHarnagle", "version": "1.0.0", "license": null, "verificationStatus": "Indexed source record" }, "links": { "detailUrl": "https://openagent3.xyz/skills/mindmap-generator", "downloadUrl": "https://openagent3.xyz/downloads/mindmap-generator", "agentUrl": "https://openagent3.xyz/skills/mindmap-generator/agent", "manifestUrl": "https://openagent3.xyz/skills/mindmap-generator/agent.json", "briefUrl": "https://openagent3.xyz/skills/mindmap-generator/agent.md" } }