CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

attribution-modeling

Multi-touch attribution modeling for advertising campaigns. Use when analyzing conversion paths, comparing attribution models, implementing data-driven attribution, or understanding assisted conversions.

Quality

82%

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

63%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 well-structured, information-dense reference for attribution modeling with genuinely useful platform-specific data and concrete workflows. Its weaknesses are token efficiency (textbook model definitions and a promotional footer) and the absence of any progressive disclosure — everything is inlined in one long file with no executable tooling for the computational steps.

Suggestions

Move the Attribution Models Reference, Reference Data tables (lookback windows, platform defaults, typical credit shifts), and Examples into separate files under references/ with clearly signaled links, keeping SKILL.md as a concise overview with the workflows.

Trim the per-model 'Strengths/Weaknesses' textbook commentary for standard models (first-touch, last-touch, linear, time-decay, position-based) that Claude already knows, and remove the promotional footer links.

Add an executable script or concrete calculation method for the Markov chain workflow (transition matrix construction and absorption computation) and include explicit validation checkpoints (e.g., verify normalized attribution weights sum to 100%, verify reconciled totals match GA4).

DimensionReasoningScore

Conciseness

The body spends ~80 lines restating textbook definitions of standard attribution models ("100% credit → first interaction", "Strengths: Simple, highlights discovery channels") that Claude already knows, and the promotional footer ("Try Synter — AI Agent Media Buyers...") is pure padding. The platform-specific data (lookback defaults, DDA thresholds, GA4 navigation) does earn its place, keeping this at 'mostly efficient with some unnecessary explanation' rather than 'noticeably verbose'.

3 / 5

Actionability

Guidance is concrete: exact GA4 paths ("Admin → Attribution Settings"), formulas, numeric thresholds ("3,000 ad interactions + 300 conversions in 30 days"), and interpretation tables (assist ratio bands). Not a 5 because steps like "Apply each model to the same dataset" and "recalculate conversion probability using matrix absorption" give no executable method or tooling to actually compute the results.

4 / 5

Workflow Clarity

Three workflows with clear numbered sequences and useful interpretation rules ("If Channel A gets 40% on last-touch but 15% on first-touch → it's a closer"), plus mild checkpoints ("Monitor for 2-4 weeks", "Total matches GA4: 350"). Not a 5 because no explicit validate-then-proceed loops exist; not a 3 because the sequences are well-defined and operations are read-only analysis, so the destructive/batch cap does not apply.

4 / 5

Progressive Disclosure

A single ~300-line monolithic file with no bundle files at all; the Attribution Models Reference, Reference Data tables (lookback windows, platform defaults), and Examples sections are inline content that would fit better in separate reference files. Section headers are clear, matching 'some structure but could be better organized; content that should be separate is inline'.

3 / 5

Total

14

/

20

Passed

Description

92%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 description that clearly and explicitly states both what the skill does and when to use it, with four concrete trigger actions in natural marketing language. The only minor gap is keyword coverage — a few common synonyms like 'marketing attribution' or 'first-touch/last-touch' would make triggering even more reliable.

DimensionReasoningScore

Specificity

"analyzing conversion paths, comparing attribution models, implementing data-driven attribution, or understanding assisted conversions" lists four parallel concrete actions, matching the score-5 anchor of 'multiple specific concrete actions; comprehensive coverage'. Not a 4 because coverage of the attribution domain within the description is comprehensive rather than having minor gaps.

5 / 5

Completeness

Explicitly answers both: what ("Multi-touch attribution modeling for advertising campaigns") and when ("Use when analyzing conversion paths, comparing attribution models, implementing data-driven attribution, or understanding assisted conversions") with concrete trigger phrases — an exact structural match to the score-5 anchor.

5 / 5

Trigger Term Quality

"conversion paths", "attribution models", "data-driven attribution", and "assisted conversions" are natural phrases users would say. Not a 5 because common synonyms and variations such as "marketing attribution", "first-touch/last-touch", or "channel credit" are missing — 'good keyword coverage; a few natural terms missing'.

4 / 5

Distinctiveness Conflict Risk

"Multi-touch attribution" carves out a clear niche with distinct triggers and minimal conflict risk against generic analytics or document skills. The description is in third-person noun-phrase voice, so no voice penalty applies. Not a 4 because no specific closely-related skill overlap is evident from the wording.

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

Synter-Media-AI/free-skills

Path

skills/attribution-modeling/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.