CtrlK
BlogDocsLog inGet started
Tessl Logo

ua-campaign

When the user wants to plan or optimize paid user acquisition campaigns. Also use when the user mentions "Apple Search Ads", "user acquisition", "paid ads", "UA", "ad campaign", "install campaign", "Facebook ads for apps", "TikTok ads", or "cost per install". For organic growth, see aso-audit. For launch-specific UA, see app-launch.

69

Quality

84%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Quality

Content

78%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 highly actionable, information-dense UA playbook with concrete structures, targets, and templates. Its main gaps are progressive disclosure (everything inlined in one long file with no reference files) and a missing explicit validation checkpoint between the assessment and channel-selection stages.

Suggestions

Move the per-platform deep dives (Apple Search Ads, Meta, Google UAC) and the channel/metric comparison tables into separate reference files under references/, keeping SKILL.md as a concise overview that links to them one level deep.

Add an explicit validation checkpoint after the Initial Assessment (e.g., 'Only proceed to Channel Selection once budget, target CPI/ROAS, LTV, audience, countries, and category are all confirmed') to make the workflow feedback loop explicit.

Trim the explanatory prose in 'Why Start Here' to bare bullets so the body stays lean and assumes Claude's competence.

DimensionReasoningScore

Conciseness

Content is dense, table-driven reference material that assumes domain competence and avoids padding, but the 'Why Start Here' prose and a few explanatory asides ('Highest intent (user is actively searching)') are minor over-explanation that could be trimmed.

4 / 5

Actionability

Provides fully concrete, executable guidance: campaign-structure tree diagrams, bidding tables with specific CPA targets, an optimization checklist, metric formulas with target thresholds, and a copy-ready UA plan output template.

5 / 5

Workflow Clarity

The Initial Assessment is a clearly numbered 1–7 sequence and the optimization cadence table plus checklist supply feedback loops, but there is no explicit validate-then-proceed checkpoint tying the assessment inputs to the channel-selection decision.

4 / 5

Progressive Disclosure

The file is well-sectioned but ~200 lines with no bundle files in references/scripts/assets; channel-comparison tables and the per-platform deep dives are inlined material that would be better split into one-level-deep reference files rather than kept in the overview.

3 / 5

Total

16

/

20

Passed

Description

90%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.

A strong, third-person description with explicit trigger terms and boundary guidance to sibling skills. Its only weakness is that the action list (plan/optimize) understates the launch, structuring, and measurement work the body actually covers.

DimensionReasoningScore

Specificity

Quotes 'plan or optimize paid user acquisition campaigns' — names the domain and two concrete actions (plan, optimize), but does not enumerate the fuller set of capabilities (launch, structure, bid, measure) covered in the body, so coverage is not comprehensive.

3 / 5

Completeness

Explicitly answers 'what' (plan or optimize paid user acquisition campaigns) and 'when' (a dedicated 'Also use when the user mentions...' clause with concrete trigger phrases), satisfying the 5-anchor requirement for both.

5 / 5

Trigger Term Quality

Lists a comprehensive set of natural terms a user would say — 'Apple Search Ads', 'user acquisition', 'paid ads', 'UA', 'ad campaign', 'install campaign', 'Facebook ads for apps', 'TikTok ads', 'cost per install' — including the abbreviation and platform-specific synonyms.

5 / 5

Distinctiveness Conflict Risk

Clear paid-UA niche with distinct triggers and explicit disambiguation ('For organic growth, see aso-audit. For launch-specific UA, see app-launch.'), minimizing conflict with adjacent skills.

5 / 5

Total

18

/

20

Passed

Validation

100%

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

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
Eronred/aso-skills
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.