Skip to main content
Alison Aquinas logoAlison's LLM Skills Marketplace

markdownlint

Included in skill bundleshared-skillsView on GitHub ↗

Files

SKILL.mdagentsreferencesscripts

Install

Install only this skill with npx skills
npx skills add alisonaquinas/llm-shared-skills --skill 'markdownlint' -g -y
Install the containing skill bundle
/plugin install shared-skills@llm-skills
Download markdownlint-skill.zip
This skill is bundled inside shared-skills. Use npx skills when you only want this skill, or install the bundle once to make every included skill available through the plugin marketplace flow. Browse the full skill bundle repository at github.com/alisonaquinas/llm-shared-skills.

Invoke

Invoke this skill after installation
/shared-skills:markdownlint

SKILL.md

name: markdownlint description: > Run markdownlint-cli2 to lint and fix Markdown files using project-specific rules. Use when enforcing Markdown linting rules, applying fixes to documentation, validating README/AGENTS/docs formatting, checking configuration file compliance, understanding Markdown lint violations, disabling specific rules, or running quality checks against curvecapture/markdownlint-cli2.jsonc or local .markdownlint-cli2.jsonc config files.

Markdownlint CLI2 Enforcer

Prerequisite Check

Run this before proposing lint or fix commands:

command -v markdownlint-cli2 >/dev/null 2>&1 || command -v markdownlint >/dev/null 2>&1

If no markdownlint binary is available, surface that first and either run scripts/install.sh or scripts/install.ps1, or use the documented npx --yes markdownlint-cli2 fallback when networked package execution is acceptable.

Quick Start

  1. Confirm a runner exists: markdownlint-cli2 --version or npx --yes markdownlint-cli2 --version
  2. Resolve the config before linting anything
  3. Run a check without --fix first
  4. Apply --fix only when the task requires edits
  5. Re-run the check and report the final status

Intent Router

RequestReferenceLoad When
Install tool, first-time setupreferences/install-and-setup.mdUser needs to install markdownlint-cli2 or do initial configuration
Rule reference, config formatreferences/rules-and-config.mdUser asks about specific rules, how to disable/configure rules, or understand violations
Quick command patterns(Inline below)Standard lint/fix workflows

Overview

Use markdownlint-cli2 to check and fix Markdown consistently. Prefer the provided Curvecapture config file when present, then fall back to local repo config files.

Workflow

  1. Resolve config file.
  • Prefer explicit user-provided config path.
  • Else prefer curvecapture/markdownlint-cli2.jsonc.
  • Else use local markdownlint-cli2.jsonc or .markdownlint-cli2.jsonc if present.
  1. Resolve target scope.
  • Use user-provided file paths or globs when given.
  • If scope is not provided, lint **/*.md and **/*.markdown from current working directory.
  • Avoid linting generated output and dependency trees unless explicitly requested.
  1. Run lint check first.
  • Run without --fix to capture violations.
  • Report failing rules and affected files before making edits.
  1. Apply fixes as needed.
  • Run with --fix only when user asks for fixes or when task requires enforcing rules.
  • Re-run lint check to ensure a clean result.
  1. Summarize clearly.
  • Report config used, targets checked, whether fixes were applied, and final lint status.

Commands

Use the bundled script for deterministic execution:

./skills/markdownlint-cli2-enforcer/scripts/run-markdownlint-cli2.sh --config ./curvecapture/markdownlint-cli2.jsonc README.md AGENTS.md

Run with automatic config detection:

./skills/markdownlint-cli2-enforcer/scripts/run-markdownlint-cli2.sh README.md

Run and auto-fix:

./skills/markdownlint-cli2-enforcer/scripts/run-markdownlint-cli2.sh --fix README.md AGENTS.md

Verification cue: a clean run exits without rule violations after the final non---fix pass. If the binary is missing, stop at install or npx guidance rather than presenting the wrapper as immediately runnable.

Safety and Guardrails

ActionGuardrailWhy
Lint checkAlways run without --fix firstVerify violations before modifying files
Report violationsList failed rules and affected files before auto-fixingOperator visibility; manual review of what changed
Apply fixesOnly when user explicitly requests --fix or task requires itPrevent unintended modifications
Verify after fixRe-run lint check to ensure clean resultConfirm fixes were effective

Resources

scripts/run-markdownlint-cli2.sh

Use this wrapper to:

  • auto-select config file
  • run markdownlint-cli2 directly if installed
  • fall back to markdownlint (with mapped disabled rules) when available
  • else fall back to npx --yes markdownlint-cli2 when binary is missing
  • apply optional --fix

Recovery note: if local binaries are missing, state which path comes next: install script, wrapper fallback, or npx. Do not imply that --fix is safe until the lint pass has been shown first.

← Back to marketplace