aoa-quest-harvest

Evaluate repeated quest-shaped harvests and emit promotion receipts.

4|Updated Mar 18, 2026
One-click install
npx skills add https://github.com/8Dionysus/aoa-skills --skill aoa-quest-harvest
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: aoa-quest-harvest
Source: https://github.com/8Dionysus/aoa-skills/tree/main/.agents/skills/aoa-quest-harvest
Command: npx skills add https://github.com/8Dionysus/aoa-skills --skill aoa-quest-harvest

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This skill automates the governance decision process for repeated quest-shaped work by evaluating evidence and routing to the correct downstream surface (quest, skill, playbook, or other owner surfaces), ensuring decisions are explicit and auditable.

Core Features & Use Cases

  • Structured triage: collects bounded, reviewed harvest input and determines promotion targets based on repeatability and surface fit.
  • Explicit receipts: emits promotion receipts and kernel telemetry for closed triage.
  • Auditability: keeps nearest wrong targets visible and preserves evidence linkage for traceability.

Quick Start

Provide a bounded harvest packet with repeat shape and current owner surface to initiate the triage.

Frequently Asked Questions about aoa-quest-harvest

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

FAQPage Schema
How do I decide whether to promote a repeated workflow pattern to a higher surface?

To decide workflow pattern promotion, you triage bounded, reviewed harvest packets to evaluate repeatability and surface fit, yielding an explicit promotion verdict and identifying the next artifact.

What is a quest promotion receipt in telemetry-driven governance?

A quest promotion receipt is a telemetry record emitted during governance triage to explicitly document the decision outcome when routing repeated quest-shaped work to downstream owner-repo surfaces.

How do I automate triage for repeated quest patterns across owner-repo surfaces?

You automate triage by providing a bounded harvest packet with the repeat shape and current owner surface, which the system evaluates to route work to the correct downstream surface.

What do I need to provide to initiate quest pattern triage?

To initiate quest pattern triage, you must provide a bounded harvest packet containing the repeat shape and the current owner surface, ensuring strict boundaries and telemetry requirements are met.

When should I avoid promoting a quest pattern to a higher surface?

You should avoid promotion when the triage evidence lacks sufficient repeatability or fails the surface fit evaluation, meaning the pattern should stay a quest rather than advancing to a skill or playbook.

How does quest pattern triage compare to manual workflow governance?

Quest pattern triage automates governance decisions by enforcing strict boundaries and telemetry requirements, whereas manual workflow governance lacks explicit receipts and auditable evidence linkage for traceability.