Skip to content
TrustedSkillsbeta
Back to all skills

Skill Linter

Checked
majesticlabs-dev·vlatest·agents

Skill Linter analyzes your text for potential issues like style inconsistencies and errors, ensuring cleaner, more professional output.

Repository

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 majesticlabs-dev/majestic-marketplace --skill skill-linter -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

majesticlabs-dev

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 majesticlabs-dev/majestic-marketplace at 04e97708c2.

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

Commit
04e97708c2
Manifest
.claude/skills/skill-linter/SKILL.md
Scanned
2 files, 495 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 Skill Linter analyzes text files representing AI agent skills to ensure they adhere to specific formatting and content guidelines. It checks for compliance with required frontmatter, structural rules (like directory naming and file existence), and content quality standards—such as avoiding ASCII art, decorative quotes, or unnecessary persona statements. The goal is to improve the clarity, efficiency, and discoverability of skills within a marketplace environment.

When to use it

This skill is useful in these scenarios:

  • Adding new skills to a marketplace.
  • Reviewing pull requests (PRs) for existing skills.
  • Running quality checks before merging changes into a codebase.
  • Ensuring that existing skills meet established compliance standards.

Key capabilities

  • Frontmatter Validation: Checks required and optional frontmatter fields against defined constraints (e.g., name length, description content).
  • Structural Rule Enforcement: Verifies directory names match skill names, mandatory files exist, and disallowed files are absent.
  • Content Quality Analysis: Identifies and flags issues like ASCII art, decorative quotes, persona statements, and unnecessary lines.
  • Description Routing Quality Assessment: Evaluates the clarity and effectiveness of skill descriptions in defining usage scenarios and expected outputs.

Example prompts

Here are some examples of how you might use this skill:

  • "Analyze skill-example/SKILL.md for compliance."
  • "Check the quality of the description in my-new-skill/SKILL.md."
  • "Run a full linting check on all skills in the skills/ directory."

Tips & gotchas

  • The skill requires access to the text files being analyzed (typically .md files).
  • Skill descriptions should focus on when and how to use the skill, not on adopting a persona.
  • Pay attention to warnings related to description routing quality; these indicate areas where the description could be improved for better discoverability and usability.