conversion-verifier

conversion-verifier is a skill for Claude Code from metrikia-io/marketing-skills. It costs 160 tokens per session (5,108 once invoked), scanned A, original, MIT.

A reconciliation tool that compares sales reported by advertising platforms with purchases recorded in a store or payment system. ROAS means return on advertising spend, and reconciliation means explaining why two records do not match.

In plain words
What is it for?
Use it to compare Meta, Google, or TikTok conversion reports with Shopify or Stripe purchases and create a client-ready explanation of the remaining gap.
Why use it?
It separates legitimate differences—such as refunds, time zones, attribution rules, or other sales channels—from discrepancies that still need investigation.

Skill for Claude Code

Written for Claude Code: shipped in a Claude Code plugin.

Part of the marketing-skills plugin — 2 skills shipped together

Good fit Use it to compare Meta, Google, or TikTok conversion reports with Shopify or Stripe purchases and create a client-ready explanation of the remaining gap.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/metrikia-io/marketing-skills/conversion-verifier
Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

Any agent
npx skills add metrikia-io/marketing-skills --skill conversion-verifier
Clone the repo
git clone --depth 1 https://github.com/metrikia-io/marketing-skills

Made for: Claude Code.

Or install marketing-skills, the plugin that ships this one along with the rest of its 2 skills.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

agentmods badge for conversion-verifier

README.md
[![agentmods](https://agentmods.dev/badge/skills/metrikia-io/marketing-skills/conversion-verifier/github.svg)](https://agentmods.dev/skills/metrikia-io/marketing-skills/conversion-verifier)
Your own site
<a href="https://agentmods.dev/skills/metrikia-io/marketing-skills/conversion-verifier"><img src="https://agentmods.dev/badge/skills/metrikia-io/marketing-skills/conversion-verifier/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for conversion-verifier

Your own site · 80×15
<a href="https://agentmods.dev/skills/metrikia-io/marketing-skills/conversion-verifier"><img src="https://agentmods.dev/badge/skills/metrikia-io/marketing-skills/conversion-verifier.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 160 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 5,108 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5.1 $0.00160 $0.05108
Opus 5 $0.00080 $0.02554
Sonnet 5 $0.00032 $0.01022
Haiku 4.5 $0.00016 $0.00511

Measured 11d ago against content hash 04d8a6fe4b7d, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-11, from the pricing page.

Security

Grade A, and why

conversion-verifier scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 11d ago.

The scan reads SKILL.md. This mod also ships 9 executable files (scripts/build_report.py, scripts/charts.py, scripts/columns.py, …), listed below but not scanned — reading those needs a real analyzer, not pattern matching.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

skills/conversion-verifier/SKILL.md · 429 lines

How it starts

The opening of the file, as written. The whole thing — 429 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Conversion Verifier

Ad platforms grade their own homework. Meta decides which sales Meta caused, Google decides which sales Google caused, and neither is ever asked to check its answer against the bank. This does that check.

The idea that makes this useful

Anyone can subtract two numbers and announce that the platform is lying. That tool would be wrong most of the time, because most of the gap between claimed and actual has legitimate causes: attribution windows shift dates, timezones slide orders across midnight, refunds are never reported back, and a store's total includes channels the platform never touched.

An experienced buyer knows all of this and will dismiss a naive "you're being lied to" report in about ten seconds.

So the work here is not the subtraction. It is separating the explained gap from the unexplained one. The unexplained residual is the only number worth acting on, and it is the number nobody currently has.

Hold that standard throughout. Being right matters more than being alarming, and a report that survives scrutiny is worth more to the person reading it than one that impresses them for a minute.

Checklist

Create a task for each of these and work through them in order.

  1. Get the ad data with the least friction that works: the Meta connection if they have it, the export if not
  2. Ask for the store export and the four questions, gross margin first
  3. Run reconcile.py with --gross-margin, deterministic numbers, no interpretation
  4. Read the JSON as an analyst, using references/gap-taxonomy.md
  5. Deliver the finding in the chat first, then write the narrative to the caps
  6. Build the visual report with build_report.py, then tell them how to get a PDF
  7. Close with the limit and the offer, in that order, never reversed

Two rules that decide whether this gets used at all

Gaetan, a media buyer, tested the first version and gave two verdicts worth holding onto. Both are about friction rather than analysis.

Read the full file on GitHub · 429 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 11d ago First seen · 429 lines · 160 tokens per session scan A 04d8a6fe4b7d

Subscribe to this mod's changes

conversion-verifier is a skill published in the GitHub repository metrikia-io/marketing-skills (1 stars, last pushed 1mo ago), licensed MIT. It adds 160 tokens to every session and 5,108 once invoked, about $0.0008 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.

Related

Other skills, from other repositories

Threat Intelligence & CTI

Cyber threat intelligence production — the intelligence cycle, IOC extraction/normalization/enrichment, STIX/TAXII and MISP, structured analytic models (Diamond, Kill Chain, ATT&CK), source scoring, actor/campaign tracking, and finished intelligence reporting.

Masriyan/Claude-Code-CyberSecurity-Skill · 57 tokens

ads-performance-analytics

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…

rampstackco/claude-skills · 147 tokens

ads-creative-development

How to produce ad creative that converts at performance scale. Hook patterns, format selection, video pacing, variation systems, sequential testing methodology, fatigue detection, brand-voice alignment without conversion dilution, and platform-specific creative norms. Triggers on ad creative, ad design, hook patterns…

rampstackco/claude-skills · 124 tokens

paid-media-strategy

A discipline for running paid media that does not light money on fire. Hypothesis writing for paid spend, channel selection, budget allocation, audience targeting, bid strategy, campaign types, what NOT to spend on, attribution reality, and the failure modes that produce expensive lessons. Triggers on paid media…

rampstackco/claude-skills · 142 tokens

ecommerce-full-pipeline

An e-commerce workflow assistant covering product discovery, 1688 product collection, listing on multiple platforms, promotional copy, and short-video creation. 1688 is a Chinese online wholesale marketplace.

anbeime/skill · 96 tokens

absolute-simplify

Use when the user wants to simplify, clean up, refactor, tidy, or refine code — their staged/unstaged git changes or a target file/path. Reduces complexity, flattens nesting, removes redundancy and dead code, scores each change by value (holding low-value churn), then runs tests to prove nothing broke. Invoke on…

maddhruv/absolute · 178 tokens