Agent skill · data analytics · affaan-m
skill-comply
Visualize whether skills, rules, and agent definitions are actually followed — auto-generates scenarios at 3 prompt strictness levels, runs agents, classifies behavioral sequences, and reports compliance rates with full tool call timelines. Use when checking whether agents actually follow the skills, rules, and definitions they were given, rather than assuming they do.
Why this skill is useful
Adds executable scripts for automated compliance measurement and reporting that extend the AI's capabilities in verifying adherence to defined skills and rules.
What it needs
Requires bash installed locally. About 1k tokens when loaded. Last updated 2026-08-06. 238,342 stars on the source repository.
What this skill does
skill-comply: Automated Compliance Measurement Measures whether coding agents actually follow skills, rules, or agent definitions by: 1. Auto-generating expected behavioral sequences (specs) from any .md file 2. Auto-generating scenarios with decreasing prompt strictness (supportive → neutral → competing) 3. Running claude -p and capturing tool call traces via stream-json 4. Classifying tool calls against spec steps using LLM (not regex) 5. Checking temporal ordering deterministically 6. Generating self-contained reports with spec, prompts, and timelines Supported Targets Skills (skills//SKILL.md): Workflow skills like search-first, TDD guides Rules (rules/common/.md): Mandatory rules like testing.md, security.md, git-workflow.md Agent definitions (agents/.md): Whether an agent gets invoked when expected (internal workflow verification not yet supported) When to Activate User runs /skill-comply <path> User asks "is this rule actually being followed?" After adding new rules/skills, to verify agent compliance Periodically as part of quality maintenance Usage Key Concept: Prompt Independence Measures whether a skill/rule is followed even when the prompt doesn't explicitly support it. Report Contents Reports are self-contained and include: 1. Expected behavioral sequence (auto-generated spec) 2. Scenario prompts (what was asked at each strictness level) 3. Compliance scores per scenario 4. Tool call timelines with LLM classification labels Advanced (optional) For users familiar with hooks, reports also include hook promotion recommendations for steps with low compliance. This is informational — the main value is the compliance visibility itself.
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills affaan-m/skill-comply--4b477a