CtrlK
BlogDocsLog inGet started
Tessl Logo

paid-ads-review

Produce a read-only, evidence-based paid-media performance review across connected platforms or supplied exports. Use for weekly or monthly reports, scorecards, performance, CPA, ROAS, CTR, spend trends, pacing, or conversion-tracking health.

65

Quality

79%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./paid-ads/paid-ads-review/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

85%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.

The body is an efficient, well-structured instruction skill: concise, action-oriented, with a clear sequenced workflow and built-in validation guardrails around tracking and unqualified aggregates. It earns the top score on conciseness and progressive disclosure and is just short of perfect on actionability and workflow clarity.

DimensionReasoningScore

Conciseness

The body is lean and assumes Claude's competence — no padding, no explaining what ROAS or CTR is — and every token earns its place while still covering method, delegation, reporting format, and guardrails.

5 / 5

Actionability

Concrete, executable guidance is present: specific delegate skills are named, the scorecard lists exact columns to include, and output ends with a defined hold/investigate/action choice; it falls short of fully copy-paste-ready only because no literal command or template is provided.

4 / 5

Workflow Clarity

A clear three-phase sequence (assemble evidence → report the decision → end with a verdict/route) is present with validation checkpoints (verify tracking before treating CPA/ROAS as decision-grade, mark absent tracking as blocking), but explicit error-recovery feedback loops are only implicit.

4 / 5

Progressive Disclosure

For an under-50-line, single-purpose skill with no external bundle files, the body is well-organized into clearly signaled sections and references to shared contracts and platform skills are one level deep with no nesting, satisfying the simple-skill exception for the top score.

5 / 5

Total

18

/

20

Passed

Description

73%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.

The description is strong: third-person, specific, and explicitly answers both what the skill does and when to use it with natural paid-media trigger terms. It is concise without padding, though it could list a few more discrete actions and synonyms to reach the top anchor.

DimensionReasoningScore

Specificity

Names the domain (paid-media performance review) and several concrete actions — 'read-only', 'evidence-based', 'pacing', 'conversion-tracking health' — but stops short of listing multiple discrete operations like a scorecard build or export handling.

4 / 5

Completeness

Clearly answers 'what' (produce a read-only evidence-based review) and 'when' (Use for weekly/monthly reports, scorecards, CPA/ROAS trends), with an explicit 'Use for' trigger clause; the 'when' could be marginally more specific but both halves are present.

4 / 5

Trigger Term Quality

Includes natural terms users would say — 'weekly or monthly reports', 'scorecards', 'CPA', 'ROAS', 'CTR', 'spend trends', 'pacing' — with good coverage, though a few common synonyms (e.g. 'ad spend', 'paid social') are missing.

4 / 5

Distinctiveness Conflict Risk

The paid-media niche is well-scoped with distinct triggers (CPA, ROAS, CTR, pacing) that are unlikely to fire for unrelated skills, with only minor overlap risk against a generic analytics skill.

4 / 5

Total

16

/

20

Passed

Validation

93%

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

Validation — 15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository
nowork-studio/notfair-plugin
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.