check-skill-formatting

You validate skill files by running linting scripts that check for placeholder conventions, code fence integrity, and relative path usage. This identifies formatting inconsistencies and enforces project standards before committing new skills.

Markdown linting flags bracket placeholders like [string] because they violate instructional placeholder conventions. The formatter enforces the { string } convention to maintain consistency and prevent stylistic regressions across skill files.

The best way to check internal markdown references is using a relative path linter that flags ../ usage and promotes the ${CLAUDE_PLUGIN_ROOT} convention. This ensures better maintainability and prevents broken internal links in skill files.

Yes, the formatter checks code fence integrity in skill files by identifying bare or improperly nested code fences within Markdown. It runs specific linting scripts to catch these structural formatting violations.

Yes, you can use this formatter to maintain frontmatter integrity in markdown skills. It validates frontmatter integrity alongside preprocessing patterns and placeholder conventions, ensuring skill files meet formatting standards before review.

The limitations of automated skill file formatting checks include a basic implementation depth that focuses strictly on placeholder, fence, and relative path linting. It does not perform complex semantic validation or auto-fix all stylistic issues without manual intervention.