CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

fatigue-frequency-manager

Use when the user asks to "is my ad fatiguing", "why is CTR dropping at scale", or "should I rotate creative / widen the audience"; reads frequency, CTR and CVR decay against an early-flight baseline and returns Rotate-creative / Widen-audience / Hold triggers with a per-ad-set fatigue read. Not for building the replacement creative — use ad-creative-builder; not for the RQS score or vetoes — use ad-account-auditor. 广告疲劳检测/频次管理/换素材还是扩人群

Quality

83%

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

70%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-structured diagnostic workflow with genuinely strong sequencing and validation logic — the fatigue-vs-saturation split, CVR-truth-set check, and decision gate are concrete and executable. Its weaknesses are repeated boundary/restatement padding across sections and a reference graph that points entirely to files missing from the presented bundle, leaving key templates and thresholds unverifiable.

Suggestions

State the skill's boundaries (not ad-creative-builder, not ad-account-auditor, asks before writing memory) once — in the intro or Skill Contract — and drop the repetitions in step 5, Save Results, Reference Materials, and Next Best Skill.

Include the referenced files (skill-contract.md §Handoff Summary Format and §Save Results Template, measurement-protocol.md frequency ceilings, roas-benchmark.md R1/R2) in the bundle, or inline the minimal versions of the handoff/save templates so the skill is self-contained when the paths don't resolve.

Replace the ellipsis placeholders in the ledger.py record example with one filled example row (realistic frequency/ctr/cvr/reach values) so the command is copy-paste runnable.

DimensionReasoningScore

Conciseness

The instructions are tight domain guidance with no explanations of concepts Claude already knows, but the same boundary statements are repeated several times — "does not build the replacement creative (`ad-creative-builder` owns that) and does not compute the RQS" (intro), "Only `ad-account-auditor` computes the RQS or runs vetoes" (Reference Materials), "this skill flags; it does not score or veto" (step 5, repeated in Next Best Skill), and "This skill asks before writing memory" (Save Results) — plus the intro paragraph restating the frontmatter description and the Skill Contract's Expected output duplicating step 6.

3 / 5

Actionability

Gives a concrete executable command with its argument shape (`python3 "${CLAUDE_PLUGIN_ROOT}/scripts/connectors/ledger.py" record <ad-set> --source paid --data '{...}'` plus the `trend` invocation), an exact memory path and filename convention (`memory/ad/fatigue-frequency-manager/YYYY-MM-DD-<ad-set>-fatigue.md`), an explicit per-ad-set output field list, and precise stop-and-ask conditions. Not 5: the ledger example uses ellipsis placeholders rather than a filled runnable sample, and both output templates (handoff summary, save-results) are deferred to external files instead of shown.

4 / 5

Workflow Clarity

Six clearly sequenced steps with explicit validation checkpoints: stop if the set is still in learning phase (step 1), verify a CVR drop against the GA4/ecommerce order truth set before calling it saturation (step 5), a Decision Gate enumerating exact stop-and-ask vs continue-silently conditions, and a "Done when" checklist with routing on failed validation (flag → ad-account-auditor). Not 4: the checkpoints are explicit and outcome-routed, not merely present.

5 / 5

Progressive Disclosure

Sections are well organized and each reference is clearly signaled with a description of what it holds, but every referenced file — skill-contract.md, measurement-protocol.md, roas-benchmark.md, CONNECTORS.md, SECURITY.md, scripts/connectors/README.md, and the sibling SKILL.mds — is absent from the bundle (no references/, scripts/, or assets/ directories exist, and the ../../../ paths resolve to files that do not exist), so the deferred content (handoff format, save template, frequency ceilings, R1/R2 veto definitions) is unreachable. Not 4 because references cannot be considered 'mostly clear' when none of them resolve; not 2 because the body itself is well-sectioned and references are prominently labeled, not buried.

3 / 5

Total

15

/

20

Passed

Description

95%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: concrete trigger phrases in the user's own words, a precise statement of what it does and does not do, and explicit disambiguation from sibling skills. The only minor deduction is capability coverage that stops short of the diagnosis and memory-handoff actions the body actually performs.

DimensionReasoningScore

Specificity

Concrete, domain-specific actions: "reads frequency, CTR and CVR decay against an early-flight baseline and returns Rotate-creative / Widen-audience / Hold triggers with a per-ad-set fatigue read". Not 5: coverage stops at reading decay and returning triggers — the fatigue-vs-saturation diagnosis and memory-write that the skill performs are absent, and the trailing untranslated keyword string adds no capability. Not 3: far more specific than 1-2 generic actions.

4 / 5

Completeness

Explicitly answers both: what ("reads frequency, CTR and CVR decay against an early-flight baseline and returns ... triggers with a per-ad-set fatigue read") and when ("Use when the user asks to ..." with three concrete trigger phrases), going further with explicit not-for boundaries. Third-person voice throughout.

5 / 5

Trigger Term Quality

Quotes verbatim natural user phrasings — "is my ad fatiguing", "why is CTR dropping at scale", "should I rotate creative / widen the audience" — exactly what a media buyer would say, plus domain keywords (frequency, CTR, CVR, rotate creative, widen audience) and Chinese-language synonyms (广告疲劳检测/频次管理/换素材还是扩人群).

5 / 5

Distinctiveness Conflict Risk

Clear niche (ad fatigue/saturation diagnosis at scale) with explicit carve-outs to siblings — "Not for building the replacement creative — use ad-creative-builder; not for the RQS score or vetoes — use ad-account-auditor" — so it is unlikely to trigger for the wrong skill.

5 / 5

Total

19

/

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: 14 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/fatigue-frequency-manager/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.