Overview

A quest (long-running task) skill package distills the complete playbook for a recurring class of multi-step data analysis tasks: decomposing them into analysis objectives, executing them in order, and producing tables, charts, and conclusion-style reports. A qualified quest skill package consists of four layers of knowledge:

1. Table manuals (tables/*.yaml): one file per table, capturing field truth and the semantic model (columns/dimensions/measures) — the factual foundation on the data side;
2. Metric manuals (metrics/METRIC-NNN.yaml): one file per metric, capturing the three-level calculation semantics of field → measure → metric; this is the single authoritative source of calculation definitions for the whole skill package;
3. Analysis knowledge (objectives/ + SKILL.md + approach.md): an execution manual per analysis objective plus the top-level guide; each objective file declares its gates and metric dependency contract in YAML frontmatter;
4. Report requirements (report/, recommended joint production): text report requirements (text_report.md) and web report template packages (web_report/), linked to the gates of each objective — every piece of material the report needs must be covered by the output of some gate.

This skill is a meta-skill: it does not analyze any business data. Instead, it guides you in creating skill packages with the structure above — what goes in each file, what the formats look like, and what gates must pass for the package to qualify.

Recommended joint production (both directions): when the skill package has reporting requirements, produce the report/ deliverables together with it (template and gates designed as one, data from a single source); when the user only wants a report template, produce in the reverse direction as a "minimal skill shell" (a data-supply objective + template package, with almost no analysis constraints) — see the "Reverse production" section of references/report-structure.md.

When to Use