team-shinchan:verify-skills

Validate SKILL.md files for schema, naming, and input validation compliance.

8|2|Updated Feb 3, 2026
One-click install
npx skills add https://github.com/seokan-jeong/team-shinchan --skill team-shinchan-verify-skills
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: team-shinchan:verify-skills
Source: https://github.com/seokan-jeong/team-shinchan/tree/main/skills/verify-skills
Command: npx skills add https://github.com/seokan-jeong/team-shinchan --skill team-shinchan-verify-skills

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill enforces schema, naming, and input validation for SKILL.md files to prevent malformed or misnamed skills from entering the codebase and to maintain discoverability and CI reliability.

Core Features & Use Cases

  • Schema Validation: Executes a node validator to confirm required frontmatter fields (name, description, user-invocable) and required sections are present.
  • Format & Naming Checks: Ensures skills follow kebab-case naming and structural conventions.
  • Input Validation: Verifies that input validation rules are defined and correctly structured.
  • Use Case: Run after modifying skills, adding/removing skills, or in CI to block merges that introduce invalid or noncompliant skill files.

Quick Start

Use the verify-skills skill to run the node-based validators against the skills directory.

Frequently Asked Questions about team-shinchan:verify-skills

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

FAQPage Schema
How do I validate SKILL.md files for schema and naming compliance in CI?

You can validate SKILL.md schema and naming compliance by running a node-based validator against the skills directory to check for required frontmatter, kebab-case names, and input validation rules during local edits or CI runs.

What is skill schema validation and why is it needed for Claude plugins?

Skill schema validation is the process of enforcing required frontmatter fields and structural conventions in SKILL.md files. It is needed to prevent malformed or misnamed skills from entering the codebase and to maintain discoverability.

How do I ensure input validation rules are defined in my skill files?

To ensure input validation rules are defined, run a validator that verifies the presence and correct structure of input validation sections within your SKILL.md files, blocking merges if these rules are absent.

Does the validator require node to check for missing frontmatter in skills?

Yes, the validator requires node-based execution to check for missing frontmatter and must exit with code 0 to confirm the presence of name and description fields in the skill files.

What happens if my skill naming violates kebab-case conventions during a pull request?

If skill naming violates kebab-case conventions during a pull request, the schema validation process will catch the naming violation and block the merge to prevent noncompliant skill files from entering the codebase.