Skill Detail

Compile agent-ready documentation bundles with docmd

Use docmd when a project needs one Markdown documentation source to produce a site, search index, llms.txt, MCP endpoints, and structured knowledge bundles for agents.

Library & API ReferenceMulti-Framework
Library & API Reference Multi-Framework Security Reviewed
⭐ 2.5k GitHub stars ⬇ 36.6k/wk npm
COPY SKILL INSTRUCTIONS (OPTIONAL)
npx skills add agentskillexchange/skills --skill compile-agent-ready-documentation-bundles-with-docmd Copy
Uses the third-party skills CLI, not an ASE-owned installer. Check your agent’s compatibility. This copies instructions; complete the upstream tool setup below separately.
At a glance
Tools required
Node.js 18+, Markdown documentation source, optional MCP-capable coding agent or RAG pipeline consumer
Install & setup
Run npx @docmd/core dev in a documentation folder for local preview, or install @docmd/core globally and use docmd dev or docmd build. Review the generated site, search index, llms.txt, MCP endpoints, and knowledge bundle outputs before deployment.
Author
docmd
Publisher
Project
Last updated
Sep 21, 2026
Quick brief

docmd is a documentation compiler for human readers and machine consumers. Use it when an operator wants agents to maintain or publish documentation from Markdown while also generating AI-facing context such as llms.txt files, search indexes, MCP server endpoints, and OKF/RAG bundles. The workflow is to point docmd at a docs directory, run the local dev or build command, then review the generated static site and machine-readable outputs before publishing. The scope boundary is documentation build and agent-context packaging; it is not a generic static-site generator card or an SDK listing.

How it works

What this skill actually does

Inputs and prerequisites: Node.js 18+, Markdown documentation source, optional MCP-capable coding agent or RAG pipeline consumer.

Setup notes: Run npx @docmd/core dev in a documentation folder for local preview, or install @docmd/core globally and use docmd dev or docmd build. Review the generated site, search index, llms.txt, MCP endpoints, and knowledge bundle outputs before deployment.

Source and verification boundary: use https://docs.docmd.io as the canonical reference before running the workflow; keep commands, API calls, CLI usage, and generated outputs reviewable against that upstream source.

Framework fit: publish this as a Multi-Framework workflow only when the operator can invoke the documented toolchain directly, rather than treating the upstream project as a generic product listing.