CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

attribution-reconciler

Use when platform-reported conversions disagree with GA4/ecommerce, when you suspect Meta and Google are double-counting the same sales, or for a standing (monthly) reconciliation workbook that de-dups stacked credit against an order-ID truth set, normalizes attribution windows and currency, compares attribution models, and reads incrementality from a geo/holdout test. Not for the point-in-time R2 veto or RQS gate — use ad-account-auditor; not for the ROI/ROAS ratio math itself — use roi-calculator; not for organic dark-social share attribution or GA4 direct-traffic decomposition — use dark-social-attributor. 付费广告归因对账/去重/增量

Quality

82%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Low

Low-risk findings worth noting

SKILL.md
Quality
Evals
Security

Quality

Content

73%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 instruction skill with an explicit, well-gated workflow, concrete match/de-dup formulas, and clear boundaries against neighboring skills. Its main weakness is redundancy — the handoff and truth-set rules are restated several times — and cross-skill references with deep relative paths that may not resolve outside the parent repo.

Suggestions

State the roi-calculator / ad-account-auditor delegation once (e.g. in the intro blockquote or Next Best Skill) and trim its repetition from the Skill Contract, Step 7, and Reference Materials to cut ~15% of tokens.

Consolidate the repeated 'order IDs are the truth set, never platform-reported counts' rule into a single highlighted statement instead of restating it in the blockquote, the body paragraph, and Steps 1/3/4.

Move the inline cross-skill links scattered through the body into the single Reference Materials section, and verify the deep relative paths (../../../references/..., ../../orchestrate/...) resolve from the skill's install location or shorten them.

DimensionReasoningScore

Conciseness

Mostly efficient with no basic-concept tutoring, but noticeably padded by repetition: the delegation to roi-calculator/ad-account-auditor is restated in the intro blockquote, the Skill Contract ('Done when' bullet), Step 7, Reference Materials, and Next Best Skill, and the order-ID truth-set rule is repeated three times. This fits anchor 3 ('mostly efficient but... could be tightened') better than anchor 4, where over-explanation would be only minor.

3 / 5

Actionability

Concrete, executable guidance throughout: explicit match labels ('matched', 'double-counted', 'unmatched'), join keys ('order ID (preferred) or timestamp + value as a fallback'), computed formulas ('double-count rate (claimed conversions / real orders)', 'incremental orders ÷ exposed'), a literal output path, and a concrete failure status ('return status: NEEDS_INPUT'). As an instruction-only skill the absence of code is not penalized; it falls short of anchor 5 only because some steps (e.g. 'convert all monetary values to one currency at a stated rate', model comparison 'e.g. last-click vs linear') leave specifics to the model's discretion.

4 / 5

Workflow Clarity

The 7 numbered steps are clearly sequenced (confirm truth set → normalize → match → de-dup → compare models → incrementality → hand off) with an explicit validation gate in Step 1 ('if it is absent, return status: NEEDS_INPUT... do not reconcile'), error-recovery paths (unresolved mismatches pushed to open-loops.md), edge-case branches (no holdout → 'mark incrementality N/A'), and a 'Done when' checklist — matching anchor 5's validation-plus-checklist profile.

5 / 5

Progressive Disclosure

No bundle files exist (references/, scripts/, assets/ are absent), so this scores the body's own structure: well-organized sections with a dedicated 'Reference Materials' list where each link carries a one-line purpose. It is not anchor 5 because many references use fragile deep relative paths outside the skill directory (e.g. '../../../references/roas-benchmark.md', '../../orchestrate/ad-test-designer/references/measurement-control.md') that cannot be verified to resolve, and the same links are repeated inline throughout the body rather than consolidated.

4 / 5

Total

16

/

20

Passed

Description

87%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 highly effective description: concrete enumerated capabilities, an explicit multi-trigger 'Use when' clause, and unusually good conflict avoidance via explicit redirects to adjacent skills. The only deductions are a second-person trigger clause and a few missing synonyms (e.g. 'Facebook' for Meta).

DimensionReasoningScore

Specificity

Lists multiple concrete actions — 'de-dups stacked credit against an order-ID truth set, normalizes attribution windows and currency, compares attribution models, and reads incrementality from a geo/holdout test' — which is comprehensive coverage (anchor 5), but the second-person trigger clause 'when you suspect Meta and Google are double-counting' incurs the rubric's −1 voice penalty, dropping it to 4.

4 / 5

Completeness

Explicitly answers both questions: 'what' via the enumerated actions (de-dup, normalize, compare models, read incrementality) and 'when' via the opening 'Use when platform-reported conversions disagree with GA4/ecommerce, when you suspect Meta and Google are double-counting...' with concrete trigger phrases — a clear anchor 5 match. It is not a 4 because the 'when' is fully explicit with multiple specific triggers, not merely present.

5 / 5

Trigger Term Quality

Strong natural keywords users would actually say: 'platform-reported conversions disagree with GA4', 'double-counting', 'Meta and Google', 'monthly reconciliation', 'attribution models', 'geo/holdout test'. A few common synonyms are missing (e.g. 'Facebook', 'conversion mismatch', 'reporting doesn't match'), so it fits anchor 4 ('good keyword coverage; a few natural terms missing') rather than the fully comprehensive anchor 5.

4 / 5

Distinctiveness Conflict Risk

Clear niche (paid-channel reconciliation against an order-ID truth set) with explicit negative boundaries redirecting three adjacent skills: 'Not for the point-in-time R2 veto or RQS gate — use ad-account-auditor; not for the ROI/ROAS ratio math itself — use roi-calculator; not for organic dark-social share attribution... use dark-social-attributor'. Minimal conflict risk — anchor 5.

5 / 5

Total

18

/

20

Passed

Validation

81%

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

Validation — 13 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

metadata_field

'metadata' should map string keys to string values

Warning

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

relative_links

Relative link issues: 21 suspicious

Warning

Total

13

/

16

Passed

Repository

aaron-he-zhu/aaron-marketing-skills

Path

ad/scale/attribution-reconciler/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.