Skill

verification-slots

This skill should be used when the user asks about "verification slots", "integrating a linter", "adding a deterministic tool", "harness-enforcer", "constraint enforcement interface", "wrapping a tool", or needs the technical reference for how deterministic and agent-based checks work in the harness framework.

From ai-literacy-superpowers

Install

Run in your terminal

npx claudepluginhub russmiles/ai-literacy-superpowers --plugin ai-literacy-superpowers

Tool Access

This skill uses the workspace's default tool permissions.

Supporting Assets

View in Repository

references/tool-integration.md

Skill Content

Similar Skills

skill-lookup

Searches, retrieves, and installs Agent Skills from prompts.chat registry using MCP tools like search_skills and get_skill. Activates for finding skills, browsing catalogs, or extending Claude.

prompts.chat

157.5k

prompt-lookup

Searches prompts.chat for AI prompt templates by keyword or category, retrieves by ID with variable handling, and improves prompts via AI. Use for discovering or enhancing prompts.

prompts.chat

157.5k

agent-payment-x402

Enables AI agents to execute x402 payments with per-task budgets, spending controls, and non-custodial wallets via MCP tools. Use when agents pay for APIs, services, or other agents.

ecc

140.3k

Stats

Stars1

Forks0

Last CommitMar 30, 2026

Actions

View Source View Plugin View on GitHub View README

Verification Slots

The verification slot is the harness framework's core technical abstraction. Every constraint — whether backed by a linter, a formatter, a structural test, or an LLM agent — is checked through the same interface. This uniformity means the rest of the system (hooks, CI, commands) does not care how a constraint is verified.

The Contract

Input:

Constraint definition (rule, enforcement type, tool)
Scope (commit, pr, weekly, manual)
File set (changed files, or all files)

Output:

Result: pass or fail
Findings: list of {file, line, message} (empty on pass)

How the Enforcer Decides

The harness-enforcer agent reads each constraint from HARNESS.md and dispatches verification based on the enforcement field:

Enforcement	What happens
`deterministic`	Execute the `tool` command, interpret exit code
`agent`	Read the `rule` text, review files, produce findings
`deterministic + agent`	Run both, merge findings
`unverified`	Skip — log as unchecked

Deterministic Tool Integration

To fill a verification slot with a deterministic tool:

Identify a tool that checks the constraint (linter, formatter, scanner, custom script)
Verify it runs locally and produces usable output
Update the constraint in HARNESS.md: set enforcement to deterministic and tool to the exact command
Run /harness-audit to confirm the tool works in the harness context

For detailed integration patterns for common tools (ESLint, Prettier, gitleaks, ArchUnit, custom scripts), consult references/tool-integration.md.

Agent-Based Verification

When no deterministic tool exists, the enforcer reads the constraint's prose rule and reviews code against it. The output format is identical to deterministic verification — pass/fail with file:line findings.

Agent-based checks are:

Flexible — work with any constraint that can be described in prose
Non-deterministic — may give different results on identical input
Token-intensive — each check costs LLM inference
Nuance-aware — can evaluate intent and context, not just syntax

Mixed Enforcement

Some constraints benefit from both levels. For example, a linter checks that doc comments exist (deterministic presence check) while the agent reviews that comments explain reasoning rather than restating signatures (quality check).

Use deterministic + agent in the enforcement field and list both tools.

Additional Resources

Reference Files

references/tool-integration.md — Step-by-step integration patterns for linters, formatters, type checkers, secret scanners, structural test frameworks, and custom scripts