package-validator

Validate SEMO package structure and Sub-Agent optimization rule conformance.

Updated Dec 11, 2025
One-click install
npx skills add https://github.com/semicolon-devteam/semo --skill package-validator
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: package-validator
Source: https://github.com/semicolon-devteam/semo/tree/main/packages/meta/skills/package-validator
Command: npx skills add https://github.com/semicolon-devteam/semo --skill package-validator

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires Bash, Read, Grep, and includes references (resource) components.

What problem does it solve?

This Skill automatically verifies the structural integrity of SEMO packages and ensures adherence to Claude Code Sub-Agent optimization rules, acting as a critical quality gate before versioning or deployment.

Core Features & Use Cases

  • Structural Validation: Checks for correct directory structure and file presence within SEMO packages.
  • Frontmatter Compliance: Verifies that all Agent/Skill/Command files have the required frontmatter fields (name, description, tools, model).
  • Optimization Rule Check: Audits Agents for "PROACTIVELY use when" patterns and standard tool usage, ensuring efficient AI interaction.
  • Consistency Verification: Confirms CLAUDE.md consistency and proper integration of components.
  • Use Case: Before releasing a new version of semo-next, you can run "package-validator semo-next" to ensure all components meet quality standards and optimization rules.

Quick Start

Validate a package: "package-validator {패키지명}" Check Agent/Skill rules: "Agent/Skill 추가/수정/삭제 후 검증" Run pre-versioning checks: "버저닝 전 품질 게이트"

Frequently Asked Questions about package-validator

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

FAQPage Schema
How do I validate SEMO package structure before release?

Package validation checks SEMO package directory structure, file presence, and frontmatter completeness (name, description, tools, model) to ensure quality standards. Run package-validator with your package name to receive a PASS/FAIL assessment before versioning.

What does SEMO package validation check for?

Validation audits kebab-case naming, allowed tools, CLAUDE.md consistency, frontmatter compliance, and Sub-Agent optimization rules like "PROACTIVELY use when" patterns to enforce Claude Code standards.

When should I run package validation in my workflow?

Run validation after adding, updating, or deleting agents or skills, and before pre-release versioning gates. It acts as a quality gate to catch structural and optimization issues early.

Can I validate multiple agents and skills in one SEMO package?

Yes, package-validator scans the entire SEMO package directory structure and checks all Agent, Skill, and Command files for frontmatter compliance and optimization rule adherence in a single pass.

What happens if package validation finds issues?

Validation outputs a structured PASS/FAIL assessment identifying missing frontmatter fields, naming violations, inconsistent CLAUDE.md references, or Sub-Agent optimization rule breaches so you can fix them before deployment.

Do I need Bash and Grep installed to run package validation?

Yes, package-validator depends on Bash, Read, and Grep utilities. Ensure these tools are available in your environment before running validation on SEMO packages.