verify / default

Verify entity-bootstrap receipts for existence, YAML frontmatter, provenance, and stage trail integrity.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/Collectively-Gary/GaryOS --skill verify-default
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: verify / default
Source: https://github.com/Collectively-Gary/GaryOS/tree/main/data/skills/verify/default
Command: npx skills add https://github.com/Collectively-Gary/GaryOS --skill verify-default

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill prevents silent corruption in GaryOS actions by verifying that every entity-bootstrap receipt matches the on-disk entity file and its stage trail.

Core Features & Use Cases

  • Verifies entity-bootstrap receipts for each external_refs entry (kind: file, subkind: entity-bootstrap) by checking file existence, YAML frontmatter validity, and provenance correctness.
  • Confirms audit-trail integrity by ensuring the expected stages/NNN-*.md witness exists for the action touch event (bootstrap or touch).
  • Validates merge redirect tombstones when the receipt includes redirect metadata, ensuring the tombstone chain terminates correctly, matches the declared hop count, and respects the cap.
  • Escalates to the operator only on structural failures by setting awaiting_operator gates with precise recovery options.

Quick Start

Ask your system to run verify/default to confirm that the entity-bootstrap receipts produced by commit are structurally correct and fully auditable.

Frequently Asked Questions about verify / default

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

FAQPage Schema
How do I verify entity-bootstrap receipts and validate their YAML frontmatter provenance?

Verify entity-bootstrap receipts by checking file existence, validating YAML frontmatter structure, and confirming provenance correctness for each external_refs entry. It ensures on-disk entity files match their stage trail.

What is the best way to audit tombstone redirect chains for entity bootstrap files?

Audit tombstone redirect chains by re-walking merged tombstones to the receipt ref, validating that the chain terminates correctly, matches the declared hop count, and respects the configured cap constraints.

How do I confirm audit-trail integrity for stage witness files after a bootstrap action?

Confirm audit-trail integrity by ensuring the expected stages/NNN-*.md witness file exists for the action touch event. This validates the complete stage trail entry for bootstrap or touch operations.

Do I need a playbook-specific verify recipe to validate entity-bootstrap receipts?

No playbook-specific verify recipe is needed. This skill applies across any playbook lacking a specific recipe, including the fallback playbook: other, and also supports re-verification referenced by per-playbook skills.

Why does workflow validation escalate to an operator gate on structural failures?

Workflow validation escalates to operator gates by setting awaiting_operator flags only on structural failures. This provides precise recovery options when entity-bootstrap receipts are corrupted or missing required audit trails.

Can I use a default fallback to re-verify receipts previously checked by playbook-specific skills?

Yes, the default fallback supports re-verification referenced by per-playbook verify skills. This allows you to re-check entity-bootstrap receipts even after a playbook-specific validation has already run.