Skip to content
TrustedSkillsbeta
Back to all skills

Markdownlint

Checked
povertyaction·vlatest·writing·MIT

Markdownlint automatically checks your Markdown for style errors, ensuring clean formatting and readability – a vital tool for collaborative documentation.

Install on your platform

Showing Claude Code. One command installs this skill into any of the agents below.

  1. 1

    Run this in your project

    terminal
    $ npx skills add povertyaction/ipa-stata-template --skill markdownlint -a claude-code
  2. Uses the open-source skills CLI and needs Node.js. Add -g to install it for your user instead of this project.

What we know about this skill

Publisher

povertyaction

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.

No human has reviewed this code. The checks below are a static scan of the files at one commit — nobody has run this skill or judged whether it works. A skill runs with whatever access you give your agent, so read the source before you install it.

Automated safety checks

scanned

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 povertyaction/ipa-stata-template at 550aebd016.

    The exact upstream commit SHA that was scanned is recorded, so the result refers to specific bytes.

Scanned
3 files, 384 lines
This is a static scan, not a review. It reads the skill's files; it does not run them, and it cannot tell you whether the skill is any good or whether the code does what its description says. A skill runs with whatever access you give your agent.
What each check looks for →

About this skill

What it does

The markdownlint skill enforces consistent style and formatting in Markdown documents. It checks for common errors, stylistic issues, and adherence to best practices, ensuring readability and maintainability of text files written in Markdown. This skill helps automate the process of reviewing and correcting Markdown content.

When to use it

  • Team documentation: Standardize Markdown formatting across a team’s shared documents.
  • Blog posts: Ensure blog articles adhere to consistent style guidelines before publishing.
  • Technical writing: Maintain quality and consistency in technical manuals or guides.
  • Project READMEs: Enforce clean and readable project documentation for open-source projects.

Key capabilities

  • Markdown linting
  • Style enforcement
  • Error checking

Example prompts

  • "Please lint this Markdown file: [file content]"
  • "Check the style of this document and suggest improvements: [file content]"
  • "Run markdownlint on this text and report any errors: [text]"

Tips & gotchas

This skill assumes you are providing valid Markdown syntax. Complex or unusual Markdown constructs might not be handled perfectly, so review suggestions carefully.