CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

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

84%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Low

Low-risk findings worth noting

SKILL.md
Quality
Evals
Security

Quality

Content

71%Weight 40%Scale 1-5

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

A dense, well-structured instruction skill: a clear 9-step workflow with concrete budgets, enums, and validation blocks, and exemplary use of two real one-level reference files. The main costs are repetition — the scope guard and skill-routing disclaimers each appear two to three times — and output formats that live in files outside this bundle rather than inline or in the references.

Suggestions

Cut the duplicated scope guard (the closing 'manifest, specs, budgets, and gap report only' recap) and consolidate the routing disclaimers: technical-seo-checker/serp-markup-builder routing is stated in the opening scope guard, step 7, and Reference Materials — one authoritative statement plus the Reference Materials entry is enough.

Add a worked example of one completed manifest row and the handoff-summary shape (inline or in references/asset-specs.md) so the output format is executable without the external skill-contract.md, which is not part of this bundle.

Close the step-1 validation loop: when the canon-version mismatch blocks publish-ready assets, state the recovery route explicitly (e.g., route back to message-house-builder for a new accepted handoff) instead of only 'do not silently rebase copy'.

DimensionReasoningScore

Conciseness

The body never explains concepts Claude already knows, but it is noticeably tighten-able: the scope guard appears twice (the opening paragraph and the closing '**Scope guard**: manifest, specs, budgets, and gap report only'), the technical-seo-checker/serp-markup-builder routing is stated three times (scope guard, step 7, Reference Materials), and the long opening paragraph re-derives what the frontmatter description already says. This matches 'mostly efficient but... could be tightened' rather than the minor-trim level of 4.

3 / 5

Actionability

For an instruction-only skill the guidance is highly concrete: exact store budgets ('App Store: name 30, subtitle 30, keywords 100, promotional text 170, description 4,000; Play: title 30, short description 80, full description 4,000'), the nine presskit() sections named, a status enum ('missing / draft / final / approved'), a starter table in references/asset-specs.md, and three Quick Start invocations. Not 5 because the actual output shapes depend on files outside this bundle (the handoff summary format lives in skill-contract.md and registry-events.py usage is assumed), leaving minor execution gaps.

4 / 5

Workflow Clarity

Nine clearly sequenced steps (confirm tier → skeleton → press kit → demo specs → store listings → FAQ → go-live checklist → guardrails → freeze and report) with real checkpoints: 'A mismatch or unresolved material claim blocks publish-ready assets', unresolved wording kept '[needs source]' with ready status blocked, and a 'Done when' contract. Not 5 because the step-1 mismatch handling stops ('do not silently rebase copy') without a recovery loop naming where to route the fix, so a feedback loop is implicit rather than explicit.

4 / 5

Progressive Disclosure

The body is an appropriately lean overview with both bundle files real, one level deep, and well signaled: 'Use the starter table in [asset-specs.md](references/asset-specs.md)', 'follow [Launch Action Control](references/action-control.md)', plus a Reference Materials section annotating each. The heavy spec tables (press-kit sections, dual-store budgets, go-live checklist, manifest template) are correctly split into asset-specs.md rather than inlined, and asset-specs.md does not nest further. This matches the clear-overview anchor; the many cross-skill links are labeled but don't create nesting.

5 / 5

Total

16

/

20

Passed

Description

95%Weight 40%Scale 1-5

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

An excellent description: explicit trigger phrases, comprehensive concrete deliverables, and explicit routing away from four neighboring skills. Its only real weakness is sheer length — one ~190-word run-on sentence with nested parenthetical lists that could be cut roughly in half without losing triggering information.

DimensionReasoningScore

Specificity

The description lists many concrete deliverables — 'produces a tier-scoped launch asset manifest', 'a 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', 'a technical go-live checklist manifest (robots flip, sitemap, OG tags, analytics verification)' — which is 5-level coverage, but it is packed into a single ~190-word sentence with nested parentheticals, so verbosity dilutes clarity. Not 5 because 'concise and clear beats long and padded'; not 3 because the actions are far more than 1-2 and fully concrete.

4 / 5

Completeness

Both halves are explicit: 'when' opens the description ('Use when the user asks to...') and 'what' follows immediately ('produces a tier-scoped launch asset manifest with production status — ...'). This matches the anchor 'clearly and explicitly answers both what AND when with concrete trigger phrases'; 4 would require the 'when' to be less explicit, which it is not.

5 / 5

Trigger Term Quality

It leads with quoted natural trigger phrases users would actually say — '"package the launch assets", "build a press kit", or "prep the store listing and go-live checklist"' — and adds domain synonyms ('press kit', 'store listing', 'go-live checklist', 'App Store Connect / Play Console') plus Chinese equivalents ('发布资产打包/press kit/商店listing规格/上线检查清单'). This matches the comprehensive-synonyms anchor; 4 would require noticeably missing natural terms, which it doesn't have.

5 / 5

Distinctiveness Conflict Risk

It carves a clear niche (launch asset manifest/specs) and explicitly disambiguates four adjacent skills — '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'. Clear niche with distinct triggers and minimal conflict risk, matching the 5 anchor; no neighboring anchor fits better.

5 / 5

Total

19

/

20

Passed

Validation

81%

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

CriteriaDescriptionResult

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

Reviewed

Table of Contents

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.