XMind Generator

Generate XMind mind map files (.xmind) from Markdown outlines or plain text descriptions. Use when a user asks to create a mind map, visualize a structure, o...

Security Scan

The skill is internally consistent: it is a Node-based XMind file generator that requires installing the xmind npm package and writes .xmind files to disk — nothing in the code or instructions appears to ask for unrelated credentials or hidden network endpoints.

Purpose & Capability

Name/description (generate .xmind from Markdown/plain text) match the provided script and package.json dependency on the 'xmind' npm package. Requiring Node and an npm install of the xmind package is proportionate to the stated purpose.

Instruction Scope

SKILL.md instructs running the script from the skill directory and defaults output to a file path; the script accepts --input, --text, or stdin and writes the output file to any path the caller provides. This is expected for a file generator, but be aware it will read arbitrary input files you point it at and will write to arbitrary filesystem paths (respecting the process user permissions). There is a small documentation inconsistency: SKILL.md says 'Default output location: the OpenClaw workspace directory' while also instructing 'Always run from the skill directory' — the script uses the current working directory, so the actual default depends on where you run it.

Install Mechanism

No automated install spec in registry; SKILL.md requires running 'npm install' which will fetch 'xmind' and its transitive dependencies from the public npm registry per package-lock.json. This is a normal but moderate-risk install vector (npm packages are third-party code). There are no downloads from arbitrary URLs or extract operations beyond standard npm installs.

Credentials

The skill declares no required environment variables, credentials, or config paths, and the code does not access env vars. The script only reads input files/stdin and writes an output .xmind file; requested access is proportional to the functionality.

Persistence & Privilege

always is false and the skill does not request persistent elevated privileges or modify other skills or system-wide agent settings. It only writes files that the running user permits.

Assessment

This skill looks like a straightforward Node script that creates .xmind files. Before installing/running: (1) run npm install in a sandboxed or controlled environment (not as root) and review package-lock.json or the 'xmind' package source if you want to audit third-party code; (2) when running, explicitly specify safe input and output paths so the script doesn't read or overwrite files you care about; (3) on Windows, piping from /dev/stdin may not work — prefer --input or --text; (4) if you need stronger assurance, inspect the 'xmind' npm package and transitive dependencies for unexpected network calls or filesystem access.

Generate .xmind files from Markdown outlines or plain text using the XMind SDK.

Script

scripts/generate_xmind.js — main generator. Requires Node.js and the xmind npm package.

Installation

Install dependencies before first use:

cd <skill_dir>
npm install

Usage

# From Markdown outline file
node scripts/generate_xmind.js --input outline.md --output /path/to/output.xmind

# From inline text (use \n for newlines)
node scripts/generate_xmind.js --text "# Root\n- Branch 1\n  - Leaf\n- Branch 2" --output output.xmind

# From stdin
echo "..." | node scripts/generate_xmind.js --output output.xmind

Always run from the skill directory:

cd <skill_dir>

Default output location: the OpenClaw workspace directory.

Input Format

Both formats are supported:

Markdown outline:

# Root Topic
- Main Branch 1
  - Sub topic 1
  - Sub topic 2
- Main Branch 2
  - Sub topic 3
    - Leaf node

Plain text / free-form description: When user provides a description instead of an outline, first convert it to Markdown outline structure, then pass to the script.

Workflow

1. If user provides a Markdown outline → pass directly to script via --text or --input
2. If user provides a plain text description → convert to Markdown outline first, then generate
3. Output file goes to workspace directory unless user specifies otherwise
4. Confirm the output path to the user after generation