Skip to content
TrustedSkillsbeta
Back to all skills

Markdownlint

Checked
jcardif·vlatest·writing·MIT

Markdownlint analyzes your Markdown for style issues, ensuring clean formatting and readability – a vital tool for consistent 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 jcardif/agent-skills --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

jcardif

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 jcardif/agent-skills at 34216b2e68.

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

Scanned
2 files, 655 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 jcardif-markdownlint skill analyzes Markdown files and flags potential style or formatting issues. It helps ensure consistency and adherence to best practices within Markdown documents. This includes checking for things like incorrect indentation, invalid syntax, and common stylistic errors.

When to use it

  • Content Creation: Use before publishing blog posts, documentation, or any other content written in Markdown.
  • Code Documentation: Enforce consistent formatting in code comments and README files.
  • Team Collaboration: Standardize Markdown style across a team working on shared documents.
  • Automated Checks: Integrate into CI/CD pipelines to automatically validate Markdown files during development.

Key capabilities

  • Markdown syntax validation
  • Style guide enforcement (details not provided)
  • Potential error flagging

Example prompts

  • "Please lint this markdown file and report any errors: [file contents]"
  • "Check the following markdown for style inconsistencies: [markdown text]"
  • "Analyze this document and suggest improvements to its Markdown formatting: [document content]"

Tips & gotchas

The skill's specific ruleset is not detailed in the provided source. Results should be reviewed carefully, as some flags may represent subjective stylistic choices rather than hard errors.