skill-linter

Validate skill metadata and filesystem structure against marketplace specifications.

47|11|Updated Nov 26, 2025
One-click install
npx skills add https://github.com/majesticlabs-dev/majestic-marketplace --skill skill-linter
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: skill-linter
Source: https://github.com/majesticlabs-dev/majestic-marketplace/tree/main/.claude/skills/skill-linter
Command: npx skills add https://github.com/majesticlabs-dev/majestic-marketplace --skill skill-linter

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

Validate skills against the agentskills.io specification to ensure marketplace readiness and quality gates. It validates frontmatter fields (name, description, license, compatibility, metadata, allowed-tools), directory naming, line limits, and structure.

Core Features & Use Cases

  • Frontmatter validation: ensures required fields (name, description) and optional ones (license, compatibility, metadata, allowed-tools) meet constraints.
  • Directory and structure validation: directory must match name, SKILL.md must exist, line limits enforced, and only allowed subdirectories present.
  • Quality gating: helps reviewers, CI, and PRs ensure skills adhere to the marketplace spec.

Quick Start

Run the linter against a Skill Unit directory: ./scripts/validate-skill.sh path/to/skill-name

Frequently Asked Questions about skill-linter

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I validate a skill against marketplace compliance standards?

Skill validation checks frontmatter fields, directory naming, line limits, and structure against the agentskills.io specification. Run the linter on your skill directory to receive a conformance assessment with actionable remediation notes and pass/fail status for marketplace readiness.

What frontmatter fields are required in SKILL.md?

Required frontmatter fields are name and description. Optional fields include license, compatibility, metadata, and allowed-tools. The linter validates that all fields meet length constraints and format requirements.

Can I use custom subdirectories in my skill folder structure?

No. The linter enforces allowed subdirectories only. Your skill directory name must match the skill name, SKILL.md must exist at the root, and only permitted subdirectories are permitted within the plugins/*/skills/* hierarchy.

How do I run the skill linter in my CI pipeline?

Execute ./scripts/validate-skill.sh with your skill directory path. The linter outputs conformance results and pass/fail status, enabling automated quality gating in CI checks and pull request validation workflows.

What happens if my skill fails validation?

The linter provides actionable remediation notes identifying specific violations—missing fields, naming mismatches, line limit overages, or disallowed subdirectories. Fix issues according to the notes and rerun validation until the skill achieves pass status.

Does the linter check line limits on descriptions?

Yes. Line limits are enforced on description and other frontmatter fields as part of the agentskills.io specification. The linter reports any violations and specifies the maximum allowed length for each field.