lofn-qa

Audit Lofn creative runs and classify them as ship, repair, or fail.

19|1|Updated Mar 26, 2024
One-click install
npx skills add https://github.com/LocalSymmetry/lofn --skill lofn-qa
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: lofn-qa
Source: https://github.com/LocalSymmetry/lofn/tree/main/.agents/skills/lofn-qa
Command: npx skills add https://github.com/LocalSymmetry/lofn --skill lofn-qa

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill audits completed Lofn creative pipeline outputs and determines whether they meet the strict quality gates required to ship, need repair, or must fail.

Core Features & Use Cases

  • Adversarial QA Review: Validates image, music, video, and story runs against modality-specific gate checklists.
  • Integrity Checks: Confirms pipeline continuity, prompt structure, evidence capture, and repair routing for partial or suspicious runs.
  • Decision Support: Produces a clear SHIP, REPAIR, or FAIL verdict with concise guidance for the next action.
  • Use Case: Use it after an automated Lofn generation run to catch structural breaks, missing continuity, or low-quality outputs before delivery.

Quick Start

Ask the skill to audit the latest Lofn run directory and return a SHIP, REPAIR, or FAIL verdict with the required repair brief.

Frequently Asked Questions about lofn-qa

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

FAQPage Schema
How do I validate automated creative pipeline outputs before delivery?

To validate creative pipeline outputs before delivery, audit completed runs against modality-specific gate checklists to verify continuity, prompt structure, and evidence capture, producing a clear ship, repair, or fail verdict.

What is adversarial QA review for generative media pipelines?

Adversarial QA review for generative media pipelines is the process of validating image, music, video, and story outputs against strict gate checks to catch structural breaks, missing continuity, or low-quality runs before they ship.

How do I audit a creative run directory and get a ship or fail verdict?

You can audit a creative run directory by applying strict gate checks for pipeline continuity, modality structure, and repair routing, which returns a concise ship, repair, or fail verdict with guidance for the next action.

Does pipeline QA validation work for partial or suspicious generation runs?

Pipeline QA validation does work for partial or suspicious generation runs by applying adversarial validation to verify package integrity, checking prompt structure and evidence capture to determine if the output needs repair or must fail.

When should I use automated gating for creative generation pipelines?

You should use automated gating for creative generation pipelines immediately after an automated run to catch structural breaks, missing continuity, or low-quality outputs before delivery, ensuring package integrity across all media modalities.