Skill Validator FAQs

Question 1

Can I validate a specific skill without scanning the entire repository?

Accepted Answer

Yes, you can use the command '/validate-skills <name>' to focus the audit on a single specific skill directory.

Question 2

How does the security scanning feature work?

Accepted Answer

The skill runs specialized scripts to scan the directory for patterns matching API keys, secrets, and local user paths (like /Users/username/) to prevent accidental data leaks.

Question 3

What exactly does the Validate Skills tool check?

Accepted Answer

It verifies the existence of SKILL.md, validates all required YAML frontmatter fields, checks that naming follows lowercase-hyphen conventions, and scans for sensitive data like secrets or hardcoded paths.

Question 4

What constitutes a 'blocking' error in the validation report?

Accepted Answer

Critical issues like missing required frontmatter fields (name, description) or invalid naming conventions are marked as Errors and will block the publication status.

Question 5

Is a README.md file mandatory for validation to pass?

Accepted Answer

While a README.md is highly recommended for documentation and will trigger a warning if missing, it is not currently a blocking error for publication.

Skill Validator

主要功能

使用场景

Skill Validator

主要功能

使用场景