lint-skill

To validate frontmatter and workflow consistency, run a lint check to scan skill definitions, enforce structural rules, and generate a compliance report highlighting any missing fields or broken references.

The best way to detect broken references and placeholders is to scan all skill files using a validation linter that analyzes workflow steps and references to identify gaps and keep repositories healthy.

You can enforce skill naming conventions and use triggers by applying automated checks across all skills in the marketplace, validating their definitions against required atomic and composite scope rules.

Yes, you can check prerequisites and validation types for both composite and atomic skills by applying structural analysis that validates references and enforces scope conventions across the ecosystem.

Skill integration fails because divergent frontmatter and structural inconsistencies cause maintenance pain, requiring a lint validation to ensure all definitions comply with the required workflow rules.