Markdown Linter Fixer
CheckedAutomatically identifies and corrects common Markdown formatting errors to ensure clean, readable documents.
Install on your platform
Showing Claude Code. One command installs this skill into any of the agents below.
- 1
Run this in your project
terminal$ npx skills add s2005/markdown-linter-fixer-skill --skill markdown-linter-fixer -a claude-code Uses the open-source
skillsCLI and needs Node.js. Add-gto install it for your user instead of this project.
What we know about this skill
Publisher
s2005
Taken from the source listing. We haven't verified who controls this account.
Install target
Live repository
Not pinned. Installing fetches whatever the repository holds at the time you run the command.
Automated safety checks
This skill passed all 6 checks. We read its files at one commit and looked for the things that make a skill dangerous to run — not for whether it works.
Declares what it does: passed
SKILL.md parses and declares a name and a description.
SKILL.md exists, its frontmatter parses, and it declares a name and a description.
No undeclared network calls: passed
Makes no network calls.
Every host the skill dials — from its scripts, its config endpoints or the commands it tells the agent to run — is either well-known package and API infrastructure or declared in its own frontmatter. Links in documentation are not counted.
No obfuscated payloads: passed
No encoded or obfuscated payloads.
No base64, hex or compressed blob is decoded and then executed, and no encoded shell commands.
No credential access: passed
Reads no keys, tokens, keychains or credential files.
Neither the code nor the SKILL.md instructions read SSH keys, cloud credentials, keychains, token stores, browser cookie databases or dotfiles that hold secrets.
No pipe-to-shell installers: passed
No pipe-to-shell or download-and-run installers.
No `curl … | sh` pattern, in the code or in the instructions, that runs code fetched at run time.
Pinned to a commit: passed
Scanned s2005/markdown-linter-fixer-skill at 4f2fdc340d.
The exact upstream commit SHA that was scanned is recorded, so the result refers to specific bytes.
- Commit
- 4f2fdc340d
- Scanned
- 4 files, 555 lines
About this skill
What it does
The markdown-linter-fixer skill automatically corrects common formatting errors in Markdown documents. It leverages a linter to identify issues such as incorrect indentation, trailing whitespace, and unclosed brackets. The skill then applies fixes based on the linter's suggestions, ensuring consistent and valid Markdown syntax.
When to use it
- Cleaning up drafts: Use it when you have a rough draft of a document with inconsistent formatting that needs polishing.
- Preparing documents for publication: Ensure your Markdown files are error-free before submitting them to platforms or services that require clean Markdown.
- Standardizing team documentation: Enforce consistent formatting across a team's Markdown documents to improve readability and maintainability.
- Automating repetitive fixes: Avoid manually correcting common Markdown errors by letting the skill handle it automatically.
Key capabilities
- Automatic Markdown linting
- Correction of indentation errors
- Removal of trailing whitespace
- Fixing unclosed brackets and other syntax issues
Example prompts
- "Please fix the formatting in this Markdown document."
- "Can you lint and correct this file?"
- "Make sure this Markdown is valid and well-formatted."
Tips & gotchas
The skill relies on a linter, so its effectiveness depends on the rules configured within that linter. Review the changes made by the skill to ensure they align with your desired formatting style.