hook.simulate

Validate and simulate Betty Framework hook manifests with JSON output.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires yaml.

What problem does it solve?

The hook.simulate skill allows developers to test a hook manifest before registering it in the Betty Framework by validating structure, simulating triggers, and optionally executing commands in a controlled environment.

Core Features & Use Cases

  • Manifest validation for required and optional fields
  • Pattern matching and trigger simulation for expected file changes
  • Optional command execution in a safe environment
  • JSON output suitable for automation and analysis

Quick Start

python skills/hook.simulate/hook_simulate.py examples/test-hook.yaml

Frequently Asked Questions about hook.simulate

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

FAQPage Schema
How do I validate a Betty Framework hook manifest before registration?

Hook.simulate validates your manifest structure, simulates trigger events, and tests command execution in a controlled environment before you register it in Betty Framework. Run it against your hook YAML file to catch configuration errors early and ensure your manifest meets all required field specifications.

Can I test hook commands without actually executing them?

Yes, hook.simulate supports dry-run mode to validate command syntax and behavior without executing them. This lets you verify your hook logic, pattern matching, and timeouts safely before deploying to production.

What does hook pattern matching validation do?

Hook.simulate tests file pattern matching logic to ensure your hook triggers correctly on the intended file changes. It simulates events against your patterns and reports which triggers fire, helping you catch overly broad or restrictive pattern definitions.

How do I get structured output from hook validation for automation?

Hook.simulate outputs results in JSON format, making it suitable for automation pipelines, CI/CD integration, and programmatic analysis. You can parse and act on validation results without manual inspection.

Can I test hook timeouts and blocking behavior?

Hook.simulate enforces timeout settings and validates blocking behavior as specified in your manifest. It reports timeout violations and blocking issues so you can adjust timing parameters before registration.