verify / task

Verify task playbook outputs and validate entity-merge receipts.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill validates that a completed playbook task produced the right artifacts and, for entity-merge tasks, that the merge receipts are consistent and complete.

Core Features & Use Cases

  • Generic task verification: Confirms local file existence and well-formedness for file-based outputs, and re-fetches external deliveries to confirm receipts.
  • Entity-merge doctrine verification: Ensures the merge tombstone and winner receipt are both present, validates tombstone strip-discipline and chain resolution, checks stage migration counts, alias extensions, loser-stage cleanup, and the presence of a native winner merge-stage trail.
  • Gate-backed failure handling: Uses operator gates to address missing or inconsistent receipts rather than silently succeeding.

Quick Start

Ask an operator to verify the commit results for playbook: task by running the verify/task Skill and resolving any awaiting_operator gates if receipt data or invariants are incomplete.

Frequently Asked Questions about verify / task

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

FAQPage Schema
How do I verify entity-merge receipts and tombstone correctness for completed tasks?

Verify entity-merge receipts by checking that merge tombstones and winner indices are present, validating tombstone strip-discipline, chain depth, migrated stages, alias extensions, loser cleanup, and native merge-stage trail presence.

What is task output validation for YAML frontmatter and playbook actions?

Task output validation confirms completed playbook actions produced correct artifacts by parsing local or externally referenced files, checking well-formedness, and re-fetching external deliveries to confirm receipt consistency.

How do I check audit trail consistency when merging entities with external references?

Check audit trail consistency by dispatching to verify default behaviors when entity-bootstrap receipts apply, enforcing strict binary gate checks on chain resolution, stage migration counts, and native winner merge-stage trails.

Why does task validation fail silently instead of reporting missing merge receipts?

Task validation does not fail silently; it uses operator gates to address missing or inconsistent receipts and pauses execution with an awaiting_operator state rather than returning a false success.

Does generic task verification work with both local files and external delivery receipts?

Generic task verification works with both local files and external deliveries, confirming local file existence and well-formedness while re-fetching external artifacts to validate their receipt data.

What are the limitations of binary gate checks for entity-merge tombstone validation?

Binary gate checks enforce strict pass or fail conditions for tombstone correctness and chain resolution, meaning any incomplete invariant data or missing merge-stage trails will halt the process pending operator resolution.