Help us improve
Share bugs, ideas, or general feedback.
From markymark
Validate markdown quality in the current workspace using markymark diagnostics
npx claudepluginhub sethyanow/markymark --plugin markymarkHow this skill is triggered — by the user, by Claude, or both
Slash command
/markymark:markdown-checkThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Validate markdown files in your workspace for common issues using markymark's built-in diagnostics engine.
Validates Markdown documentation links, detecting broken relative links, missing anchor targets, malformed URLs, and orphaned documentation files. Use before releases or doc updates.
Guides markdown linting with markdownlint-cli2: run checks, fix MD0XX errors, configure .markdownlint-cli2.jsonc rules/ignores, set up VS Code extension and GitHub Actions. Supports GFM/CommonMark for validation and workflows.
Scans markdown files for broken internal links, unreachable external URLs via HTTP checks, and missing images. Use before releases, after doc restructuring, or audits.
Share bugs, ideas, or general feedback.
Validate markdown files in your workspace for common issues using markymark's built-in diagnostics engine.
Use this skill when:
This skill runs markymark's diagnostic engine across your workspace markdown files and reports:
Broken Links
[[MissingPage]][text](#missing-anchor)[[File#BadHeading]]Duplicate Headings
## Details and ## details! both create #detailsXML Tag Issues
<agent> without </agent>Simply invoke the skill from Claude Code:
/markdown-check
The skill will:
**/*.md and **/*.mdx files in the workspace📝 Markdown Quality Report
issues.md:
Line 15: Broken wiki link [[MissingPage]]
Line 23: Duplicate heading slug: #overview
README.md:
Line 42: Broken markdown link [text](#missing-section)
Line 67: Unclosed XML tag <example>
✅ Summary: 4 issues found in 2 files
This skill is a thin wrapper around markymark's LSP diagnostics:
No configuration required - uses workspace root detection from markymark.