What problem does it solve? Publishing HTML artifacts (reports, guides, agent outputs) to the soli-frames viewer requires a strict, safe dispatch process: misconfigured payloads cause GitHub API 422 errors, oversized files get rejected, and outward-facing actions need human approval. This Skill enforces a five-phase protocol that validates configuration, classifies egress risk, and gates every dispatch behind explicit human confirmation. ## Core Features & Use Cases - Five-phase dispatch pipeline: Pre-flight + Egress Check, Build Payload, Validate, Human Gate, and Dispatch + Log, each with explicit STOP conditions. - Egress classification (R.CS4): Blocks analytics reports containing sensitive per-actor or rate-card data before any external call. - Strict payload contract: Builds the nested event_type/client_payload JSON with base64-encoded HTML, slug regex validation, and size limits (100 KB hard cap). - Mandatory human gate (R.CS3): Shows a dispatch summary and requires explicit confirmation; supports --dry-run for payload inspection without sending. - Use Case: After generating a sprint report HTML, run the protocol to validate the slug, check the 80 KB warning threshold, review the summary, and dispatch it to soli-frames as a draft pending merge. ## Quick Start Ask the agent to share the generated HTML report to soli-frames using the content share protocol with the dry-run flag first to inspect the payload.
