CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

pixel-capi-auditor

Audit pixel and Conversions API (CAPI) implementations across all ad platforms. Use when verifying tracking setup, diagnosing conversion data discrepancies, optimizing Event Match Quality, or auditing deduplication logic.

Quality

81%

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

67%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 exceptionally actionable — executable commands, complete payloads, and pass/fail checklists for every platform — and workflows are reasonably clear with embedded verification steps. Its main weaknesses are a monolithic single-file structure with no reference files for per-platform detail, plus marketing footer and case-study padding that waste context tokens.

Suggestions

Split each platform section (Meta, Google, TikTok, LinkedIn, Reddit, Microsoft) into its own reference file (e.g., references/meta-capi.md) and keep SKILL.md as an overview with clearly signaled one-level-deep links.

Remove the promotional 'About this skill' footer and trim the narrative before/after metrics in the Examples section to reclaim context tokens.

Add an explicit top-level audit workflow section (e.g., 1. capture click IDs, 2. run per-platform checklists, 3. verify deduplication, 4. prioritize fixes) instead of embedding the priority order only in Example 3.

DimensionReasoningScore

Conciseness

The reference material (tables, payloads, curl commands) is dense and assumes domain knowledge rather than explaining basics, but the promotional 'About this skill' footer ('Want this skill (and 40+ more) running on autopilot...') and narrative case-study claims ('Attributed conversions increased 42%', 'CPA decreased 28%') are unnecessary padding. Could be tightened by removing marketing content and trimming the illustrative Examples section.

3 / 5

Actionability

Copy-paste-ready curl commands per platform with full JSON payloads, checklists with exact pass criteria ('`event_id` matches pixel + CAPI', 'Score ≥ 6.0'), specific UI verification paths (Events Manager → Test Events), and concrete dedup verification steps. Only the cross-platform middleware block is explicit pseudocode, which is appropriate for a flexible pattern.

5 / 5

Workflow Clarity

Per-platform audit checklists provide sequenced checks with pass criteria, and the deduplication section has an explicit verify loop (trigger test conversion → check event appears once → confirm 'Deduplicated'). Missing a top-level end-to-end audit sequence — the prioritized remediation order only appears inside Example 3 rather than as a stated workflow.

4 / 5

Progressive Disclosure

A ~500-line monolithic SKILL.md inlines all six platforms' reference material (payloads, endpoints, checklists) that clearly belongs in per-platform reference files; no bundle files or references exist at all. Section headers are well-organized (above anchor 1's 'minimal structure'), but there is no progressive disclosure whatsoever, fitting the 'content that clearly belongs in separate files is inlined' anchor.

2 / 5

Total

14

/

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 description: third-person voice, concrete actions, an explicit 'Use when...' clause with domain-specific trigger phrases, and a well-delineated niche. Minor room to broaden natural keyword variations (e.g., 'server-side tracking', 'conversion tracking', platform names).

DimensionReasoningScore

Specificity

Lists several concrete actions ('verifying tracking setup, diagnosing conversion data discrepancies, optimizing Event Match Quality, or auditing deduplication logic'), though the what-side rests on the single umbrella verb 'Audit pixel and Conversions API (CAPI) implementations' with the specifics pushed into the trigger clause. Not 5 because the action list in the 'what' portion is thinner than the comprehensive example; clearly above 3's '1-2 concrete actions'.

4 / 5

Completeness

Explicitly answers both: what ('Audit pixel and Conversions API (CAPI) implementations across all ad platforms') and when ('Use when verifying tracking setup, diagnosing conversion data discrepancies, optimizing Event Match Quality, or auditing deduplication logic') with concrete trigger phrases, matching the anchor-5 example structure.

5 / 5

Trigger Term Quality

Includes natural domain phrases users would say: 'pixel', 'Conversions API (CAPI)', 'conversion data discrepancies', 'Event Match Quality', 'deduplication'. Missing common variations like 'server-side tracking', 'conversion tracking', or platform names ('Meta pixel'), so not the comprehensive synonym coverage of a 5.

4 / 5

Distinctiveness Conflict Risk

Clear niche (ad-platform conversion tracking audit) with distinct technical triggers like 'Event Match Quality' and 'deduplication logic' that are unlikely to fire for unrelated skills; minimal conflict risk.

5 / 5

Total

18

/

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

skill_md_line_count

SKILL.md is long (522 lines); consider splitting into references/ and linking

Warning

Total

15

/

16

Passed

Repository

Synter-Media-AI/free-skills

Path

skills/pixel-capi-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.