Browse / Security Testing / SEMO Package Validator

SEMO Package Validator

Validates the structural integrity and rule compliance of SEMO framework packages and Sub-Agents.

SkillSecurity TestingComplianceAi Agent

The source repository doesn't declare a license. Check its terms before reusing the code.

Key features

  • Enforces tool standardization by checking for forbidden tool usage
  • Verifies documentation consistency between agents and the CLAUDE.md manifest
  • Checks for correct file naming conventions and directory structures
  • Audits compliance with Sub-Agent optimization rules, like the 'PROACTIVELY' pattern
  • Validates required frontmatter fields (name, description, tools, model)

Use cases

  • Perform a quality gate check before versioning a package or releasing new code.
  • Verify the integrity of an Agent or Skill after making additions or modifications.
  • Audit a package to ensure it complies with project-specific optimization rules and documentation standards.

FAQ

What does the SEMO Package Validator skill do?

This skill automatically validates the structural integrity and rule compliance of packages within the SEMO framework. It checks file structures, frontmatter fields, Sub-Agent optimization rules, and documentation consistency to ensure your project is correctly configured.

When should I use this skill?

Use the SEMO Package Validator after adding or modifying an Agent/Skill, when updating the `CLAUDE.md` manifest for consistency, as a pre-commit or pre-versioning quality gate, or anytime you need to audit compliance with SEMO's best practices.

How does this skill improve my development workflow?

It automates tedious manual checks, preventing common configuration errors early. This saves time, reduces bugs, enforces coding standards across your team, and ensures your Sub-Agents are consistently structured and optimized for performance.

What specific capabilities does it provide?

It validates required frontmatter fields (name, description, tools, model), audits Sub-Agent optimization rules like the 'PROACTIVELY' pattern, enforces tool usage standards, verifies documentation consistency, and checks for correct file naming conventions.