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 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规格/上线检查清单

Quality

96%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Quality

Content

92%Weight 40%Scale 1-3

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A dense but genuinely actionable body: concrete budgets and statuses, a sequenced 9-step workflow with blocking validation checkpoints, and clean one-level-deep reference split. The only weak spot is mild verbosity from a duplicated scope guard and long compound sentences.

Suggestions

Remove the closing 'Scope guard' block (lines 69) since the same boundary is already stated in the intro Scope Guard paragraph — keep one authoritative version.

Break the long compound sentences in the intro and Scope Guard into shorter declarative sentences so each handoff/rule is its own line.

Tighten the RAMP framework exposition in the opening paragraph to just the lever and handoff; the framework detail is available in ramp-benchmark.md.

Dimension	Reasoning	Score
Conciseness	Mostly efficient and operational, but the Scope Guard is stated twice (intro paragraph and closing) and several sentences are long compound runs that could be tightened; not score-3 lean where every token earns its place.	2 / 3
Actionability	Highly actionable for an instruction-only skill — exact character budgets (name 30, subtitle 30, keywords 100, promotional text 170, description 4,000; Play title 30/short 80/full 4,000), named statuses (missing/draft/final/approved), and the nine presskit() sections give copy-paste-ready specifics; absence of code is not penalized per scoring notes.	3 / 3
Workflow Clarity	A clear 9-step sequence with explicit validation/guard checkpoints — step 1 blocks on canon mismatch, step 6 blocks ready status on unresolved claims, step 9 freezes and reports gaps with evidence labels — matching the top anchor.	3 / 3
Progressive Disclosure	Well-structured overview (Quick Start, Skill Contract, Data Sources, Instructions, Reference Materials) with one-level-deep references, e.g. asset-specs.md for the section spec and starter table (confirmed real file), keeping detail out of SKILL.md.	3 / 3
	Total	11 / 12 Passed

Description

100%Weight 40%Scale 1-3

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A strong description: concrete actions, natural quoted triggers, explicit what-and-when guidance, and clear negative boundaries against neighboring skills. It is dense but every clause is operational rather than fluffy.

Dimension	Reasoning	Score
Specificity	Lists many concrete actions — 'press kit spec (factsheet, description, history, features, videos, images, logo and icon, awards, contact)', 'demo script and screenshot specs', 'dual-store listing metadata drafts against the official character budgets', and 'technical go-live checklist manifest' — matching the top anchor for multiple specific concrete actions.	3 / 3
Completeness	Opens with 'Use when the user asks to...' (explicit when) and follows with a detailed 'produces a tier-scoped launch asset manifest...' (clear what), satisfying both halves with explicit triggers.	3 / 3
Trigger Term Quality	Explicit quoted natural triggers a user would actually say — 'package the launch assets', 'build a press kit', 'prep the store listing and go-live checklist' — plus domain terms press kit / store listing / go-live checklist, giving good coverage.	3 / 3
Distinctiveness Conflict Risk	Clear niche (launch asset manifest) reinforced by explicit exclusions — 'Not for the message copy itself — use message-house-builder or content-writer; not for landing page UX — use landing-optimizer' — making conflict with adjacent skills unlikely.	3 / 3
	Total	12 / 12 Passed

Validation

81%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 13 / 16 Passed

Validation for skill structure

Criteria	Description	Result
metadata_field	'metadata' should map string keys to string values	Warning
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning
relative_links	Relative link issues: 27 suspicious	Warning

	Total	13 / 16 Passed

Repository: aaron-he-zhu/aaron-marketing-skills
Path: launch/assemble/launch-asset-packager/SKILL.md
Commit: 4a77c48

Reviewed: 9 days ago

Table of Contents

Discovery Implementation Validation

Is this your skill?

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.