| name | launch-asset-packager |
| slug | aaron-launch-asset-packager |
| displayName | Launch Asset Packager · 发布资产打包 |
| summary | 资产清单/press kit/商店listing规格/上线检查 |
| description | Use when the user asks to "package the launch assets", "build a press kit", or "prep the store listing and go-live checklist"; produces a tier-scoped launch asset manifest with production status — a press kit spec (factsheet, description, history, features, videos, images, logo and icon, awards, contact), demo script and screenshot specs, a launch FAQ, dual-store listing metadata drafts against the official character budgets (per App Store Connect / Play Console documentation), and a technical go-live checklist manifest (robots flip, sitemap, OG tags, analytics verification — execution stays with technical-seo-checker and serp-markup-builder). Not for the message copy itself — use message-house-builder or content-writer; not for landing page UX — use landing-optimizer; not for keyword research beyond the store surfaces — use keyword-research. 发布资产打包/press kit/商店listing规格/上线检查清单 |
| version | 19.2.0 |
| license | Apache-2.0 |
| compatibility | Claude Code and compatible agent-skill hosts |
| homepage | https://github.com/aaron-he-zhu/aaron-marketing-skills |
| when_to_use | Use when assembling the asset kit for a declared launch tier: the manifest with owners and production status, press kit sections per the presskit() convention, demo script and screenshot specs, a launch FAQ, App Store / Play listing character budgets, and the technical go-live checklist. The manifest layer between message-house-builder (the copy) and launch-readiness-auditor (the gate). |
| argument-hint | <product + launch tier> [channels] [target stores: ios/android/both] [existing assets] |
| metadata | {"author":"aaron-he-zhu","version":"19.2.0","discipline":"launch","phase":"assemble","geo-relevance":"low","hermes":{"tags":["marketing","launch","assemble"],"category":"launch"},"openclaw":{"emoji":"🚀","homepage":"https://github.com/aaron-he-zhu/aaron-marketing-skills"}} |
Launch Asset Packager
Assembles the tier-scoped asset manifest for a launch — every artifact the moment needs, its owner, its spec source, and its production status — in the Assemble phase of the RAMP loop (Research → Assemble → Mobilize → Prove). It feeds the RAMP A sub-items directly: press kit complete, per-channel asset kits complete per tier to each surface's documented spec (store listing character budgets included), and the technical go-live pass — and the manifest tracks the localization-variant and message-match rows the auditor later checks. It works one lever — the kit — and hands off: only launch-readiness-auditor computes the RAMP profile result or runs the A1 veto.
Scope guard: this skill owns the asset manifest and specs, not the content inside them. It does not write the message copy (message-house-builder owns the message house; long-form goes to content-writer), build the landing page or signup UX (landing-optimizer), research store keywords beyond budget-fitting the fields (keyword-research), execute the go-live technical items (technical-seo-checker and serp-markup-builder own execution — this skill only lists and tracks the manifest items), adjudicate product claims (marked [needs source] and routed to memory/events/claims.ndjson via an authorized operation: propose request to registry-events.py), or score any RAMP dimension.
Quick Start
Package the launch assets for [product] — tier [T1/T2/T3], channels: [list]. What exists already: [links / list].
Build the press kit spec for [product], plus a demo script and screenshot shot list for the walkthrough video.
Draft the App Store + Play listing metadata against the official character budgets, and give me the technical go-live checklist for [site].
Skill Contract
Expected output: a tier-scoped asset manifest (artifact · owner · spec source · status), a press kit section spec, demo script + screenshot specs, a launch FAQ outline, dual-store listing drafts with Measured character counts against the official budgets, a technical go-live checklist (manifest only), and the standard handoff summary.
