plugins-claude/markdown/skills/markdown/SKILL.md
Markdown linting and formatting — check, format, setup
npx skillsauth add st0nefish/claude-toolkit markdownInstall 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.
$IF($1, Run the $1 action below.)
$IF(!$1, Available actions: check, format, setup. Usage: /markdown [action])
Lint markdown files for style violations using rumdl.
Check a single file:
bash ${CLAUDE_PLUGIN_ROOT}/scripts/rumdl-wrap check README.md
Check all markdown in a directory:
bash ${CLAUDE_PLUGIN_ROOT}/scripts/rumdl-wrap check docs/
Check everything in the repo:
bash ${CLAUDE_PLUGIN_ROOT}/scripts/rumdl-wrap check .
.rumdl.toml config in the project/markdown format to auto-fix violations/markdown setupAuto-fix markdown lint violations using rumdl.
Fix a single file:
bash ${CLAUDE_PLUGIN_ROOT}/scripts/rumdl-wrap check --fix README.md
Fix all markdown in a directory:
bash ${CLAUDE_PLUGIN_ROOT}/scripts/rumdl-wrap check --fix docs/
Fix everything in the repo:
bash ${CLAUDE_PLUGIN_ROOT}/scripts/rumdl-wrap check --fix .
.rumdl.toml config in the project/markdown setupInstall rumdl, the Rust markdown linter and formatter.
command -v rumdl && rumdl --version
Via Cargo (all platforms):
cargo install rumdl
Via Homebrew (macOS):
brew install rumdl
After installing, verify with rumdl --version.
development
Start work from your description — explore the codebase and plan
data-ai
Multi-phase, multi-agent feature workflow: spec → plan → refine → divide → execute → review. Invoke when the user escalates a session-start/session-issue flow to orchestration, or asks to run a non-trivial feature (multiple files, design ambiguity, cross-cutting concerns, correctness-critical paths) through the full multi-agent workflow. For small fixes, prefer session-start.
tools
Browse open issues, pick one, and start work on it
tools
Interact with GitHub and Gitea issue trackers and CI systems. List and show issues, file bugs, comment on issues or PRs, list and show pull requests, and fetch CI run logs — all from any repo context without leaving the session.