configs/claude-code/skills/md-syntax/SKILL.md
Markdown authoring guidelines for formatting, code blocks, and structure. Use when writing or editing markdown files.
npx skillsauth add jimweller/dotfiles md-syntaxInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Follow these rules when creating or editing markdown files.
bash, yaml, json, text, hcl, go, etc. Never use bare ```##, ###, etc.) not **Bold** on its own line# Title at the top# Title/md-lint to format and lint after writing the filePut a single blank line between markdown types/styles. Do not put multiple blank lines between markdown styles.
CORRECT
## Heading
paragraph
- list item one
- list item two
> block quote
````text
INCORRECT
```markdown
## Heading
paragraph
- list item one
- list item two
> block quote
```text
### Headings not bold
CORRECT
```markdown
### Heading
paragraph
```text
INCORRECT
```markdown
**heading incorrect bold**
paragraph
```text
### Code Blocks
Always specify language
CORRECT with language
```bash
#!/bin/bash
```text
INCORRECT without language
```text
#!/bin/bash
```text
### Trailing New Line
Always include a single trailing newline so the file ends in a blank line
INCORRECT no trailing newline
```markdown
The End.
```text
CORRECT trailing newline
```markdown
The End.
```text
````
testing
Search saved session transcripts for past decisions, actions, errors, and context that has left the current conversation window.
data-ai
Review a PRD for defects via Claude opus subagent.
development
--- name: md-style description: README style guide for concise, direct documentation. Use when writing or editing README files. ß--- <!-- markdownlint-disable-file MD041 --> # README Style Guide Write concise, direct README files for experienced engineers. ## Principles - **No fluff** - Skip tables of contents, verbose explanations, development history - **No roadmaps** - Document current state only, not plans or decisions. Readme is an engineering specification. Not a project plan or chan
testing
Use when a factual claim lacks evidence, when called out for fabricating facts, or when a statement needs verification before being presented as true. Takes a claim as argument.