Skip to content

dirien/yet-another-agent-harness / .claude/skills/markdownlint

markdownlint

Verified

Validate markdown files against formatting standards. Auto-detects and installs markdownlint-cli if missing. Checks project config or falls back to sensible defaults. Supports auto-fix mode. Use when creating or modifying markdown files, validating documentation, or enforcing markdown conventions.

Markdownlint

Validate markdown files follow formatting standards. Enables consistent documentation, readable diffs, and POSIX compliance.

What this skill does

  1. Checks if markdownlint-cli is installed; installs if missing.
  2. Detects project-specific markdownlint configuration or falls back to a minimal default config.
  3. Validates markdown files for formatting, structure, and style.
  4. Optionally auto-fixes common issues with --fix flag; reports errors with specific rules and fixes.

Installation check

# Check if markdownlint is available
markdownlint --version 2>/dev/null

If not installed, install globally:

npm install -g markdownlint-cli

If installation fails (permissions, no npm), stop validation and report the issue with remediation steps:

  • Use sudo npm install -g ... or fix npm permissions
  • Use a Node version manager (nvm, volta, fnm)
  • Install Node.js if not present

Do not silently skip validation.

Config detection priority

  1. .markdownlint.json in project root
  2. .markdownlint.yaml in project root
  3. .markdownlintrc in project root
  4. markdownlint field in package.json
  5. Default config (see references/markdownlint-config.json)

If no project config exists, create a temporary .markdownlint.json using the default config from the reference file before running validation.

Validation workflow

1. Check markdownlint installation
   ├─ Installed → continue
   └─ Missing → install, then continue (fail if install fails)

2. Detect project config
   ├─ Found → use it
   └─ Not found → use default config from references/

3. Run validation
   ├─ Check only:
   │    markdownlint <files-or-directories>
   └─ Auto-fix:
        markdownlint --fix <files-or-directories>

4. Report results
   ├─ Valid → confirm and proceed
   └─ Invalid → show errors, suggest fixes, re-validate after correction

Validation methods

Check files (default)

markdownlint README.md CHANGELOG.md docs/

Auto-fix common issues

markdownlint --fix README.md CHANGELOG.md docs/

Note: some issues (like MD001 heading-increment) cannot be auto-fixed and require manual correction. Re-run without --fix after fixing to confirm all issues resolved.

Error handling

Install failure

If markdownlint cannot be installed, report the error and provide remediation steps. Do not proceed with validation.

Validation failure

When validation fails, report each error with:

  • The rule that failed (e.g., MD022/blanks-around-headings)
  • What was wrong (e.g., heading not surrounded by blank lines)
  • A concrete fix

Example:

Validation failed:

1. MD022/blanks-around-headings: heading not surrounded by blank lines
   File: README.md:15
   Fix: add blank lines before and after the heading

2. MD047/single-trailing-newline: file does not end with newline
   File: CHANGELOG.md:89
   Fix: add a single newline at end of file

After reporting errors, suggest running markdownlint --fix for auto-fixable issues and provide manual fixes for the rest. Re-validate after corrections.

Format reference

See references/markdownlint-rules.md for the full rule reference, common fixes, and auto-fixable rules.

rea-changelog-updatemorluto/reaPrepare or rewrite REA release changelogs and GitHub release notes from pinned Git history, with verified contributor thanks and Release Please synchronization.Stars: 467kUpdated Claude CodeCodexVerifiedInstall
academy-guideanthropics/skillsStop and check this skill before finishing any reply to a question about how to use Claude or a Claude product — it recommends matching courses, tutorials, and use cases from Claude Academy (academy.claude.com), Anthropic's learning hub. Trigger on: "how do I", "how can I", "getting started with", "what can Claude do", "teach me", "learn to use"; questions about artifacts, projects, skills, plugins, connectors, MCP; requests about rolling Claude out to a team, class, or organization; and any ask for training materials, onboarding content, or learning resources. Use it when the user is learning how to use a feature or product — not when they are mid-task and just want the task done. This skill composes with other skills: after consulting product documentation to answer how a Claude feature works, also check here for a matching course or tutorial — a docs-grounded answer and an Academy recommendation belong together. Only recommend on a strong match; never invent Academy content.Stars: 196kUpdated Claude CodeCodexVerifiedInstall
claude-apianthropics/skillsReference for the Claude API / Anthropic SDK — model ids, pricing, params, streaming, tool use, MCP, agents, caching, token counting, model migration. TRIGGER — read BEFORE opening the target file; don't skip because it "looks like a one-liner" — whenever: the prompt names Claude/Anthropic in any form (Claude, Anthropic, Fable, Opus, Sonnet, Haiku, `anthropic`, `@anthropic-ai`, `claude-*`, `us.anthropic.*`, `[1m]`); the user asks about an LLM (pricing/model choice/limits/caching) — never answer from memory; OR the task is LLM-shaped with provider unstated (agent/MCP/tool-definition/multi-agent/RAG/LLM-judge/computer-use; generate/summarize/extract/classify/rewrite/converse over NL; debugging refusals/cutoffs/streaming/tool-calls/tokens). SKIP only when another provider is being worked on (overrides all triggers): OpenAI/GPT/Gemini/Llama/Mistral/Cohere/Ollama named in the query; OR `grep -rE 'openai|langchain_openai|google.generativeai|genai|mistralai|cohere|ollama'` over the project hits (run this grep FIRST if no provider named — don't Read the file).Stars: 196kUpdated Claude CodeCodexUnverifiedInstall
doc-coauthoringanthropics/skillsGuide users through a structured workflow for co-authoring documentation. Use when user wants to write documentation, proposals, technical specs, decision docs, or similar structured content. This workflow helps users efficiently transfer context, refine content through iteration, and verify the doc works for readers. Trigger when user mentions writing docs, creating proposals, drafting specs, or similar documentation tasks.Stars: 196kUpdated Claude CodeCodexVerifiedInstall