Md writer
Write or edit knowledge-base Markdown with frontmatter, Mermaid diagrams, related-document links, and markdownlint validation. Use for guides, specs, ADRs, runbooks, and API documentation; not repository meta files such as README, CHANGELOG, CLAUDE.md, AGENTS.md, or SKILL.md.From its SKILL.md
npx -y skills add skrrt-sh/skills --skill md-writerAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- 2 stars2 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
SKILL.md
2.5 KB, as published. Nobody here has run it
Markdown Authoring
Write readable, lint-clean knowledge-base documents. Match an established local convention before applying this skill's defaults.
Document shape
Use this frontmatter for new documents, omitting fields whose values are unknown:
---
title: "Document title"
description: "One-sentence purpose"
created: "YYYY-MM-DD"
updated: "YYYY-MM-DD"
status: "draft"
---
Add author, version, tags, category, aliases, related, refs, or audience only when
the user, repository, or document supplies a real value. Never invent metadata. For new documents,
use today's date and version: "1.0.0" only when the repository versions individual documents.
Make the H1 match title. Follow it with a one-line blockquote summary. Add a table of contents
when it materially improves navigation, typically at five or more H2 sections.
Diagrams
Use Mermaid instead of ASCII art. Choose the diagram type that fits the relationship. Use <br/>
for line breaks in labels; a literal \n does not render as a break.
flowchart TD
A["First line<br/>second line"] --> B["Result"]
Formatting
- Wrap prose at 120 characters; exempt code blocks and tables.
- Avoid inline HTML outside Mermaid content.
- Use compact tables with single-space cell padding.
- Name files with lowercase hyphenated words.
- Give every fenced code block a language.
Related documents
For a document in an existing knowledge base, search nearby Markdown files and titles for genuine
topic, dependency, or parent/child overlap. Add deduplicated relative paths to this document's
related field. Edit existing documents to add backlinks only when the user asked for
bidirectional links; update only their related and updated fields.
Validate
From the target repository, run
${CLAUDE_SKILL_DIR}/scripts/validate-md.sh <file.md> on every changed in-scope Markdown
file. It may rewrite mechanical formatting; re-read a changed file before editing it again. Fix
reported judgment-based violations and repeat until clean.
Read references/validation.md only when validation is skipped, cannot start, or reports a violation.
What ships with it: 4 files
6.1 KB alongside SKILL.md, 1 of them executable
config/
evals/
- evals.json1.3 KB
scripts/
- validate-md.shruns4.1 KB
- package.json463 B