CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

paid-measurement-loop

Use when the user asks to "read back" a paid campaign change, "did this ad change work", or "compare ROAS/CPA before and after"; reads ROAS/CPA against a control over a fixed readback window and returns a Promote / Keep-testing / Rollback / Unproven readback decision with the math delegated to roi-calculator. Not for RQS scoring or veto adjudication — use ad-account-auditor; not for the ROI ratio math — use roi-calculator; not for cross-channel rollups — use performance-analyzer. 付费广告复盘/ROAS回看/投放效果归因

Quality

90%

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

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.

A well-engineered instruction skill: the readback workflow is unambiguous, sequenced, and rich with validation checkpoints and error-recovery rules, and it consistently delegates math and auditing to sibling skills. The main gaps are minor — placeholder values in the ledger command, an undefined numeric decision bar, some repeated boundary restatements, and references that all point outside the package and could not be verified.

Suggestions

Inline a compact default for the Promote/Rollback decision bar (e.g., a minimum delta-vs-control percentage or significance rule) so step 8 is executable without loading measurement-protocol.md.

Replace the '{"spend": ..., "revenue": ..., "conversions": ...}' placeholder with one complete ledger.py record example using realistic values.

Consolidate the auditor-boundary restatements (intro paragraph, step 7, step 8, Next Best Skill) into a single boundary note to cut repeated tokens.

DimensionReasoningScore

Conciseness

The body is dense with operational constraints Claude does not already know (learning-phase resets, "conversion lag (a click today converts days later...)", "Meta 7-day-click vs Google last-click are not comparable") rather than generic explanations, but the auditor/delegation boundary is restated in the intro, Skill Contract, steps 7–8, and Next Best Skill, which could be trimmed to a single note. This fits 'efficient; minor instances of over-explanation' rather than score 5's 'every token earns its place', and is clearly above score 3 since almost all content is skill-specific.

4 / 5

Actionability

Concrete, near-copy-paste commands are given ('python3 "${CLAUDE_PLUGIN_ROOT}/scripts/connectors/ledger.py" record <campaign> --source paid --data ...' plus diff/trend variants) and the Quick Start covers three common cases, but the ledger payload uses '{"spend": ..., "revenue": ..., "conversions": ...}' placeholders and the Promote/Rollback decision bar ('beats control past the bar') is never defined numerically inline. This matches 'mostly executable guidance with minor gaps' rather than score 5's fully copy-paste-ready coverage.

4 / 5

Workflow Clarity

Eight numbered steps in strict order with explicit stop conditions ('If the campaign is still in learning phase, **stop** — do not read or change it'), a validation checkpoint (step 7 signal-integrity check with 'mark the readback **Unproven**'), and a feedback loop ('State the concrete repair before any new readback... then restart the fixed readback window'), plus a 'Done when' checklist. This is the score-5 anchor: clear sequence, explicit validation, error-recovery loops, and a checklist.

5 / 5

Progressive Disclosure

Sections are clear and the Reference Materials list signals each external file with what it contains ('readback windows, required readback fields, the control rule...'), but no bundle exists in this package (no ./references/, ./scripts/, ./assets/) and every detailed reference resolves outside the skill via deep relative paths (../../../references/skill-contract.md, ../../orchestrate/ad-test-designer/references/measurement-control.md) that cannot be verified here. Good structure with minor organization gaps fits score 4; it is not score 5 because navigation to the referenced detail is unverifiable and paths escape the skill's own directory.

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.

An exemplary description: it answers what and when with quoted user-facing trigger phrases, states the concrete output (a four-way readback decision), and positively routes users away from three adjacent skills. No fluff or over-claims; the only cost is length, which is spent entirely on disambiguation and triggers.

DimensionReasoningScore

Specificity

It lists multiple concrete actions in third person — 'reads ROAS/CPA against a control over a fixed readback window', 'returns a Promote / Keep-testing / Rollback / Unproven readback decision', 'with the math delegated to roi-calculator' — comprehensively covering the skill's behavior. This matches score 5's 'multiple specific concrete actions; comprehensive coverage'; it is well above score 4 because no meaningful capability of the skill is left undescribed.

5 / 5

Completeness

It opens with an explicit 'Use when the user asks to...' clause containing concrete trigger phrases, then states clearly what the skill does (control-based ROAS/CPA readback over a fixed window returning a four-way decision). Both what and when are explicit with concrete triggers — the exact score-5 anchor — not merely the score-4 'when could be more explicit'.

5 / 5

Trigger Term Quality

It quotes the exact natural phrases a user would say ('"read back" a paid campaign change', '"did this ad change work"', '"compare ROAS/CPA before and after"') and adds bilingual synonyms ('付费广告复盘/ROAS回看/投放效果归因') plus domain terms ROAS and CPA. This is comprehensive natural-term coverage with synonyms, matching score 5 rather than score 4's 'a few natural terms missing'.

5 / 5

Distinctiveness Conflict Risk

It carves out a clear niche (the readback decision, window, and control) and explicitly disambiguates the three nearest skills ('Not for RQS scoring or veto adjudication — use ad-account-auditor; not for the ROI ratio math — use roi-calculator; not for cross-channel rollups — use performance-analyzer'). Minimal conflict risk, matching score 5 rather than score 4's 'minor overlap risk with closely related skills'.

5 / 5

Total

20

/

20

Passed

Validation

75%

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

Validation — 12 / 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: 16 suspicious

Warning

referenced_paths_exist

Referenced path issues: 1 missing, 1 deeper-than-1-level

Warning

Total

12

/

16

Passed

Repository

aaron-he-zhu/aaron-marketing-skills

Path

ad/scale/paid-measurement-loop/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.