Install
$ agentstack add skill-guoliang1114-boop-ariaai-mindmap ✓ scanned · ✓ verified, works with Claude Code, Cursor, and more.
Security review
✓ PassedNo issues found. Passed automated security review. · v0.1.0 How review works →
- ✓ Prompt-injection patterns
- ✓ Secret / credential exfiltration
- ✓ Dangerous shell & filesystem operations
- ✓ Untrusted network calls
- ✓ Known-malicious package signatures
What it can access
- ✓ Network access No
- ✓ Filesystem access No
- ✓ Shell / process execution No
- ✓ Environment & secrets No
- ✓ Dynamic code execution No
From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.
Verified badge
Passed review? Show it. Paste this badge into your README, it links to the public security report.
Reliability & compatibility
Declared compatibility
Compatibility is declared by the source manifest. End-to-end runtime verification is coming, see below.
We're building live execution health for every listing: tool-call success rate, median latency, uptime, and last-checked timestamps, measured, not self-reported. It isn't live yet, so we don't show numbers we can't stand behind.
How agent discovery & health will work →About
Mind Map Diagram Generator
Quick Start: Start with @startmindmap -> define root and branches with * or +/- markers -> optionally set branch side, direction, and styles -> wrap in `plantuml fence.
> ⚠️ IMPORTANT: Always use `plantuml or `puml code fence. NEVER use `text — it will NOT render as a diagram.
Critical Rules
- Every diagram starts with
@startmindmapand ends with@endmindmap - Each hierarchy level is represented by repeating markers:
*style:*(root),**(level 1),***(level 2)+/-style:+grows left branch,-grows right branch- Keep one marker style consistent in the same local branch (do not randomly mix indentation styles)
- Use
left sideto switch subsequent branches to the left side of the root - Use direction keywords when needed:
top to bottom directionright to left direction- Multi-line node content must use block syntax:
**:Line 1\nLine 2;- For quick color coding, use inline node color:
*[#Orange] Root**[#lightgreen] Child- For reusable themes, define `
and apply stereotypes like>` - Rich text/Creole and icon syntax are supported inside node text (see examples)
Node Syntax Cheat Sheet
| Pattern | Meaning | Example | |--------|---------|---------| | * Root | Root node with star syntax | * Product Strategy | | ** Child | First-level child | ** Goals | | *** Grandchild | Deeper hierarchy | *** KPI | | + Root | Root node with +/- syntax | + Architecture | | ++ Left branch | Branch expanding on one side | ++ Services | | -- Right branch | Branch expanding on opposite side | -- Risks | | ***_ Boxless | Boxless/minimal child node | ***_ Notes | | # Root | Alternative root marker style | # Topic | | **:...; | Multi-line block node | **:Item A\nItem B; |
Branch Side and Direction
| Control | Syntax | Use Case | |--------|--------|---------| | Left-side split | left side | Split map into left/right groups from root | | Top-to-bottom | top to bottom direction | Tree-like vertical hierarchy | | Right-to-left | right to left direction | RTL reading flow or mirrored layouts |
Styling Options
| Method | Syntax | Best For | |-------|--------|----------| | Inline node color | **[#FFBBCC] Idea | Fast per-node emphasis | | Reusable class style | ... .green { ... } + > | Consistent visual themes | | Depth-based style | :depth(1) { ... } | Global formatting by hierarchy depth | | Node/arrow global style | node { ... } / arrow { ... } | Unified typography and connectors |
Recommended Color Palettes
Pick a palette that matches the map's purpose. Use inline [#hex] for quick coloring or define `` classes for reuse.
General-Purpose (Pastel)
| Role | Hex | Preview | Usage | |------|-----|---------|-------| | Root | #2196F3 | 🔵 | Central topic | | Branch A | #A5D6A7 | 🟢 | Category / group 1 | | Branch B | #90CAF9 | 🔵 | Category / group 2 | | Branch C | #CE93D8 | 🟣 | Category / group 3 | | Branch D | #FFE082 | 🟡 | Category / group 4 | | Leaf | #E0E0E0 | ⚪ | Detail nodes |
Status / RAG
| Status | Hex | Usage | |--------|-----|-------| | Done / OK | #C8E6C9 | Completed, healthy | | In Progress | #FFF9C4 | Active, warning | | Blocked / Risk | #FFCDD2 | Issue, danger | | Not Started | #E0E0E0 | Pending, neutral |
Warm Corporate
| Role | Hex | |------|-----| | Root | #1565C0 | | Level 1 | #FFB74D | | Level 2 | #4DB6AC | | Level 3 | #E0E0E0 |
Cool Tech
| Role | Hex | |------|-----| | Root | #263238 | | Level 1 | #00BCD4 | | Level 2 | #80DEEA | | Level 3 | #B2EBF2 |
Earth Tone
| Role | Hex | |------|-----| | Root | #5D4037 | | Level 1 | #A1887F | | Level 2 | #C8E6C9 | | Level 3 | #FFF9C4 |
> Tip: Avoid pure saturated colors (#FF0000, #00FF00) — they reduce readability. Prefer soft/muted tones for backgrounds and reserve bold colors for the root only.
Mind Map Patterns
| Pattern | Purpose | Example | |--------|---------|---------| | Basic Hierarchy | Topic decomposition and study outlines | [basic-hierarchy.md](examples/basic-hierarchy.md) | | Bilateral Layout | Pros/cons, options vs risks, two-side analysis | [bilateral-layout.md](examples/bilateral-layout.md) | | Boxless Branches | Lightweight secondary nodes and annotations | [boxless-branches.md](examples/boxless-branches.md) | | Styled Theme | Color-coded branches and reusable classes | [styled-theme.md](examples/styled-theme.md) | | Direction Control | Vertical or RTL reading direction | [direction-control.md](examples/direction-control.md) | | Rich Text Content | Detailed notes with icons and formatting | [rich-text-content.md](examples/rich-text-content.md) | | Project Planning | Work breakdown and action map | [project-planning.md](examples/project-planning.md) |
Quick Example
@startmindmap
* Product Launch
** Goals
*** Revenue
*** User Growth
left side
** Risks
*** Timeline Slip
*** Budget Overrun
right to left direction
** Channels
*** Content
*** Ads
@endmindmap
Common Pitfalls
| Issue | Solution | |------|----------| | Diagram not rendered | Use `plantuml fence + @startmindmap ... @endmindmap | | Branch depth looks wrong | Check marker count (*, **, ***) and indentation consistency | | Multi-line text breaks parser | Use : ... ; block syntax, ensure trailing ; exists | | Colors not applied | Verify hex format (#RRGGBB) or stereotype class names | | Layout direction unexpected | Add explicit top to bottom direction or right to left direction |
Capability Upgrade
Mode Selection
- Quick: 把主题拆成 2-3 层思维导图。
- Standard: 形成结构清晰、左右平衡、带颜色层级的 PlantUML mindmap。
- Deep: 结合项目目标、知识库内容、会议记录或战略框架,生成可用于研讨、培训或汇报的结构化导图。
Structure Logic
先确定导图目的:发散、归纳、决策、学习、路线图或问题拆解。目的不同,分支应分别按 MECE、时间、责任、因果或优先级组织。
Quality Gates
- [ ] 一级分支 3-7 个,避免过宽或过窄。
- [ ] 同层节点使用同一分类口径。
- [ ] 分支深度不超过可读范围。
- [ ] 颜色用于表达语义,不只是装饰。
- [ ] 输出包含 PlantUML 和必要的结构解释。
Deliverable Catalog
| Deliverable | When to use | Minimum content | Format | |-------------|-------------|-----------------|--------| | Mind map | 主题拆解 | 中心主题、一级分支、二级分支和结构说明 | PlantUML / Markdown | | Issue tree | 咨询问题拆解 | 核心问题、MECE 分支、假设和证据需求 | PlantUML / PPT | | Knowledge map | 知识整理 | 主题、概念、关系、引用和后续阅读 | PlantUML / Markdown | | Decision tree | 路径选择 | 判断条件、分支、结果、风险和建议 | PlantUML | | Workshop map | 研讨会输出 | 议题、观点、投票、行动项和责任人 | PlantUML / Markdown | | Mindmap QA checklist | 发布前 | 分支数量、层级、一致性、方向和颜色语义 | Checklist |
Source & license
This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.
- Author: guoliang1114-boop
- Source: guoliang1114-boop/AriaAI
- License: MIT
- Homepage: https://aria.d2cgo.co/
Install and usage instructions live in the source repository linked above.
Reviews
No reviews yet, be the first.
Write a review
Versions
- v0.1.0 Imported from the upstream source.