run-attested

Trigger the AFK runner for attested contracts and stream audit output.

Updated Apr 22, 2026

Search Tags:#docker #end-to-end #manual-testing #attestation #dogfood #run-attested #afk-runner

Ready to run

npx skills add https://github.com/ValescoAgency/flightplan --skill run-attested

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: run-attested
Source: https://github.com/ValescoAgency/flightplan/tree/main/run-attested
Command: npx skills add https://github.com/ValescoAgency/flightplan --skill run-attested

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Manually initiate an end-to-end dogfooding run against an already-attested goal-contract to validate the AFK runner in a controlled environment.

Core Features & Use Cases

Orchestrates a manual dispatch to @valesco/afk-runner for attested contracts.
Streams audit output to surface verdicts and branch state for post-run review.
Enforces preconditions (contract presence, matching attestation, signing keys, and local Docker readiness) before execution.

Quick Start

Prepare the repo by ensuring a matching .afk/attestations/<id>.json exists and then run this skill to dispatch the attested contract.

Frequently Asked Questions about run-attested

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I run an attested contract for end-to-end testing?▼

To run an attested contract for end-to-end testing, trigger the AFK runner against your existing contract. The process validates preconditions, checks for a matching .afk/attestations/<id>.json, and streams the audit output for real-time monitoring.

What is an attested contract dogfooding run?▼

An attested contract dogfooding run is a manual end-to-end validation process that exercises the AFK runner against an already-attested goal-contract in a controlled environment to verify behavior and surface verdicts.

What prerequisites do I need to validate before running an attested contract?▼

Before running an attested contract, you need a matching .goal-contract.yml, a corresponding attestation record in .afk/attestations/, valid signing keys, and local Docker readiness. The preflight checks enforce these conditions before execution.

How do I monitor audit output during an end-to-end runner execution?▼

To monitor audit output during runner execution, tail the audit stream which surfaces real-time verdicts and branch state. This allows immediate post-run review of the dogfooding execution against the attested contract.

Why does my attested contract run fail the preflight checks?▼

Attested contract runs fail preflight checks when the .goal-contract.yml is missing, the matching attestation record in .afk/attestations/ cannot be found, signing keys are invalid, or local Docker is not running or ready for execution.