Skip to content

BumpyClock/agent-templates / skills_archive/behavior-validator

behavior-validator

Verified

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

FileKindSize
SKILL.mdskill md3.7 KB
agents/openai.yamlconfig232 B
references/contract-template.mdmarkdown1.4 KB
references/report-schema.mdmarkdown1.4 KB

references/report-schema.md

View on GitHub
# Behavior Validator Report Schema

Use this JSON shape when the orchestrator needs machine-readable behavior validation output.

```json
{
  "overall_behavior": "satisfies_contract",
  "overall_confidence": 0.9,
  "target": {
    "type": "web app",
    "access": "http://localhost:3000"
  },
  "checks": [
    {
      "contract_clause": "User task 1",
      "status": "pass",
      "severity": null,
      "evidence": "Created an invoice, refreshed the page, and saw it remain in the invoice list.",
      "reproduction_steps": [
        "Open /invoices",
        "Click Create",
        "Submit valid invoice fields",
        "Refresh /invoices"
      ],
      "confidence": 0.9
    }
  ],
  "anti_cheat_probes": [
    {
      "probe": "Changed fixture amount and refreshed dashboard",
      "result": "Dashboard total updated from 120 to 180"
    }
  ],
  "blockers": []
}
```

Allowed `overall_behavior` values:

- `satisfies_contract`
- `violates_contract`
- `blocked`

Allowed check `status` values:

- `pass`
- `fail`
- `blocked`
- `out_of_scope`

Use `severity` only for `fail` checks; use `null` otherwise. Use `fail` for observable contract violations, including static or fake behavior. Use `blocked` only when runtime access or required test inputs are unavailable. Redact credentials, tokens, cookies, private user data, and unrelated log content from every evidence field.
receiving-code-reviewobra/superpowersUse when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical rigor and verification, not performative agreement or blind implementationStars: 319kUpdated Claude CodeCodexVerifiedInstall
requesting-code-reviewobra/superpowersUse when completing tasks, implementing major features, or before merging to verify work meets requirementsStars: 319kUpdated Claude CodeCodexVerifiedInstall
using-git-worktreesobra/superpowersUse when starting feature work that needs isolation from current workspace or before executing implementation plans - ensures an isolated workspace exists via native tools or git worktree fallbackStars: 319kUpdated Claude CodeCodexVerifiedInstall
verification-before-completionobra/superpowersUse when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence before assertions alwaysStars: 319kUpdated Claude CodeCodexVerifiedInstall