How to read paid media dashboards without fooling yourself. Attribution models, platform reporting quirks, multi-platform reconciliation, ROAS vs LTV horizon traps, statistical noise in performance metrics, incrementality testing, and the failure modes that produce expensive lessons. Triggers on read paid media dashboard, attribution analysis, ROAS vs LTV, multi-platform reconciliation, ad incrementality, geo holdout, conversion lift study, ghost bidding, paid media reporting, board-deck paid media metrics, blended CAC, MMM, MTA, last-click attribution. Also triggers when a marketer is about to scale, kill, or rebudget a campaign based on platform metrics, or when reconciling platform reports against warehouse revenue.
65
78%
Does it follow best practices?
Impact
—
No eval scenarios have been run
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./skills/ads-performance-analytics/SKILL.mdQuality
Discovery
100%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This is an excellent skill description that thoroughly covers the domain of paid media dashboard analysis with highly specific capabilities, comprehensive trigger terms spanning both technical acronyms and natural language scenarios, and clear guidance on when to activate. The description is well-structured, moving from what it does to explicit trigger conditions including situational triggers. Minor note: the description is quite long, but the density of useful information justifies the length.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions and concepts: attribution models, platform reporting quirks, multi-platform reconciliation, ROAS vs LTV horizon traps, statistical noise analysis, incrementality testing, and failure modes. Very detailed about what the skill covers. | 3 / 3 |
Completeness | Clearly answers both 'what' (how to read paid media dashboards, attribution analysis, reconciliation, incrementality testing, failure modes) and 'when' with explicit triggers including specific terms and situational triggers like 'when a marketer is about to scale, kill, or rebudget a campaign based on platform metrics'. | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural terms users would say: 'ROAS vs LTV', 'blended CAC', 'MMM', 'MTA', 'last-click attribution', 'geo holdout', 'conversion lift study', 'ghost bidding', 'board-deck paid media metrics'. These are terms marketers naturally use when seeking this kind of guidance. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive niche focused specifically on paid media dashboard interpretation and attribution pitfalls. The combination of paid media analytics, attribution models, incrementality testing, and platform reconciliation creates a clear, unique domain unlikely to conflict with other skills. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
57%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a comprehensive and well-structured knowledge skill that covers paid media analytics interpretation thoroughly, with good progressive disclosure to reference files and a useful 12-consideration framework. Its main weaknesses are verbosity (explaining concepts Claude likely knows, philosophical framing, audience descriptions) and a lack of executable artifacts—no SQL queries, no spreadsheet formulas, no dashboard configuration code—which limits actionability for a data-team skill. The workflow for high-stakes decisions (scaling/killing campaigns) would benefit from explicit validation checkpoints with specific numeric thresholds.
Suggestions
Add executable artifacts: a blended CAC SQL query, a reconciliation formula, or a dashboard validation script that Claude can actually use or adapt when helping users.
Trim introductory and contextual paragraphs—remove audience descriptions, philosophical framing ('This is not a moral failing'), and explanations of basic concepts (what ROAS is, what LTV is) that Claude already knows.
Add explicit decision gates with numeric thresholds to the workflow—e.g., 'Before killing a campaign: (1) confirm ≥2 weeks of data, (2) verify platform-warehouse delta >30%, (3) check incrementality test results if available, (4) only then recommend kill.'
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is thorough and mostly well-written, but it's verbose in places—explaining what attribution models are, what ROAS and LTV mean, and providing extensive context that Claude already knows. The introductory paragraphs, audience descriptions, and philosophical framing ('This is not a moral failing; it is a structural incentive') add tokens without adding actionable value. The 12 common interpretation failures section is useful but could be more compressed. | 2 / 3 |
Actionability | The skill provides concrete mental frameworks, worked examples (e.g., Meta 2.5x ROAS vs Google 1.8x ROAS), and specific heuristics (e.g., '30% incremental rate for retargeting'). However, it lacks executable code, SQL queries, dashboard configuration snippets, or copy-paste-ready reconciliation formulas. For a data-team-mentor playbook, the absence of any executable artifacts (even a blended CAC SQL query or a reconciliation spreadsheet formula) limits actionability to conceptual guidance rather than concrete execution. | 2 / 3 |
Workflow Clarity | The 12-consideration framework provides a clear checklist, and the reconciliation pattern has a logical sequence. However, for destructive decisions (killing campaigns, rebudgeting), there are no explicit validation checkpoints or feedback loops—e.g., no 'before killing a campaign, verify X, Y, Z' checklist with specific thresholds. The geo holdout section describes setup requirements but doesn't provide a step-by-step workflow with validation gates. | 2 / 3 |
Progressive Disclosure | The skill has excellent progressive disclosure structure: a clear overview with well-organized sections, and seven clearly signaled one-level-deep reference files covering glossary, attribution comparison, platform quirks, incrementality playbook, reconciliation patterns, cohort templates, and interpretation failures. Navigation is intuitive and references are contextually placed near relevant content. However, no bundle files were provided to verify the references actually exist. | 3 / 3 |
Total | 9 / 12 Passed |
Validation
90%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 10 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 10 / 11 Passed | |
8e70d03
Table of Contents
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.