CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

platform-benchmarks

Ground channel-mix and budget-split decisions in typical CPM, CPC, and CPA ranges per platform, and set realistic performance expectations. Use when a user asks what to expect on a platform, how to split budget across channels, or whether their numbers are normal.

Quality

82%

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

The canonical home for this skill is platform-benchmarks in Synter-Media-AI/plugin

SKILL.md
Quality
Evals
Security

Quality

Content

71%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 lean, well-organized advisory skill with concrete tool names, clear sequencing, and good guardrail rules. Its central weakness is that it promises 'typical CPM, CPC, and CPA ranges per platform' in its description but provides no actual ranges in the body, leaving its core deliverable unfulfilled when account history is unavailable.

Suggestions

Include actual directional benchmark ranges (e.g., typical CPM/CPC/CPA bands per platform) in the body or a references file, or explicitly state where to source current ranges, since the skill's name and description promise them but none appear.

Spell out the fallback workflow when no account history exists for a platform (e.g., how to combine industry benchmarks with a forecast_campaign run and how to label the confidence of the projection).

Remove the duplicated caveats between the intro paragraph and the Rules section ('not as a promise' vs. 'Never present a benchmark as a guaranteed result') to tighten the token budget.

DimensionReasoningScore

Conciseness

The body is lean, assumes Claude's competence (no explaining what CPM or a funnel is), and every section carries account-specific information. Minor duplication between the intro ('not as a promise; the account's own history beats any benchmark') and the Rules section ('Never present a benchmark as a guaranteed result', 'Prefer the account's own history') could be trimmed, so it falls just short of the 5 anchor.

4 / 5

Actionability

Concrete elements exist (named tools like 'pull_google_ads_performance', 'forecast_campaign', per-platform behavioral notes, explicit handoffs to media-plan and launch), but the body contains no actual CPM/CPC/CPA ranges — the skill's namesake deliverable promised in the description — leaving only qualitative direction ('low CPM', 'higher CPC'). This is a missing key detail, not a minor gap, so it does not reach the 4 anchor.

3 / 5

Workflow Clarity

A clear sequence is present: pull account data first via named tools, use benchmarks only for 'platforms not yet run or for a directional split', weight the split with 'a rationale and projected CPA per channel', then hand off to media-plan and launch, with Rules acting as guardrails including an explicit fallback ('If you do not have a real number, say so'). It is not 5 because there are no explicit validation checkpoints or feedback loops, though the advisory (non-destructive) nature means the validation cap does not apply.

4 / 5

Progressive Disclosure

The skill is under 50 lines with no bundle files (references/, scripts/, assets/ do not exist) and no content that needs external files; the four section headers ('Use the account's own data first', 'How platforms typically behave', 'Splitting budget', 'Rules') are well-organized, which per the rubric guideline earns a 5 for a simple skill.

5 / 5

Total

16

/

20

Passed

Description

83%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 description with explicit what/when structure, concrete metrics, and natural trigger phrases. Its main gaps are the absence of platform names and the synonym 'benchmarks', which keep trigger coverage and distinctiveness just below the top anchors.

DimensionReasoningScore

Specificity

Names concrete actions ('Ground channel-mix and budget-split decisions', 'set realistic performance expectations') with specific metrics (CPM, CPC, CPA), but says only 'per platform' without naming platforms or covering more actions, so coverage has minor gaps rather than being comprehensive.

4 / 5

Completeness

Explicitly answers both 'what' (ground channel-mix and budget-split decisions in CPM/CPC/CPA ranges, set realistic expectations) and 'when' with three concrete trigger phrases in an explicit 'Use when...' clause. Not 4 because the 'when' clause is already specific and concrete, matching the 5 anchor.

5 / 5

Trigger Term Quality

Includes natural user phrasings like 'what to expect on a platform', 'how to split budget across channels', and 'whether their numbers are normal', but omits common synonyms such as 'benchmarks' and specific platform names (Google Ads, Meta) users would say.

4 / 5

Distinctiveness Conflict Risk

The ad-platform benchmark niche is clear and mostly distinct, but 'how to split budget across channels' and 'set realistic performance expectations' have minor overlap risk with media-planning and forecasting skills. Not 5 because these triggers could plausibly fire a closely related skill.

4 / 5

Total

17

/

20

Passed

Validation

100%

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

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

Synter-Media-AI/plugin

Path

packages/claude-directory/skills/platform-benchmarks/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.