attest

Execute an interactive attestation workflow for .goal-contract.yml and record JSON attestations.

Updated Apr 22, 2026
One-click install
npx skills add https://github.com/ValescoAgency/flightplan --skill attest-valescoagency
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: attest
Source: https://github.com/ValescoAgency/flightplan/tree/main/attest
Command: npx skills add https://github.com/ValescoAgency/flightplan --skill attest-valescoagency

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Walk humans through the AFK attestation checklist for a .goal-contract.yml and write an attestation record to gate the afk-ready process.

Core Features & Use Cases

  • Interactive, tiered checklist rendering based on the contract's metadata.
  • Validates the contract against the attestation schema and records attestation metadata for audit.
  • Writes a structured .afk/attestations/<linearIssueId>.json record and helps teams enforce governance.

Quick Start

Run the attest workflow against the current repo's .goal-contract.yml to generate the attestation record.

Frequently Asked Questions about attest

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

FAQPage Schema
How do I generate an attestation record for a goal contract?

To generate an attestation record, run an interactive workflow against your repository's .goal-contract.yml file to validate the contract schema, capture attester metadata, and write the output to .afk/attestations.

What is contract governance attestation and when do I need it?

Contract governance attestation validates a .goal-contract.yml file against an attestation schema to gate the afk-ready label, preventing drift between the YAML contract and its recorded approval metadata.

How do I enforce an afk-ready gate on my repository?

Enforce an afk-ready gate by running the attestation workflow to validate your .goal-contract.yml, which computes the attestedContentSha and persists a structured JSON record for audit compliance.

Does the attestation workflow require any external dependencies?

The attestation workflow operates with no external dependencies, requiring only a .goal-contract.yml file in the current repository to execute the interactive checklist and persist the JSON record.

How does the attestation process prevent YAML contract drift?

The attestation process prevents YAML contract drift by computing an attestedContentSha during validation, linking the .goal-contract.yml content directly to its persisted JSON record for audit verification.

Can I customize the attestation checklist for different contract metadata?

The attestation checklist renders interactively with tiered levels based on the .goal-contract.yml metadata, allowing the workflow to adapt dynamically to the specific contract configuration during validation.