A modular skill set for AI agents to understand and work with docmd documentation projects.
SaferSkills independently audited docmd-skills (Agent Skill) and scored it 100/100 (green). The audit ran 55 deterministic rules across Security, Supply Chain, Maintenance, Transparency, and Community; it found 0 high-severity and 0 lower-severity findings. The full rule-by-rule trace and per-finding evidence are below. Free, methodology-open.
Findings & checks · 0 flagged
Every scanned point with the score it earned and what moved between them.
First recorded scan — no prior version to compare against.
The primary manifest — the file an agent reads to learn what this artifact does.
Use this skill when the user wants to build, configure, or operate a docmd documentation site. It is the default install and is loaded by npx docmd-skills <dir>.
Use it when the user wants to:
npx @docmd/core init)docmd.config.json (themes, navigation, layout, plugins, i18n, versions)docmd mcp server (search_docs, read_doc, validate_docs, get_llms_context)Do not use it for: writing or reviewing the prose inside pages (use docmd-writer), or hacking on the docmd framework itself (use docmd-dev).
SKILL.md (this file) by default whenever the user touches a docmd project.docmd/ monorepo (packages/core/src/, packages/api/src/, etc.), switch to docmd-dev instead.Each row is a reference file. Load it when you need it; the CLI column shows which docmd-skills subcommand also installs that exact file.
| Reference | CLI install subcommand | Use it for |
|---|---|---|
references/cli.md | docmd-skills (default) | All npx @docmd/core subcommands: init, dev, build, validate, live, deploy, mcp |
references/config.md | docmd-skills (default) | docmd.config.json schema, themes, navigation, layout, i18n, versions, plugins |
references/formatting.md | docmd-skills (default) | docmd-flavoured markdown: containers, tabs, cards, grids, steps, frontmatter, Mermaid |
references/plugins.md | docmd-skills (default) | Built-in and community plugins, plugins: config, plugin resolution order |
references/migration.md | docmd-skills (default) | Migrating from Docusaurus, MkDocs, VitePress to docmd |
references/deployment.md | docmd-skills (default) | Static hosting, SPA routing rewrites, docmd deploy, Docker, CI recipes |
references/validation.md | docmd-skills (default) | docmd validate, frontmatter rules, link checking, MCP validate_docs |
references/workspaces.md | docmd-skills (default) | Monorepo / multi-package doc workspaces, shared assets, cross-site nav |
references/api-user.md | docmd-skills (default) | Node API surface used by consumers of @docmd/core, @docmd/live, @docmd/ui |
npx @docmd/core init (or use pnpm create @docmd/core).docmd.config.json; cross-check against references/config.md.docs/; follow references/formatting.md and (for prose quality) docmd-writer.npx @docmd/core dev for live preview, then validate and build.references/config.md for the relevant section.references/plugins.md first — the feature may be a one-line plugin.references/validation.md for the gate command.references/deployment.md for the target host (Netlify / Vercel / Nginx / Caddy / Cloudflare Pages / GitHub Pages / Docker).docmd/ framework monorepo.~30 seconds. Free. No account. Every finding cites a rule and a line of evidence.