skill-comply

You can measure agent compliance by generating expected behavioral sequences from skill definitions, running the agent through varying prompt scenarios, and comparing the recorded tool-call timeline against the spec to calculate a compliance rate.

Agent compliance reporting quantifies whether coding agents follow defined skills by generating expected behavioral sequences, running three scenarios with decreasing prompt strictness, classifying tool usage against the spec, and reporting a compliance score.

You can test agent behavior by running three scenario prompts with decreasing strictness—from supportive to neutral to competing—and capturing the full tool call timeline to classify whether the agent still follows the defined skills.

Yes, the compliance reporting tool requires the pyyaml dependency to parse skill definitions and generate the expected behavioral sequences needed for measuring agent compliance.

Yes, the tool records a full tool-call timeline during the agent run, classifies tool usage against the generated spec, and checks temporal ordering to verify that the agent executed actions in the expected sequence.

The best way to automate compliance checks is to run a script that auto-generates behavioral specs from skill definitions, executes scenario sessions, and produces self-contained reports with timelines, compliance rates, and hook-promotion guidance.