CtrlK
BlogDocsLog inGet started
Tessl Logo

attribution-setup

When the user wants to set up, debug, or interpret app install attribution — including SKAdNetwork (SKAN), Apple's AdAttributionKit, Google Play Install Referrer, MMPs (AppsFlyer, Adjust, Singular, Branch, Kochava), deep links, deferred deep links, conversion values, postback windows, or privacy thresholds. Use when the user mentions "SKAdNetwork", "SKAN", "SKAN 4", "AdAttributionKit", "AAK", "MMP", "AppsFlyer", "Adjust", "Singular", "Branch", "attribution", "conversion value", "postback", "Install Referrer", "deferred deep link", "iOS 14.5", "ATT", "App Tracking Transparency", "IDFA", or "I can't measure my ad campaigns". For paid campaign strategy, see ua-campaign and apple-search-ads. For analytics events, see app-analytics.

72

Quality

88%

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

82%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 strong specialist body: highly actionable with concrete schemas, per-MMP checklists, a debug playbook, and an output template, organized in clean tables with a coherent assessment-to-testing flow. The main gaps are minor over-explanation of known concepts and inline placement of per-MMP detail that would benefit from reference files.

Suggestions

Trim the 'SKAdNetwork 4.0 Essentials' concept table to only the non-obvious SKAN 4 specifics (postback windows, hierarchical source IDs, privacy thresholds) and drop definitions Claude already knows.

Move the per-MMP setup checklists into per-vendor reference files (e.g. references/appsflyer.md, references/adjust.md) and keep one-line summaries in SKILL.md for progressive disclosure.

Make the mid-workflow validation checkpoints explicit (e.g. when to verify postback arrival and CV propagation during implementation, not only in the final testing plan).

DimensionReasoningScore

Conciseness

Dense, signal-heavy tables and checklists with almost no filler; however, the 'SKAdNetwork 4.0 Essentials' concept table explains basics (e.g. 'Postback | The signal Apple sends to your ad network confirming an install') that are partially over-explanation, keeping it just below the lean anchor.

4 / 5

Actionability

Fully concrete guidance: a CV schema template with actual value ranges (0, 1–5, 6–15 ... 46–63), per-MMP checklists naming specific SDK calls ('AppsFlyerLib.shared().start()', 'Adjust.appDidLaunch(...)'), a symptom→cause debug playbook, and a copy-ready output template covering the common cases.

5 / 5

Workflow Clarity

Clear sequence (Initial Assessment → stack recommendation → CV schema → implementation checklist → testing plan) with explicit verification checkpoints ('verify postback in MMP within X hours', 'Test deferred deep link from each ad source'), but some mid-process checkpoints are implicit rather than spelled out.

4 / 5

Progressive Disclosure

Well-sectioned single-file body with clear headers and navigation, but no bundle files exist and the per-MMP setup checklists plus the CV schema templates are inline content that would fit better in one-level-deep reference files.

4 / 5

Total

17

/

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 exemplary description: it clearly states what the skill does, provides an exhaustive set of natural trigger terms including the user's colloquial phrasing, and explicitly disambiguates against neighboring skills. The only improvement space is slightly broader action coverage beyond set up/debug/interpret.

DimensionReasoningScore

Specificity

Concrete actions are stated ('set up, debug, or interpret app install attribution') with a comprehensive enumeration of the domain (SKAdNetwork, AdAttributionKit, Install Referrer, MMPs, deep links, conversion values, postback windows, privacy thresholds), but only three distinct action verbs, leaving minor gaps versus the comprehensive anchor.

4 / 5

Completeness

Explicitly answers both 'what' (set up, debug, or interpret app install attribution with enumerated mechanisms) and 'when' ("Use when the user mentions..." followed by concrete trigger phrases), matching the anchor exactly.

5 / 5

Trigger Term Quality

Comprehensive natural-term coverage including synonyms and abbreviations ("SKAdNetwork", "SKAN", "SKAN 4", "AAK", "MMP", vendor names, "conversion value", "postback", "Install Referrer", "deferred deep link", "ATT", "IDFA") plus the colloquial user phrase "I can't measure my ad campaigns".

5 / 5

Distinctiveness Conflict Risk

Clear niche (mobile app install attribution) with distinct technical triggers, and explicit boundary guidance redirecting adjacent intents ("For paid campaign strategy, see ua-campaign and apple-search-ads. For analytics events, see app-analytics.") minimizes conflict risk.

5 / 5

Total

19

/

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.

Validation — 16 / 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.