Md Of Programer

Insert mind maps and architecture diagrams into Markdown documents. Triggered when the user says "draw a mind map", "draw an architecture diagram", "insert a...

Security Scan

The skill's requirements and runtime instructions match its stated purpose (producing mind‑maps and architecture diagrams) and request no surprising credentials or config access.

Purpose & Capability

Name/description (inserting mind maps and architecture diagrams into Markdown) align with required binaries (mddoc, d2) and the SKILL.md instructions which show writing source files, invoking mddoc/d2, and embedding PNGs.

Instruction Scope

SKILL.md stays on task: it instructs checking for binaries, writing source files to .mddoc/, running mddoc commands to produce PNGs, and embedding them. It does not request reading unrelated files, environment variables, or transmitting content to unexpected endpoints. The only external links are for d2 installation docs and an issues URL.

Install Mechanism

No formal install spec (instruction-only), which is low-risk. The doc suggests running package managers at runtime (npm install -g mddoc-cli, brew/winget or official d2 install). Installing npm global packages executes code from npm; this is typical for CLI tooling but worth noting because it requires network and will write to disk.

Credentials

The skill declares no required environment variables or credentials and the instructions do not access any secrets or unrelated config paths.

Persistence & Privilege

always is false and the skill does not request elevated or cross-skill configuration. It will create and write files under the workspace .mddoc/ directory as expected for its purpose.

Assessment

This skill appears coherent for creating diagrams in Markdown. Before using it: (1) be aware the instructions may run package manager commands (npm global install, brew/winget) which download and install third-party CLIs — review the mddoc-cli package source if you care about provenance; (2) the skill will create files under a .mddoc/ directory in your workspace — ensure that's acceptable and not a sensitive location; (3) prefer installing required tools yourself rather than letting an agent run installers automatically; and (4) if you need stricter controls, run the commands in an isolated environment (container/VM) rather than on a production machine.

When inserting diagrams into a Markdown document, always follow the rules below.

Dependency Check

Before doing anything, check that dependencies are installed:

which mddoc && which d2

If mddoc is not installed:

npm install -g mddoc-cli

If d2 is not installed:

• macOS: brew install d2
• Windows: winget install terrastruct.d2
• Linux / others: see https://d2lang.com/tour/install

Make sure both are available before continuing.

Rules

• All diagram source files and PNGs go only in the .mddoc/ directory (alongside the Markdown file)
• File names must use lowercase English + hyphens (auth-flow, module-overview) — no spaces or numbers
• Always write the source file first, then generate the PNG, then embed into Markdown — in that order
• Never write D2 or markmap code blocks directly in the Markdown body
• Create .mddoc/ if it does not exist

Mind Map (.mmd)

1. Write the source file → .mddoc/<name>.mmd in markmap markdown format:

# Root node

## Branch one
- Leaf node
- Leaf node

## Branch two
- Leaf node
  - Child leaf

2. Generate PNG:

mddoc mindmap .mddoc/<name>.mmd

3. Embed in Markdown:

![Mind map: <description>](.mddoc/<name>.png)
*Source: [<name>.mmd](.mddoc/<name>.mmd)*

Architecture Diagram (.d2)

1. Write the source file → .mddoc/<name>.d2 in D2 language:

direction: right

client: Client {shape: rectangle}
gateway: API Gateway {shape: rectangle}
db: Database {shape: cylinder}

client -> gateway -> db

2. Generate PNG:

mddoc arch .mddoc/<name>.d2

3. Embed in Markdown:

![Architecture: <description>](.mddoc/<name>.png)
*Source: [<name>.d2](.mddoc/<name>.d2)*

Regenerate All Diagrams

mddoc build

Feedback

Issues and suggestions → https://github.com/drunkpig/md-of-programer/issues