Skip to main content

​
Overview

The list-checks command displays all available static analysis checks with their metadata, including check IDs, names, dimensions, severity levels, and whether they’re required by the Agent Skills specification.

​
Usage

​
Options

​
string
Alias: -dFilter checks by dimension.Options:
  • structure - File structure and frontmatter checks
  • naming - Naming convention checks
  • description - Description quality checks
  • content - Content quality and completeness checks
​
boolean
default:false
Alias: -sOnly show checks required by the Agent Skills specification (excludes quality suggestions).
​
boolean
default:false
Only show quality suggestion checks (excludes spec-required checks).

​
Examples

​
List all checks

Output:

​
Filter by dimension

​
Show only spec-required checks

​
Show only quality suggestions

​
Output Format

The table includes:
​
string
Unique identifier for the check (e.g., skill-exists, valid-frontmatter)
​
string
Human-readable name of the check
​
string
Category of the check:
  • structure - File organization and frontmatter
  • naming - Naming conventions
  • description - Description quality
  • content - Content completeness and quality
​
string
Impact level:
  • error - Must be fixed (blocks validation)
  • warning - Should be addressed
  • info - Optional improvement
​
string
Whether the check is required by the Agent Skills specification:
  • Yes - Spec-required (10 checks)
  • No - Quality suggestion (18 checks)
​
string
Brief explanation of what the check validates

​
Check Categories

​
Spec-Required Checks (10)

These checks enforce the Agent Skills specification:
  • skill-exists - SKILL.md file must exist
  • valid-frontmatter - Valid YAML frontmatter
  • standard-fields - Required frontmatter fields present
  • name-required - Name field in frontmatter
  • name-length - Name within length limits
  • description-required - Description field in frontmatter
  • description-length - Description within length limits
  • body-not-empty - Non-empty skill body
  • valid-scripts - scripts/ folder structure valid
  • valid-references - references/ folder structure valid

​
Quality Suggestions (18)

These checks recommend best practices:
  • Token budgets
  • Content completeness
  • Naming conventions
  • Reference depth
  • Asset validation
  • And more…

​
Summary Line

The summary shows:
  • Total number of checks displayed
  • Count of spec-required checks
  • Count of quality suggestion checks
When filtered, the summary reflects only the displayed checks.

​
Exit Codes

  • 0: List generated successfully
  • 1: Error occurred (invalid dimension, etc.)

​
Use Cases

​
Understand available checks

See what validations are performed:

​
Focus on spec requirements

View only mandatory checks:

​
Review content checks

See all content-related validations:

​
Documentation reference

Generate a reference list of checks:

​
Notes

The total check count is 28: 10 spec-required + 18 quality suggestions.
Checks are organized using an auto-discovery pattern. Each check is a class decorated with @register_check or defined as a FieldRule in the schema.