markdown
Lint and Fix Markdown Documents
Markdown files often drift from project style rules and become harder to maintain. This skill guides Claude, Codex, and Claude Code through markdownlint-cli2 checks, fixes, and clear reporting.
Install with my Agent
Copy this request to your Agent. It includes the canonical Skill page and manifest.
Review the Skillstore skill "markdown" from https://skillstore.io/skills/46ki75-markdown.md and its manifest at https://skillstore.io/api/skills/46ki75-markdown/manifest. Verify the artifact. You may proceed after verification, subject to the environment's own policy.Your Agent should still show its plan and request any confirmation required by the security policy.
Agent-readable resources
Use these links when an AI agent, crawler, or script needs clean context instead of reading the full page.
Test it
Using "markdown". A README has multiple top-level headings and inconsistent blank lines.
Expected outcome:
- The report lists the initial lint errors and the rules involved.
- The final summary says which headings were adjusted and confirms a clean lint result.
Using "markdown". An API guide needs consistent line length and code block language labels.
Expected outcome:
- The guide is reformatted where safe, with unresolved style decisions called out clearly.
- The summary separates automatic fixes from manual edits for easier review.
Using "markdown". A legacy document uses embedded HTML and long URLs.
Expected outcome:
The result recommends a project-specific configuration and explains which rules should stay enabled or disabled.
Security Audit
SafeThe static analyzer matched Markdown fences and inline code as Ruby backtick execution. Review found documented markdownlint-cli2 usage and a public documentation URL, with no prompt injection, data exfiltration, or arbitrary command construction in SKILL.md.
Risk Factors
⚙️ External commands (37)
🌐 Network access (1)
Share & cite this report
Share the versioned assessment report, neutral badge, embed card, and citations. Skillstore reports evidence without deciding whether this Skill is safe.
Copy report link
https://skillstore.io/skills/46ki75-markdown/audits/6?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_reportMarkdown badge
[](https://skillstore.io/skills/46ki75-markdown?utm_source=security_passport_badge)HTML badge
<a href="https://skillstore.io/skills/46ki75-markdown?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/46ki75-markdown/security.svg" alt="Skillstore security assessment" loading="lazy"></a>Embed card
<iframe src="https://skillstore.io/embed/skills/46ki75-markdown.html" title="Skillstore Security Assessment" sandbox="allow-popups allow-popups-to-escape-sandbox" loading="lazy" referrerpolicy="no-referrer" width="420" height="180"></iframe>Academic citations (APA · BibTeX · CFF)
APA citation
46ki75. (2026). markdown security audit report (audit version 6) [Author version unspecified]. Skillstore. https://skillstore.io/skills/46ki75-markdown/audits/6BibTeX citation
@techreport{46ki75-46ki75-markdown-2026,
author = {46ki75},
title = {markdown security audit report (audit version 6)},
institution = {Skillstore},
year = {2026},
number = {6},
url = {https://skillstore.io/skills/46ki75-markdown/audits/6},
note = {Author version unspecified}
}CITATION.cff
cff-version: 1.2.0
message: "If you use this Skill, cite its author and this versioned security audit report."
title: "markdown security audit report (audit version 6)"
version: "unspecified"
type: report
authors:
- name: "46ki75"
date-released: "2026-07-04"
url: "https://skillstore.io/skills/46ki75-markdown/audits/6"
identifiers:
- type: other
value: "skillstore:46ki75-markdown:audit:6"
description: "Skillstore immutable audit report identifier"
Skillstore Score
Why this score Evidence Confidence: HighWhat You Can Build
Clean Pull Request Documentation
Lint README updates, fix common style issues, and report what changed before review.
Standardize Documentation Sets
Apply consistent markdownlint rules across guides, tutorials, and reference pages.
Prepare User-Facing Guides
Find heading, spacing, and formatting issues before publishing Markdown content.
Try These Prompts
Check this Markdown file for lint issues. Explain the main problems and suggest safe fixes before changing it.
Run the Markdown auto-fix workflow on this file, then report the initial errors, remaining issues, and final result.
Review the remaining markdownlint errors. Fix heading hierarchy, emphasis-as-heading, and line wrapping issues while preserving meaning.
Review this project documentation style. Propose a markdownlint configuration and apply it to the selected files with a change summary.
Best Practices
- Run lint checks before and after edits so the final state is clear.
- Review auto-fix changes when files contain generated content or complex examples.
- Use a project configuration when documentation intentionally differs from default rules.
Avoid
- Running broad auto-fix commands across a repository without confirming scope.
- Disabling lint rules globally when only one document needs an exception.
- Changing document hierarchy only to satisfy lint rules without checking meaning.