Skip to content

SKILL.md

Latest commit

 

History

History
39 lines (26 loc) · 1.82 KB

SKILL.md

File metadata and controls

39 lines (26 loc) · 1.82 KB
Raw
name creative-performance-readout
description Use when you need creative readout and next-test backlog to separate creative signal from tracking, spend, audience, and conversion-path noise.

creative performance readout

Quick Start

  • Produce creative readout and next-test backlog.
  • Read references/pattern.md before drafting; it contains product mechanics, required inputs, decision rules, artifact fields, QA checks, failure modes, proof metrics, and an example prompt.

Skill-Specific Checklist

  • Anchor the artifact around these fields: asset, audience, spend context, tracking confidence.
  • Use the artifact to decide: Which variable changes in the next creative test.
  • Do not mark ready until: Each creative variant changes one declared variable or is marked exploratory.

Workflow

  1. Confirm the requested artifact, target audience, and review owner.
  2. Gather only the missing high-risk inputs; infer low-risk defaults and label assumptions.
  3. Apply the relevant decision rules and artifact template from references/pattern.md.
  4. Return the artifact with QA checks, failure modes, proof metric, and next action.

Output Contract

Return creative readout and next-test backlog. Include the decision supported, required inputs, generated artifact, QA checks, failure modes, proof metric, and next action.

Boundary

Use another skill if the final artifact is not creative readout and next-test backlog, the main decision is outside ad-creative-generation, campaign-analytics-qa, or the user only needs broad strategy.

Guardrails

  • Keep private evidence identities and unpublished links out of repo-facing output.
  • Separate observed evidence, inference, and recommended action.
  • Ask for missing high-risk inputs before producing launch-ready work.
  • Keep the artifact narrow enough to execute or review today.