preflight-checks_skill

This skill verifies AI agent behavior against memory rules through automated pre-flight checks, ensuring consistency and detecting drift after updates.
  • Python

2.5k

GitHub Stars

5

Bundled Files

2 months ago

Catalog Refreshed

4 months ago

First Indexed

Readme & install

Copy the install command, review bundled files from the catalogue, and read any extended description pulled from the listing source.

Installation

Preview and clipboard use veilstrat where the catalogue uses aiagentskills.

npx veilstrat add skill openclaw/skills --skill preflight-checks

  • _meta.json285 B
  • CHANGELOG.md1.2 KB
  • package.json728 B
  • README.md2.8 KB
  • SKILL.md9.9 KB

Overview

This skill provides test-driven behavioral verification for AI agents to detect silent degradation when memory loads but learned behaviors are not applied. It adds scenario-based checks and canonical answers so agents can self-test after memory updates, restarts, or configuration changes. The result is objective pass/fail reporting and actionable feedback to restore expected behavior.

How this skill works

Define a set of scenario checks and expected answers in human-readable CHECKS and ANSWERS files. On startup or on demand, the agent reads the checks, answers each scenario, and compares its responses to the expected answers to produce a score and failure report. Scripts and templates automate initialization, adding new checks, and running the full suite; optional automation integrates checks into CI or session workflows.

When to use it

  • After session restart or when bootstrapping a persistent-memory agent
  • Immediately after memory updates or rule changes
  • When testing agent behavior after software updates or refactors
  • During onboarding of new agent instances or profiles
  • On demand whenever behavior consistency is uncertain

Best practices

  • Write scenario-based checks that test behavior, not trivia or raw recall
  • Include explicit wrong answers to make drift detection precise
  • Group checks into categories (Identity, Core Behavior, Communication, Anti-Patterns)
  • Keep a living ANSWERS file as the canonical behavioral reference
  • Run checks automatically on critical lifecycle events and in CI for regressions

Example use cases

  • Detect an agent that loads a tool list into memory but fails to auto-save new tools
  • Verify behavioral rules after merging a code change that touches decision logic
  • Run nightly or pre-release behavioral checks in CI to catch regressions
  • Onboard a new agent profile with role-specific PRE-FLIGHT-CHECKS files
  • Automatically trigger reloading and retesting when score drops below threshold

FAQ

Aim for 15–25 checks across key categories, with 3–5 checks per category to cover common and risky behaviors.

What happens when a check fails?

The system reports failed checks and reasons; follow the scoring guide—minor drift prompts review, larger drift triggers memory reload and retest.

Can this run automatically in CI?

Yes. Use the provided run scripts or an auto-test harness to execute checks as part of your CI workflow.

Built by
VeilStrat
AI signals for GTM teams
© 2026 VeilStrat. All rights reserved.All systems operational