Stats
Actions
Tags
From write-markdown
Applies Markdown style conventions when creating or editing Markdown files. Use when: (1) creating new Markdown files, (2) editing existing .md files, or (3) reviewing Markdown for style and formatting issues.
How this skill is triggered — by the user, by Claude, or both
Slash command
/write-markdown:write-markdownThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Apply the Markdown conventions from `./references/MARKDOWN.md` when creating or editing Markdown files. This guide targets GitHub Flavored Markdown (GFM) and aligns with markdownlint-cli2 rules.
Apply the Markdown conventions from ./references/MARKDOWN.md when creating or editing Markdown files. This guide targets GitHub Flavored Markdown (GFM) and aligns with markdownlint-cli2 rules.
These two issues cause the most lint failures. Check every Markdown file for them.
<!-- Correct: pipes aligned, cells padded -->
| Name | Type | Default |
| ------- | ------ | ------- |
| timeout | number | 30 |
| retries | number | 3 |
<!-- Wrong: ragged pipes, no padding -->
| Name | Type | Default |
| --- | --- | --- |
| timeout | number | 30 |
| retries | number | 3 |
Procedure: write all rows, find the longest content per column, pad every cell to that width, fill delimiter hyphens to match, then verify all pipes line up.
<!-- Correct -->
```bash
echo "hello"
```
<!-- Wrong: bare fence -->
```
echo "hello"
```
Use text when no syntax highlighting applies. Never leave the opening fence bare.
Read ./references/MARKDOWN.md for the complete guide. Summary:
# Title) per document (MD025)#) only, never Setext underlines (MD003)[text](url)[text][id]- for unordered (MD004); for ordered lists, use either 1. for every item or sequential numbering (1., 2., 3.), but be consistent within each list (MD029)text if none applies (MD040)<details>, <kbd>, <br>, <sub>, <sup>, etc.)After creating or editing Markdown files, run the project's lint-fix command to auto-correct table alignment, list numbering, and other formatting issues. This is a required final step, not optional.
Check package.json for project-specific scripts (e.g., yarn lint:fix, yarn lint:md:fix, npm run lint:fix). Also check Makefile targets and scripts in bin/. Run the linter in fix mode so it corrects what it can automatically.
If no project-specific lint script is available, use markdownlint-cli2 directly as a fallback.
Fetches up-to-date documentation from Context7 for libraries and frameworks like React, Next.js, Prisma. Use for setup questions, API references, and code examples.
Applies a firm's KYC/AML rules grid to parsed onboarding records: assigns risk rating, checks required documents, outputs rule outcomes with citations, and routes for escalation.
Generates daily or weekly digests of activity from connected sources (chat, email, docs, tasks, CRM), highlighting action items, decisions, mentions, and project updates.
npx claudepluginhub cboone/agent-harness-plugins --plugin write-markdown