INVALID NAME!!!

Validate SKILL.md frontmatter and generate diagnostic reports for CI.

9|1|Updated Feb 10, 2026
One-click install
npx skills add https://github.com/skill-tools/skill-tools --skill invalid-name-skill-tools
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: INVALID NAME!!!
Source: https://github.com/skill-tools/skill-tools/tree/main/packages/core/test/fixtures/invalid-skill
Command: npx skills add https://github.com/skill-tools/skill-tools --skill invalid-name-skill-tools

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Detects and surfaces Skill Unit metadata that is invalid or incomplete so teams can fix or remove broken SKILL.md entries.

Core Features & Use Cases

  • Validate presence of required fields (name and description) in SKILL.md.
  • Identify unusual characters or non-descriptive descriptions that may hinder discovery.
  • Produce a concise diagnostic report suitable for CI or PR checks.

Quick Start

Run the validator on the skill directory to reveal metadata issues.

Frequently Asked Questions about INVALID NAME!!!

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

FAQPage Schema
How do I validate SKILL.md frontmatter metadata in a CI pipeline?

To validate SKILL.md frontmatter metadata in CI, run this validator on your repository directories. It identifies missing required fields like name and description, producing a diagnostic report suitable for PR checks and automated builds.

What happens if my SKILL.md metadata is missing required fields?

When SKILL.md metadata is missing required fields, the validator flags the specific files and directories. It checks for the presence of name and description fields and reports incomplete entries so teams can fix or remove broken SKILL.md files.

Can I lint Skill Unit metadata for non-descriptive descriptions locally?

You can lint Skill Unit metadata locally to identify unusual characters or non-descriptive descriptions that hinder discovery. Running the validator on your skill directory reveals these metadata issues before pushing changes.

Do I need any dependencies to check for invalid Skill Unit metadata?

No dependencies are required to check for invalid Skill Unit metadata. The validator operates directly on a directory containing SKILL.md files, analyzing frontmatter to output a concise diagnostic report without external packages.

Why does my SKILL.md validation report show incomplete metadata entries?

Your SKILL.md validation report shows incomplete metadata entries because the validator detected missing name or description fields, or unusual characters in the frontmatter. It surfaces this invalid metadata so teams can fix broken SKILL.md entries.