description-linter

Analyze YAML frontmatter and trigger phrases in SKILL.md files to report description issues.

4|Updated Jan 29, 2026

Search Tags:#linting #validation #skills #frontmatter #conflicts #trigger-phrases

Ready to run

npx skills add https://github.com/danmestas/wardrobe --skill description-linter

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: description-linter
Source: https://github.com/danmestas/wardrobe/tree/main/skills/description-linter
Command: npx skills add https://github.com/danmestas/wardrobe --skill description-linter

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Analyzes YAML frontmatter and trigger phrases across skills/*/SKILL.md to ensure trigger quality, consistent naming, and absence of cross-skill conflicts.

Core Features & Use Cases

Validate presence of actionable trigger phrases and verbs in SKILL.md frontmatter.
Enforce frontmatter rules (name, description) and constraints like length caps and kebab-case naming.
Detect cross-skill conflicts by comparing trigger phrases across skills, and surface actionable reports.
Produce human-readable reports without performing automated edits for safe review.
Use case: perform skill audits before releases or during updates to guard against ambiguity and naming drift.

Quick Start

Invoke the linter against all skills to report description issues without making changes.

Frequently Asked Questions about description-linter

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

FAQPage Schema

How do I validate trigger phrases in YAML frontmatter for skills?▼

To validate trigger phrases in YAML frontmatter, audit skill descriptions by analyzing SKILL.md files across all skills to ensure trigger presence, consistent kebab-case naming, and actionable verbs, generating structured reports for manual review.

What is the character limit for skill descriptions in frontmatter validation?▼

Skill description validation enforces a hard character limit cap of 800 and a soft cap of 500. The linter analyzes YAML frontmatter to identify descriptions exceeding these constraints and reports them without performing automated fixes.

How do I detect cross-skill conflicts in trigger phrases?▼

Detect cross-skill conflicts by comparing trigger phrases across all skills/*/SKILL.md directories. The linter surfaces naming drift and overlapping triggers, emitting human-readable reports to guard against ambiguity before releases.

Does the skill description linter automatically fix frontmatter issues?▼

No, the description linter does not perform automated edits to fix frontmatter issues. It produces human-readable structured reports identifying trigger absence, length violations, and naming conflicts for safe manual review.

When do I need to run a frontmatter audit on SKILL.md files?▼

Run a frontmatter audit on SKILL.md files before skill releases or during updates to guard against ambiguity, naming drift, and description length violations. This ensures trigger quality and cross-skill consistency without modifying files.