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

92%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Quality

Content

85%Weight 40%Scale 1-3

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A well-structured, actionable instruction skill with a clear sequenced workflow, validation checkpoints, and clean one-level reference navigation. The main weakness is repeated restatement of the same scope/negative-scope boundary across several sections, which inflates token use without adding new information.

Suggestions

State the negative-scope boundary (vs conversion-signal-qa, attribution-reconciler, ad-account-auditor) once in the intro scope line and reference it from later sections rather than re-explaining it in steps 1, 7, Reference Materials, and Next Best Skill.

De-duplicate the 'Done when' criteria against the step-8 launch-readiness statement, which currently overlap on 'fix missing margins / undefined proxies / count-vs-value gap'.

The Quick Start block repeats the bid-goal and export-paste pattern three times; consider one canonical example plus a one-line note on the variant inputs.

Dimension	Reasoning	Score
Conciseness	Mostly efficient and domain-specific, but the negative-scope disambiguation (not conversion-signal-qa / not attribution-reconciler / not ad-account-auditor) is restated across the intro, step 1, step 7, Reference Materials, and Next Best Skill, adding repetition that could be tightened.	2 / 3
Actionability	Instruction-only yet highly actionable: concrete formulas (net_value = revenue × margin; proxy_value = avg_order_net_value × lead→sale close_rate), a Measured/User-provided/Estimated labeling scheme, explicit file paths, and 8 specific numbered steps with decision rules.	3 / 3
Workflow Clarity	An 8-step sequenced workflow with explicit checkpoints — the value-vs-count reconciliation (step 7), a launch-readiness gate (step 8), 'needs-input' error markers, and a 'Done when' checklist functioning as validation.	3 / 3
Progressive Disclosure	Well-organized into clear sections with one-level-deep, clearly signaled references (skill-contract.md, CONNECTORS.md, SECURITY.md, roas-benchmark.md, sibling SKILL.md files) each annotated with what it contains; no nested reference chains.	3 / 3
	Total	11 / 12 Passed

Description

100%Weight 40%Scale 1-3

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, third-person description with explicit 'Use when' triggers, concrete enumerated capabilities, and crisp negative-scope routing that distinguishes it from sibling skills. Voice and trigger guidance both satisfy the rubric's anchor requirements.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions — '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' — rather than vague language.	3 / 3
Completeness	Explicitly answers both 'what' ('defines and QAs the conversion VALUE model...as a value-model spec plus a pre-launch value QA sheet') and 'when' via a leading 'Use when the user asks to...' clause.	3 / 3
Trigger Term Quality	Quotes natural phrasings a user would actually say ('set up conversion values so tROAS optimizes profit not orders', 'map margin onto my purchase value', 'stop bidding to revenue when I care about profit'), giving strong trigger coverage.	3 / 3
Distinctiveness Conflict Risk	Carves a clear niche and explicitly routes away from siblings ('Not for whether the tag fires...use conversion-signal-qa; not for cross-platform double-count de-dup...use attribution-reconciler; not for scoring R1/R2...ad-account-auditor'), making wrong-skill triggering unlikely.	3 / 3
	Total	12 / 12 Passed

Validation

81%

Warnings & errors only

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

Criteria	Description	Result
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
Commit: 4a77c48

Reviewed: 9 days ago

Table of Contents

Discovery Implementation Validation

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.