CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

ad-account-auditor

Use when auditing a paid ad account for incremental contribution, wasted spend, or measurement integrity before scaling; runs a typed 20-item ROAS profile with verified vetoes and a SHIP/FIX/BLOCK/UNDECIDED gate on own exported data. Not for campaign structure design — use campaign-architect; not for creative production — use ad-creative-builder. 付费广告账户审计/ROAS评分

Quality

84%

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

77%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 tightly written, professionally structured auditor skill with an explicit gated workflow, validation checkpoints, and persistence feedback loops. Its main weaknesses are progressive disclosure: the majority of referenced runbooks, benchmarks, and the validation script live outside the bundle as unverifiable relative paths, and reference listings are duplicated between the Runtime Reads and Reference Materials sections.

Suggestions

Bundle or inline the essential content from the out-of-skill references (auditor-runbook.md, scoring-semantics.md, roas-benchmark.md, runtime-invocation.md) so every referenced path resolves within the skill folder instead of pointing three levels up to '../../../references/'.

Deduplicate the reference lists: 'Runtime Reads' and 'Reference Materials' both cite auditor-runbook.md, scoring-semantics.md, and roas-benchmark.md — consolidate into a single clearly signaled section.

Ship 'validate-audit-artifact.py' in a scripts/ folder (or state its canonical location and how to obtain it) since the Persistence workflow depends on it but it is absent from the bundle.

DimensionReasoningScore

Conciseness

The body is dense and assumes competence — it never explains concepts Claude already knows and every section carries operational content ('Score all 20 R1..S5 criteria from the benchmark with source/date/type/confidence'). It misses the 5 anchor because of minor redundancy: 'auditor-runbook.md', 'scoring-semantics.md', and 'roas-benchmark.md' are each listed twice (under 'Runtime Reads' and again under 'Reference Materials'), and cryptic cross-references like 'bare IDs that collide with RAMP/ECHO/TALE' and 'the 59 ceiling' could be tightened. It is well above the 3 anchor since there is no padded or unnecessary explanation.

4 / 5

Actionability

Mostly executable guidance: an exact runtime-root resolution command, five named veto conditions with verification standards (ROAS-R1 through ROAS-A1), a concrete persistence path pattern 'memory/audits/ad/YYYY-MM-DD-<topic>.md' with 'validate-audit-artifact.py against that intended --relative-path', and worked examples with real numbers ('raw 78, one verified R1 failure: DONE_WITH_CONCERNS/FIX, final 59'). It is not a 5 because key execution details are deferred to external files (the scorer, runbook) and the validator script is referenced but not bundled, leaving minor gaps; it clearly exceeds the 3 anchor's pseudocode-level guidance.

4 / 5

Workflow Clarity

The workflow is clearly sequenced (declare context → normalize currency/windows/IDs/lag → score all 20 items → verify vetoes → run typed scorer → report with exact typed header) with an explicit 'Validation Checkpoints' checklist and a validate→write→revalidate feedback loop in Persistence ('Assemble and validate the complete v3 draft... persist only through one full-content Write, then revalidate the target'). Worked examples cover both success and failure paths, matching the 5 anchor's explicit validation steps and error-recovery loops rather than the 4 anchor's 'minor validation gaps'.

5 / 5

Progressive Disclosure

The one bundled reference (references/auditor-runtime.md, a 404-line self-contained runtime) is clearly signaled and one level deep, but most referenced materials are not present in the bundle: '../../../references/auditor-runbook.md', 'scoring-semantics.md', 'roas-benchmark.md', 'runtime-invocation.md', 'measurement-protocol.md', and 'validate-audit-artifact.py' all point outside the skill folder and cannot be verified, and the reference lists are duplicated across two sections. This places it at the 3 anchor (structure present but organization/navigation compromised) rather than 4 (references mostly clear and verifiable) — though it is above 2 since real structure exists and nothing is a monolithic wall of text.

3 / 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 strong, well-scoped description with explicit what/when triggers, concrete output states, and explicit negative boundaries that route to sibling skills. Main weakness is unexplained internal jargon ('typed', 'verified vetoes') and missing common synonyms/platform names in the trigger terms.

DimensionReasoningScore

Specificity

Quotes several concrete actions — 'runs a typed 20-item ROAS profile with verified vetoes and a SHIP/FIX/BLOCK/UNDECIDED gate on own exported data' and auditing for 'incremental contribution, wasted spend, or measurement integrity' — with only minor coverage gaps. It falls short of the 5 anchor because terms like 'typed' and 'verified vetoes' are unexplained jargon, but exceeds the 3 anchor by listing multiple specific actions and concrete output states rather than just 1-2.

4 / 5

Completeness

Explicitly answers both questions: the 'what' is 'runs a typed 20-item ROAS profile with verified vetoes and a SHIP/FIX/BLOCK/UNDECIDED gate on own exported data', and the 'when' is a concrete 'Use when auditing a paid ad account for incremental contribution, wasted spend, or measurement integrity before scaling' clause, reinforced with explicit negative triggers. The 'when' is explicit and specific with concrete trigger phrases, matching the 5 anchor rather than the 4 anchor's 'could be more explicit'.

5 / 5

Trigger Term Quality

Includes natural phrases users would say when needing this skill: 'auditing a paid ad account', 'wasted spend', 'ROAS', 'before scaling', 'measurement integrity', plus the Chinese '付费广告账户审计/ROAS评分'. Good but not comprehensive coverage — common variations like 'PPC', 'paid media', 'ad spend', or platform names (Google Ads, Meta) are missing, so it sits between the 4 and 5 anchors, clearly above the 3 anchor's 'some relevant keywords'.

4 / 5

Distinctiveness Conflict Risk

Occupies a clear niche (auditing/gating an account, not building or fixing it) and actively disambiguates: 'Not for campaign structure design — use campaign-architect; not for creative production — use ad-creative-builder'. This explicit routing to sibling skills gives minimal conflict risk, matching the 5 anchor.

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

Warning

Total

13

/

16

Passed

Repository

aaron-he-zhu/aaron-marketing-skills

Path

ad/activate/ad-account-auditor/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.