Menu

Individual skill

behavior-validator

0upvotes

Source-blind user behavior validation against a prewritten contract for apps, CLIs, APIs, and generated artifacts.

skills/behavior-validator/SKILL.md

Read pinned source

Source commit 02f3158379a7ec355d73c92bf97d432fafb2adc9

What was checked

Matches the observed repository HEAD
Yes
Scanner rules are current
No
Repository scan complete
No
Skill scan complete
No
Observed behavior
Not checked yet
Last checked
Nov 6, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings)
1,117
Repository last updated
Nov 8, 2026
License
MIT

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files
Read excerpt

# Behavior Validator

Validate observable behavior without inspecting source. Use this as the black-box companion to code-aware review: `autoreview` judges the change bundle, while `behavior-validator` judges the running product, CLI, API, or generated artifact against a behavior contract.

## Contract

- Read the behavior contract first. If none exists, write a short one from the user request before testing. See `references/contract-template.md`.
- Stay source-blind. Do not inspect source files, diffs, tests, git history, implementation notes, build internals, or review bundles.
- Interact only through user-visible or operator-visible surfaces: browser, CLI, API, generated files, public logs, screenshots, accessibility trees, or documented runtime output.
- Treat implementation-looking evidence as contamination. If source access is required to continue, stop and report `blocked_source_required`.
- Report findings against contract clauses and observable steps, not code locations.
- Do not mark a workflow as passing until each relevant contract clause is pass, fail, blocked, or out of scope.

## Isolation
Back to top