skill-comply

Generate compliance specs and classify tool-call traces from claude -p stream-json outputs.

1|Updated Apr 7, 2026
One-click install
npx skills add https://github.com/riftzen-bit/gemini-setup --skill skill-comply-riftzen-bit
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: skill-comply
Source: https://github.com/riftzen-bit/gemini-setup/tree/main/skills/skill-comply
Command: npx skills add https://github.com/riftzen-bit/gemini-setup --skill skill-comply-riftzen-bit

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires pyyaml, and includes scripts (resource) components.

What problem does it solve?

Provides objective, repeatable measurement of whether coding agents follow documented skills, rules, and agent definitions by turning prose into observable specs and verifying actual tool-call timelines.

Core Features & Use Cases

  • Spec Generation: Auto-extracts an expected behavioral sequence from a skill/rule Markdown file.
  • Scenario Pressure Testing: Creates three scenarios (supportive, neutral, competing) to probe prompt independence.
  • Trace Collection & Analysis: Executes scenarios via claude -p, captures stream-json tool-call traces, classifies events with an LLM, enforces temporal ordering, and emits a self-contained Markdown compliance report.
  • Use Case: Validate TDD workflows, security or linting rules, and whether specialized agents invoke expected behaviors under adversarial prompts.

Quick Start

Run skill-comply on a SKILL.md path to generate a compliance spec, execute three scenarios against an agent, and produce a Markdown report summarizing compliance rates and timelines.

Frequently Asked Questions about skill-comply

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

FAQPage Schema
How do I verify if an AI agent follows documented rules and skills?

To verify agent compliance, you can generate behavioral specs from Markdown rule files, execute testing scenarios, and classify tool-call traces to measure whether the agent follows documented rules and skills.

What is tool-call trace classification for agent compliance reporting?

Tool-call trace classification evaluates agent behaviors by capturing stream-json outputs from executed scenarios, classifying tool events with an LLM, and enforcing deterministic temporal ordering to generate compliance reports.

How do I test prompt independence using supportive and competing scenarios?

You test prompt independence by generating supportive, neutral, and competing scenarios from documented rules, executing them against an agent, and comparing the resulting tool-call traces for consistent behavioral compliance.

Does skill-comply work with stream-json outputs from claude -p?

Yes, skill-comply integrates directly with claude -p stream-json outputs, capturing tool-call traces during scenario execution to classify events and enforce temporal ordering for compliance measurement.

How do I generate a compliance report for TDD workflows and linting rules?

You generate compliance reports by extracting expected behavioral sequences from TDD or linting rule Markdown files, executing pressure-testing scenarios, and emitting a self-contained Markdown report summarizing compliance rates.

What are the limitations of using LLM-based classification for agent compliance?

LLM-based classification depends on stream-json tool-call traces and deterministic temporal ordering checks, meaning compliance measurement is limited to observable tool events rather than internal agent reasoning processes.