Use when the user asks to "audit our launch plan", "are we ready to launch", or evaluate launch execution/outcomes; runs one typed RAMP preflight, execution, or outcome profile without mixing time horizons. Not for recording launch state — use launch-registry; not for running launch day — use launch-day-conductor. 发布就绪审计/RAMP分阶段评估/发布前放行
81%
Does it follow best practices?
Run evals on this skill
Adds up to 20 points to the overall score
Low
Low-risk findings worth noting
Audit one launch at one lifecycle read. Preflight evaluates readiness/assets plus planned policy and instrumentation red lines; execution evaluates observed launch-window operation; outcome evaluates post-lag proof. There is no cross-time composite.
Run RAMP preflight for launch alpha against the registry stage, canon, claims, rules, and event QA.
Run the outcome profile at day 30; keep it separate from the preflight result.Reads: one launch, one lifecycle read, registry/canon/claims state, and profile-specific evidence. Writes: only a permissioned v3 artifact. Done when: the selected profile is complete or its exact Unknowns are reported, with no launch execution or registry mutation.
launch-registry owns stage/date/embargo facts. launch-day-conductor executes the runbook. This auditor only judges the frozen evidence.
| Need | Preferred evidence |
|---|---|
| Stage/access | Projected launch record plus direct access/eligibility check |
| Narrative/claims | Canon version, claims projection, rendered assets |
| Operations/rules | Launch plan, commitments, dated official platform rules |
| Instrumentation | Verified events/UTMs and destination truth checks |
| Execution | Timestamped action/incident/response evidence |
| Outcomes | Own analytics/CRM/store truth after declared lag |
../../../references/auditor-runbook.md../../../references/scoring-semantics.md../../../references/ramp-benchmark.md../../../references/runtime-invocation.mdreferences/auditor-runtime.mdRead the declared root runtime sources and selected framework/catalog entry.
Standalone installs use the bundled immutable references/auditor-runtime.md;
never fetch mutable main or guess missing policy. Before deterministic calls,
follow runtime-invocation.md and resolve
AARON_SKILLS_ROOT="${CLAUDE_PLUGIN_ROOT:-$(git rev-parse --show-toplevel 2>/dev/null || true)}".
Require the scorer, validator and typed catalogs. If unavailable, collect the
selected profile's typed observations and Unknowns, but return
score_state: NOT_SCORED / score_confidence: not_scored without a gate verdict
or persistent artifact. Record the bound schema, runbook and catalog versions.
Declare profile/lifecycle read (preflight|execution|outcome), target launch, launch type, market, access model, observation date, and evidence window.
Every observed state needs source/date/type/confidence. Missing applicable evidence is Unknown; catalog-authorized conditional items may be N/A with reason. Run python3 "$AARON_SKILLS_ROOT/scripts/rubric-score.py" score <run.json> on the selected typed profile.
Verify profile-relevant vetoes: RAMP-R1 stage/access contradiction, RAMP-A1 material claim/disclosure failure, RAMP-M1 planned or observed manipulation/embargo/platform violation, and RAMP-P1 demonstrably broken instrumentation on participating surfaces.
DONE/SHIP, final 80.DONE_WITH_CONCERNS/FIX, final 59.DONE/BLOCK, no final score.NEEDS_INPUT/UNDECIDED, no score.State lifecycle read with every result. On trace request, qualify RAMP-R1/A1/M1/P1, especially against colliding ROAS IDs.
Begin with the auditor-runbook's exact typed conversation header. Never replace
status, verdict, or score_state with prose; list each explicitly missing
qualified item as ``ID: `unknown``` before findings.
Lead with lifecycle-specific verdict, target/context/date, score or coverage/interval, confidence, profile detail, linked prior reads, critical evidence, Unknowns, and fix/rerun owner. A preflight SHIP authorizes no external launch action by itself; explicit execution approval remains required.
Persist only after explicit authorization to memory/audits/launch/YYYY-MM-DD-<topic>.md. Preserve the scorer's orthogonal status and verdict; validate the complete v3 draft with validate-audit-artifact.py against the intended relative path, persist only through one full-content Write, and revalidate the target per the auditor runbook. Edit/shell/MCP mutations of the reserved sink are unsupported. Create separate files for separate lifecycle reads and link them by launch ID rather than overwriting.
aaron-he-zhu/aaron-marketing-skills
ffc23e6
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.