Agent skill · Data & Analytics

launch-asset-packager

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 w

aaron-he-zhugithub.com/aaron-he-zhuGitHub ↗
claude-codeApache-2.0
Install
npx skills add aaron-he-zhu/aaron-marketing-skills --skill launch-asset-packager --agent claude-code

Same command for any agent — swap --agent for codex, cursor, copilot.

Facts
Files in the skill folder: 2
SKILL.md size: 12 KB
Bundled scripts: none
Version: 19.1.0
Requires: Claude Code and compatible agent-skill hosts
Path: launch/assemble/launch-asset-packager/SKILL.md
Open the folder on GitHub →
Where it comes from
Stars: 2,508
Language: Python
Read our review of the source →

Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.

From the SKILL.md

# 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](../../mobilize/launch-readiness-auditor/SKILL.md) 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](../message-house-builder/SKILL.md) owns the message house; long-form goes to [content-writer](../../../seo-geo/implement/content-writer/SKILL.md)), build the landing page or signup UX ([landing-optimizer](../../../influencer/report/landing-optimizer/SKILL.md)), research store keywords beyo

What's inside
Steps it walks through
  1. Quick Start
  2. Skill Contract
  3. Handoff Summary
  4. Data Sources
  5. Instructions
  6. Save Results
  7. Reference Materials
  8. Next Best Skill
Ships with 1 file
  • references/asset-specs.md
More from aaron-marketing-skills
All skills →
About this skill
What does the launch-asset-packager skill do?

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 w

How do I install it?

Run `npx skills add aaron-he-zhu/aaron-marketing-skills --skill launch-asset-packager --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.

Where does this skill come from?

From aaron-he-zhu/aaron-marketing-skills, a repository with 2,508 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.

Is a popular skill a good skill?

Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.

Keep going