CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

conversion-value-mapper

Use when the user asks to "set up conversion values so tROAS optimizes profit not orders", "map margin onto my purchase value", "build value rules for lead / phone / signup conversions", or "stop bidding to revenue when I care about profit"; defines and QAs the conversion VALUE model — per-conversion values, margin/net-value adjustment, static-vs-dynamic value rules, proxy values for non-revenue actions, and a value-vs-count sanity check — as a value-model spec plus a pre-launch value QA sheet. Not for whether the tag fires or UTMs are clean — use conversion-signal-qa; not for cross-platform double-count de-dup — use attribution-reconciler; not for scoring R1/R2 — that is a scored veto in ad-account-auditor. 付费广告转化价值建模/利润出价/价值规则QA

Quality

90%

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

81%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.

The body is a strong, contract-driven instruction skill: an unambiguous 8-step workflow with real validation gates, concrete formulas, and disciplined labeling/escalation rules. Its weaknesses are moderate — repeated scope/boundary restatements, no worked example of the deliverable spec, and reliance on cross-skill references that live outside the skill bundle and cannot be verified from this directory.

Suggestions

State the scope/boundary line once (opening paragraph or Skill Contract) and have steps 1, 7, and the Reference Materials section reference it by name instead of restating it, reclaiming several lines of token budget.

Add a short worked example or row-level template of the value-model spec / QA sheet (one revenue conversion with margin adjustment, one non-revenue proxy with its derivation) so the deliverable format is concrete rather than described in prose.

Consolidate the external file links into the Reference Materials section and confirm the target paths resolve within the published bundle, so progressive disclosure does not depend on files outside the skill directory.

DimensionReasoningScore

Conciseness

The body is information-dense with no concept-teaching padding, but the scope/boundary line (values vs signal-fires vs R1/R2 scoring) is restated in the opening paragraph, step 1, step 7, Reference Materials, and Next Best Skill — redundant trimmable material. It is not a 3 because nothing explains concepts Claude already knows and every section carries actionable content.

4 / 5

Actionability

Guidance is concrete for an instruction-only skill: exact formulas (net_value = revenue × margin (or revenue − COGS); proxy_value = avg_order_net_value × lead→sale close_rate), a Measured/User-provided/Estimated labeling scheme, specific output paths, and needs-input escalation rules instead of guessing. It falls short of 5 because the deliverable itself (value-model spec and QA sheet) is described only in prose — no worked example or row-level template shows what a finished spec looks like.

4 / 5

Workflow Clarity

Eight clearly sequenced steps with explicit validation checkpoints — the step-7 value-vs-count reconciliation (with a 3× phantom-value flag example) and the step-8 launch-readiness gate that requires listing exactly what to fix — plus error-recovery routing (needs-input states, hop to attribution-reconciler or conversion-signal-qa) and a "Done when" checklist. This matches the anchor with explicit validation, feedback loops, and a checklist rather than merely having most checkpoints.

5 / 5

Progressive Disclosure

Sections are well organized and every reference is signaled with its purpose, and the core instructions appropriately live inline. It is not a 5 because the skill ships no local bundle (references/, scripts/, assets/ are absent) while pointing to files two-to-three directory levels outside itself (../../scale/attribution-reconciler/SKILL.md, ../../../references/skill-contract.md, ../../../CONNECTORS.md), and the same links are scattered inline across nearly every section rather than consolidated once — minor organization gaps rather than a fully self-contained or cleanly split structure.

4 / 5

Total

17

/

20

Passed

Description

100%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.

The description is exemplary: concrete and comprehensive capabilities, natural trigger phrases quoted verbatim, explicit use-when guidance, and explicit disambiguation from adjacent skills. The only nit is a trailing Chinese summary ("付费广告转化价值建模/利润出价/价值规则QA") that duplicates the summary field, adding mild verbosity without harming any scored dimension.

DimensionReasoningScore

Specificity

The description enumerates the full capability set in third person — "defines and QAs the conversion VALUE model — per-conversion values, margin/net-value adjustment, static-vs-dynamic value rules, proxy values for non-revenue actions, and a value-vs-count sanity check — as a value-model spec plus a pre-launch value QA sheet" — which is comprehensive rather than having minor gaps.

5 / 5

Completeness

It explicitly answers both halves: an explicit "Use when the user asks to..." clause with concrete trigger phrases, and a clear statement of what it produces (value-model spec plus pre-launch value QA sheet), going beyond the anchor-4 case where the 'when' is present but less explicit.

5 / 5

Trigger Term Quality

Four natural quoted user phrasings ("set up conversion values so tROAS optimizes profit not orders", "map margin onto my purchase value", "build value rules for lead / phone / signup conversions", "stop bidding to revenue when I care about profit") plus the domain vocabulary (tROAS, max-conversion-value, GA4, COGS, margin) give comprehensive coverage of how users would actually ask for this.

5 / 5

Distinctiveness Conflict Risk

Explicit negative-scope clauses ("Not for whether the tag fires or UTMs are clean — use conversion-signal-qa; not for cross-platform double-count de-dup — use attribution-reconciler; not for scoring R1/R2") carve out a clear niche with minimal conflict risk against sibling skills.

5 / 5

Total

20

/

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: 18 suspicious

Warning

Total

13

/

16

Passed

Repository

aaron-he-zhu/aaron-marketing-skills

Path

ad/activate/conversion-value-mapper/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.