What does this skill do, and when should you use it?
Launch Asset Packager is the Assemble-phase skill for the repository’s Launch/RAMP workflow. It organizes tier- and channel-scoped assets, press-kit specifications, demo and screenshot requirements, a launch FAQ, dual-store listing drafts, and technical go-live checks. It tracks owners, specification sources, statuses, dependencies, and gaps, but does not write final messaging, produce media, execute technical changes, or score RAMP readiness. It fits teams that need a structured launch kit and already have a declared tier, channels, and trusted product information.
Reads the launch tier and type, channels, accepted message-house handoff, narrative and claims projections, asset and pricing inventory, and store-console exports; builds one manifest row per channel-artifact with artifact, specification source, owner, due date, and status; specifies the nine press-kit sections; defines demo-story beats, screenshot shot lists, captions, and FAQ structure; drafts App Store and Play listing fields with measured character counts against the official budgets; lists robots, sitemap, OG/rich-snippet, analytics-event, and UTM verification items; freezes a manifest version, submits an authorized launches proposal, and reports missing assets, budget overruns, unresolved claims, and unverified go-live items.
- A product team has selected a T1, T2, or T3 launch and needs owners and production statuses across every channel asset.
- A mobile app is preparing both App Store and Google Play submissions and needs listing fields fitted to official character limits.
- A marketing team needs a press-kit specification covering facts, history, features, video, imagery, branding, recognition, and contact details.
- A launch team needs a demo script, screenshot shot list, FAQ outline, and technical go-live checklist while execution remains with other owners.
How do you install this skill?
- This is a static file review; the skill, scripts, connectors, and registry proposal flow were not executed.
- Recheck App Store Connect and Google Play field limits and platform policies before submission.
- Do not treat a manifest proposal or any technical go-live action as user-approved; confirm write authorization, scope, and recovery procedures.
- If the message house or claims, narrative, or launch projections and referenced materials are unavailable, apply the skill's own rule to block ready status.
- The security policy's supported version line conflicts with the skill's declared version; confirm maintenance and security-update commitments.
- Shell / CLI
- Network access
- Local filesystem
Install the repository with: git clone https://github.com/aaron-he-zhu/aaron-marketing-skills. Use launch/assemble/launch-asset-packager/SKILL.md from the cloned repository. In Claude Code, the supported plugin flow is: /plugin marketplace add aaron-he-zhu/aaron-marketing-skills, followed by /plugin install aaron-marketing@aaron. The supplied source does not document a separate standalone installation command for this skill.
tmp="$(mktemp -d)"
git clone --depth 1 https://github.com/aaron-he-zhu/aaron-marketing-skills.git "$tmp"
mkdir -p ~/.claude/skills
cp -R "$tmp/launch/assemble/launch-asset-packager" ~/.claude/skills/
rm -rf "$tmp"Generated from the source repository and skill path; it copies only this skill's folder. If the author's install steps above differ, follow those first. To scope it to one project, replace ~/.claude/skills with that project's .claude/skills.
How do you use this skill?
Use a trigger such as: Package the launch assets for [product] — tier [T1/T2/T3], channels: [list]. What exists already: [links / list]. Other supported prompts include: Build the press kit spec for [product], plus a demo script and screenshot shot list for the walkthrough video. Provide the product, launch tier, channels, existing assets, and optionally target stores: ios, android, or both.
What are this skill's strengths and limitations?
- Produces a concrete manifest, press-kit spec, demo and screenshot requirements, FAQ outline, store metadata drafts, and technical checklist.
- Tracks owners, specification sources, statuses, dependencies, and measurable character counts.
- Maintains a clear handoff boundary: technical SEO and go-live execution belong to designated skills.
- The collection is Apache-2.0 licensed and supports Claude Code and compatible Agent Skills hosts.
- Does not write final message copy, produce media, build landing-page UX, or execute robots, sitemap, metadata, or analytics changes.
- Store limits must be rechecked against current official documentation at submission time.
- Narrative-version or claims mismatches, unresolved material claims, missing assets, budget overruns, and unverified checks can block publish-ready status.
- The source provides no independent test-suite results or evidence of an actual store submission by this skill.
How does this skill compare with similar options?
Side by side with related skills; every score comes from the same FSRS standard.
| Skill | FS score | Stars | Last updated | License |
|---|---|---|---|---|
| Launch Asset Packager this page | 54 · Use with care | ★ 3k | 12d ago | Apache-2.0 |
| Market Launch Playbook Generator | 52 · Use with care | ★ 2.8k | 7mo ago | MIT |
| RAMP Launch Readiness Auditor | 61 · Recommended | ★ 3k | 12d ago | Apache-2.0 |
| Launch Window Planner | 57 · Use with care | ★ 3k | 12d ago | Apache-2.0 |
| Press & Media Relations | 55 · Use with care | ★ 3k | 12d ago | Apache-2.0 |
How did FollowSkills review this skill?
The skill specifies Tier-1, keyless inputs, treats exports as untrusted, limits technical launch work to a checklist, requires authorized registry proposals, and keeps external mutations non-executing by default. It does not fully specify confirmation for every write, rollback, sensitive-data boundaries, or source-attribution verification, so 8 points are deducted.
The contract, numbered procedure, status values, handoffs, dependencies, and blocking conditions are largely self-consistent, and technical execution is explicitly out of scope. However, several projections, references, and runtime tools are unavailable in the supplied evidence, with no skill-specific key-path tests or diagnostic failure examples; static reliability is therefore limited to 8.
Triggers, audience scenarios, argument hints, expected outputs, scope exclusions, and iOS/Android choices are clear, with bilingual wording. Boundaries for non-store launches or missing message-house and registry inputs are less explicit, and mainland-China reachability of official store documentation and connectors is not demonstrated, so 5 points are deducted.
The skill has strong structure: Quick Start, contract, data sources, procedure, handoff, references, license, and version metadata, supported by repository maintenance signals. It lacks a skill-specific changelog, explicit maintainer responsibility, and update path; the repository security policy also lists 17.x as current while this skill declares 18.0.0, so 5 points are deducted.
The stated output covers the manifest, press-kit specification, demo and screenshot specifications, FAQ, store-field counts, and technical checklist, with a starter template guiding direct use. Actual delivery depends on external projections, message-house inputs, and current official limits, and no representative finished outputs or comparative-benefit evidence are supplied; static effectiveness is scored 6.
The files identify official documentation as the source for store limits and provide internal templates, status rules, and repository test evidence. They do not provide dedicated tests for this skill's key paths, third-party execution results, or corroborating source material, and the named official sources are not included in the supplied files; 3 points are awarded.
Open a dimension to read why it scored that way
Evidence confidence：Low — Mostly static review, author material or a limited demo; useful for discovery, not high-risk decisions.
See the full review method →