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.

65

Quality

77%

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

Fix and improve this skill with Tessl

tessl review fix ./skills/ua-campaign/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

65%

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

A genuinely actionable and well-organized UA planning skill with specific numbers and templates, but it is a monolithic single file with no progressive disclosure into reference files and lacks explicit validation feedback loops in its workflows.

Suggestions

Move the per-channel deep-dives (Apple Search Ads, Meta, Google UAC) into separate reference files under references/ and link to them from a concise overview in the body, improving progressive disclosure.

Add explicit validation checkpoints to the workflow (e.g., 'After launch, verify CPI <= target; if CPI > 2x target, pause keyword/ad set and re-bid, then re-check') to introduce a validate-fix-retry feedback loop.

Tighten overlapping content — consolidate the ASCII funnel diagram with the metrics table and dedupe channel advice across sections — to improve token efficiency.

DimensionReasoningScore

Conciseness

Dense and information-rich with little concept padding, but ~200 lines with some overlap (ASCII funnel + metric table, repeated channel advice) that could be tightened, matching 'mostly efficient but could be tightened'.

2 / 3

Actionability

Highly concrete throughout: budget-to-channel dollar thresholds, CPI ranges, campaign-structure trees, target CPA numbers, metric formulas with targets, and a fill-in output template that is copy-paste ready.

3 / 3

Workflow Clarity

A numbered intake sequence and optimization checklist exist, but the launch/optimize process lacks explicit validation checkpoints or validate-fix-retry feedback loops, matching 'steps listed but validation gaps'.

2 / 3

Progressive Disclosure

No bundle files exist; all per-channel deep-dives (ASA, Meta, Google UAC) are inline in one ~200-line file rather than split into signaled one-level-deep references, though it is well-sectioned.

2 / 3

Total

9

/

12

Passed

Description

90%

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, well-structured description with excellent trigger coverage, explicit when-guidance, and clear routing away from overlapping skills. The only gap is that the 'what' lists few concrete actions rather than a comprehensive enumeration.

DimensionReasoningScore

Specificity

Names the domain and concrete actions ("plan or optimize paid user acquisition campaigns") but does not enumerate multiple specific actions, matching the 'names domain and some actions, not comprehensive' anchor.

2 / 3

Completeness

Answers both what ("plan or optimize paid user acquisition campaigns") and when ("Use when the user mentions...") with explicit triggers, matching the top anchor.

3 / 3

Trigger Term Quality

Broad natural-term coverage ("Apple Search Ads", "user acquisition", "paid ads", "UA", "cost per install", etc.) matching the 'good coverage of natural terms users would say' anchor.

3 / 3

Distinctiveness Conflict Risk

Active disambiguation ("For organic growth, see aso-audit. For launch-specific UA, see app-launch.") plus a distinct paid-UA niche with clear triggers, unlikely to conflict.

3 / 3

Total

11

/

12

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.