skills.rest
venikman
venikmanCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

workflow/parse-handoff

Parse handoff YAML files into canonical JSON validated against the U.AgentHandoff schema.

Updated Jan 11, 2026
Search Tags:#workflow#validation#json#yaml#handoff#telemetry
One-click install
npx skills add https://github.com/venikman/fpf-foundry --skill workflow-parse-handoff
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: workflow/parse-handoff
Source: https://github.com/venikman/fpf-foundry/tree/main/design/skills/workflow/parse-handoff
Command: npx skills add https://github.com/venikman/fpf-foundry --skill workflow-parse-handoff

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill eliminates the manual, error-prone process of turning handoff artifacts into a single canonical JSON representation, enabling consistent auditability and downstream automation.

Core Features & Use Cases

  • Parse: Convert a handoff YAML into a strict object model for validation.
  • Validate: Enforce the U.AgentHandoff schema to catch malformed inputs.
  • Output: Write a canonical JSON artifact to a deterministic location for reproducible reviews.
  • Telemetry: Emit a U.Work log when telemetry/log-work integration is available for auditing handoffs.

Quick Start

Run the parse-handoff skill against a handoff YAML file to produce a parsed JSON artifact. Example: provide the handoff_path and optionally an output_path to control where the JSON is written.

Frequently Asked Questions about workflow/parse-handoff

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

FAQPage Schema
How do I convert a handoff YAML file into a standardized JSON format?▼

To convert a handoff YAML file into a standardized JSON format, parse it using strict validation against the U.AgentHandoff schema to produce a canonical JSON artifact written to a deterministic output location.

Why does handoff YAML validation fail against the U.AgentHandoff schema?▼

Handoff YAML validation fails when the input is malformed and does not strictly match the U.AgentHandoff schema, which this process enforces to catch errors before generating a canonical JSON representation.

What is the best way to automate handoff artifact parsing for consistent audits?▼

The best way to automate handoff artifact parsing for consistent audits is to validate the YAML against the U.AgentHandoff schema and write a deterministic canonical JSON output, while emitting a U.Work log when telemetry is available.

Can I specify a custom output path when parsing handoff YAML to JSON?▼

Yes, you can specify a custom output path when parsing handoff YAML to JSON by providing the output_path parameter, otherwise the canonical JSON artifact is written to a default deterministic location.

Does handoff YAML parsing require telemetry integration to emit a U.Work log?▼

Handoff YAML parsing does not require telemetry integration to produce JSON, but it will emit a U.Work log for auditing purposes only when telemetry or log-work integration is available in the environment.

When do I need to canonicalize handoff artifacts into JSON?▼

You need to canonicalize handoff artifacts into JSON when downstream automation or reproducible reviews require a strict, standardized object model instead of raw YAML, ensuring consistent auditability across workflows.

Related Skills

Explore More Software Engineering Skills→
venikmanvenikman

workflow/respond-to-approval

Record structured approval responses to markdown files under runtime contexts.

Community
Intermediate
michael-conradmichael-conrad

issue-review

Route GitHub issue reviews to downstream skills via triage rules.

Community
Advanced
venikmanvenikman

governance/define-roc

Generate a Rule of Constraints YAML policy bundle for agent governance.

Community
Intermediate
GoosLabGoosLab

moai-formats-data

Reduce JSON payloads and parse TOON-encoded data for LLM workflows.

Community
Advanced