governanca

To audit SKILL.md files for security and compliance issues, validate skill definitions and requested permissions to detect misconfigurations, over-privileged tool requests, and frontmatter mismatches. This generates a structured compliance report with severity levels and exact suggested fixes.

Skill governance is the process of validating skill definitions and requested permissions to detect compliance, security, and integrity issues. You need permission validation during onboarding, code review, and periodic governance audits to catch naming, frontmatter, and permission mismatches.

To detect over-privileged tool requests in repository skills, validate skill definitions and requested permissions to flag risky patterns and inappropriate tools. This security check produces actionable remediation guidance to prevent security and maintainability regressions.

Yes, you can verify AgentSkills.io compliance by validating SKILL.md frontmatter fields, name format (lowercase-hyphen), and description quality. This ensures your repository skills meet compliance standards and prevents architectural issues.

The best way to check skill architecture and prompt quality before deployment is to validate skill definitions and permissions, which identifies weak prompts and architectural issues. This produces a structured report listing issues, severity, and exact suggested fixes.

Yes, skill governance requires file access and optional script execution to validate definitions and permissions. It also uses web and vision lookups to detect compliance, security, and integrity issues, generating structured reports with actionable remediation steps.