yf-markdown-lint

Conventional GitHub-Flavored-Markdown linter. Checks that documents are valid GFM with well-formed, resolvable links — no Obsidian wiki-links (`[[...]]`) or embeds (`![[...]]`), valid relative links/anchors, and consistent tables.

At a glance

• Category: markdown
• Invocation: auto (fires from its description conditions when relevant work appears)
• Requires tools: uv
• Source: SKILL.md · README.md

When it fires

/yf-markdown-lint invoked; checking markdown validity; verifying a generated/edited `.md` file is clean GFM; after a generator skill writes markdown.

When to skip it

non-markdown files; Obsidian-specific wiki-link tooling (plain GFM is the convention this linter enforces).

Prerequisites

Mirrors SKILL.md frontmatter depends-on-tool: [uv]. No init step, no config, no companion rule.

Usage

User-invocable. Lint files or directories, optionally scoping the rule set:

/markdown-lint [<path> ...] [--rules ML001,...] [--format text|json]

uv run .claude/skills/markdown-lint/scripts/markdown_lint.py ${ARGS:-.}

Exit 1 on any violation. Rules ML001–ML007 are documented in SKILL.md; the lint-on-edit trigger (portable rule + the Claude-Code hook alternative) is in SKILL.md.

Phase model

None. This is a tool/reference skill with no phases or state transitions.