skills-review:lint

Lint SKILL.md files against repository skill guidelines with severity filtering.

7|15|Updated Jan 23, 2026
One-click install
npx skills add https://github.com/openshift-eng/edge-tooling --skill skills-review-lint
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: skills-review:lint
Source: https://github.com/openshift-eng/edge-tooling/tree/main/plugins/skills-review/skills/lint
Command: npx skills add https://github.com/openshift-eng/edge-tooling --skill skills-review-lint

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

It prevents broken or low-quality skill definitions from being shipped by automatically checking SKILL.md files against the repo’s skill guidelines.

Core Features & Use Cases

  • Scope control: Lints changed SKILL.md files versus main, or lints everything under plugins with --all, or targets specific file paths.
  • Severity filtering: Lets you focus on failures with --severity error while suppressing advisory warnings.
  • Actionable results: Reports issues grouped by file with check ID, severity, and message, and can help propose concrete patches when failures are found.

Quick Start

Run /skills-review:lint --all --severity error to lint every SKILL.md in plugins and show only errors.

Frequently Asked Questions about skills-review:lint

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

FAQPage Schema
How do I lint SKILL.md files to catch metadata issues before merging?

Lint SKILL.md files by invoking the repo’s scripts/lint-skills.py to validate metadata against guidelines, reporting issues grouped by file with check ID and severity. Run it against changed files versus main or specific paths.

What is skill linting and how does it validate yaml frontmatter?

Skill linting automatically checks SKILL.md definitions to prevent incorrect or guideline-violating metadata from being merged. It validates yaml frontmatter and other definitions by running standardized checks against repository guidelines.

Can I lint only changed markdown files versus main instead of the whole repository?

Yes, you can lint changed files versus main by default, or lint every SKILL.md under plugins using the --all flag. You can also target specific file paths directly for more granular validation.

How do I filter linting results to show only errors and suppress warnings?

Filter linting results by using the --severity error argument to focus on failures while suppressing advisory warnings. This ensures you only see critical metadata violations that block merging.

What format does the linter use to report code quality issues in SKILL.md?

The linter reports code quality issues grouped by file, displaying the check ID, severity level, and message for each violation. It provides actionable results and can help propose concrete patches when failures are found.