policy.enforce

Validate YAML manifests against policy rules for naming, versioning, permissions, and status.

2|Updated Oct 22, 2025
One-click install
npx skills add https://github.com/epieczko/betty --skill policy-enforce
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: policy.enforce
Source: https://github.com/epieczko/betty/tree/main/skills/policy.enforce
Command: npx skills add https://github.com/epieczko/betty --skill policy-enforce

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires PyYAML.

What problem does it solve?

Validates skill and agent manifests against Betty Framework policy rules to ensure naming consistency, semantic versioning, permissions, and status lifecycle.

Core Features & Use Cases

  • Enforces lowercase naming with allowed dots for namespacing
  • Validates semantic versions and status values
  • Checks permissions against allowed set
  • Batch mode support to scan multiple manifests for governance

Quick Start

Validate a single manifest: python3 skills/policy.enforce/policy_enforce.py skills/sample.skill/skill.yaml

Frequently Asked Questions about policy.enforce

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

FAQPage Schema
How do I enforce naming conventions and versioning in skill and agent manifests?

Enforce naming conventions and versioning by running policy.enforce against your manifest files. It validates lowercase naming with dots, semantic versions, permissions, and status values to ensure consistency across your skill and agent definitions in a single validation pass.

Can I validate multiple manifests at once for policy compliance?

Yes, batch mode scans all manifests in your skills/ and agents/ directories simultaneously. This enables governance-scale validation across your entire manifest collection, reporting all violations in a single run with optional JSON output.

What policy rules does manifest validation check?

Manifest validation checks lowercase naming with allowed dots for namespacing, semantic versioning format, permissions against an allowed set, and lifecycle status values. Violations are reported with details to help you bring manifests into compliance.

How do I get policy violation reports in JSON format?

Use the JSON output option in policy.enforce to export validation results in structured JSON. This format simplifies integration with automated workflows, CI/CD pipelines, and downstream governance tools.

Do I need to validate manifests individually or can I use strict mode?

Policy.enforce supports both single-file validation for targeted checks and strict mode for batch scanning. Strict mode enforces all policy rules across your manifest collection, ideal for preventing noncompliant manifests from reaching production.