From mdmind
Inspect, validate, query, audit, deep-link, list external refs, or export mdmind Markdown outline and mind map files with the mdm CLI. Use for existing maps, structured notes, knowledge maps, tags, metadata, ids, relations, external Markdown refs, subtree inspection, filtered search, plain/json output, or exports to JSON, Mermaid, and OPML. Do not use this skill for messy source ingestion; agents should read PDFs, websites, and prose-heavy HTML themselves, author the mdmind map with map-authoring guidance, then validate it.
How this skill is triggered — by the user, by Claude, or both
Slash command
/mdmind:mdm-cli-inspectionThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Use `mdm` as the read, query, validate, and export surface for map files.
Use mdm as the read, query, validate, and export surface for map files.
#tags, or @key:value filters.mdm import; keep this skill focused on inspection, validation, querying, and export.If the task is mainly about creating or reshaping map content, use mdmind-map-authoring instead.
mdm commands --json when you need to discover command safety,
interactivity, arguments, flags, output modes, and examples locally.--plain for grep-friendly inspection and quick human scanning.--json when another tool needs the mdm response envelope with
ok, command, format, data, summary, error, and next_actions.mdm export --format json when another tool needs raw map document data.map.md#product/tasks when the user cares about one branch.--query on export when the user wants a filtered machine-readable subset.mdm refs <file> when the question is about attached external files, URLs, or image refs.mdm is available before relying on CLI output.Read only what you need:
references/command-patterns.md when choosing the right mdm subcommand.references/query-and-export.md when query syntax, deep links, or export scope matter.This skill expects mdm on PATH.
If availability is unknown, run:
command -v mdm
If mdm is missing, do not invent command results. Tell the user to install mdmind first or use the map-authoring skill for syntax-only guidance.
mdm validate <file> for parser, id, and relation checks.mdm view <file> for a readable tree.mdm find <file> "<query>" for text, tags, and metadata search.mdm kv <file> --keys key1,key2 to audit metadata fields.mdm tags <file> to summarize vocabulary.mdm links <file> to list deep-linkable ids.mdm refs <file> to list external Markdown refs attached to nodes.mdm relations <file> or mdm relations <file>#id to inspect graph edges.mdm export <file> --format json|mermaid|opml for downstream tools.mdm commands --json to discover the current command catalog.For task-heavy maps, start with active and blocked work before broader summaries:
mdm find TODO.md "#todo @status:active" --plain
mdm find TODO.md "task:open" --plain
mdm find TODO.md "task:done" --plain
mdm find TODO.md "@status:blocked" --plain
mdm kv TODO.md --keys status,owner,priority,area --plain
mdm view TODO.md#todo/focus
mdm validate TODO.md
Use find for the working set, kv for ownership/status audits, and view with a deep link when the user needs one branch in context. After agent edits, run validate before summarizing the handoff.
When inspecting task files, expect explicit checkbox markers to round-trip in the raw map, task-aware filters like task:open to find checkbox/tag/status task conventions, and derived parent rollups to appear in rendered views.
mdm command that answers that need.--json for an mdm response envelope, or
mdm export --format json for raw document JSON.mdm validate before drawing conclusions.Before handing back a result:
refs, distinguish external Markdown refs from internal ids or [[...]] relations.relations, be explicit whether the result is whole-map outgoing relations or node-focused incoming plus outgoing relations.find is for matching content; links is for discovering stable ids.refs is for Markdown links/images that point outside the map; links is for map node ids.relations file.md and relations file.md#id answer different questions.export --query can return an empty tree if the filter matches nothing.--json returns an envelope. The command-specific payload is
under data; do not expect top-level arrays from find --json, refs --json,
or validate --json.mdm export --format json intentionally remains raw document JSON instead of
an envelope.--plain and --json are mutually exclusive on commands that support both.validate is addressed.--json for response metadata
and mdm export --format json for raw map data.Provides CDSS development patterns for drug interaction checking, dose validation, clinical scoring (NEWS2, qSOFA), and alert classification integrated into EMR workflows.
npx claudepluginhub dudash/mdmind --plugin mdmind