CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

pixel-capi-setup

Set up Synter Pixel and server-side CAPI destinations across Meta, Google, TikTok, and more via Synter MCP. Use when installing pixels, configuring CAPI forwarding, verifying pixel ownership, or fixing conversion tracking before scale.

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

63%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 well-structured and sequenced with named MCP tools and a sensible verify-before-audit flow, but it stops short of executable detail for its core task (per-platform CAPI configuration) and carries a promotional footer plus duplicated tier messaging that wastes tokens. It works as a checklist but would leave Claude guessing at configuration specifics.

Suggestions

Add a short per-platform configuration reference (e.g., a table or 2-3 line examples mapping Meta CAPI, Google Enhanced Conversions, and TikTok Events API to the key arguments configure_pixel_destination needs) so the core 'Configure' step is executable rather than implied.

Trim or move the 'About this skill' footer content — the duplicated 'Solo / Scale / Crucible Managed (never a Free cloud tier)' note and utm-tagged links add no operational value for executing the skill.

Add an explicit error-recovery branch to the setup loop, e.g., 'If verify_pixel_ownership fails or health is red: check destination config, re-run configure_pixel_destination, re-verify before proceeding.'

DimensionReasoningScore

Conciseness

The operational core (prerequisites, tool table, setup loop) is lean, but the 'About this skill' section is purely promotional ('Skills files are free to clone; hosted Synter is never a Free cloud tier', repeated links), and 'Solo / Scale / Crucible Managed (never a Free cloud tier)' is stated twice — some unnecessary padding that could be trimmed, matching the 3 anchor rather than the 2 anchor's several padded sections.

3 / 5

Actionability

Concrete MCP tool names and a step-to-tool mapping are provided ('configure_pixel_destination', 'get_pixel_health', 'shopify_create_web_pixel'), but the skill's core action — configuring destinations per platform — is left as 'configure_pixel_destination per platform (Meta CAPI, Google EC, etc.)' with no argument examples or per-platform patterns, a key missing detail that keeps it below the 4 anchor's 'minor gaps'.

3 / 5

Workflow Clarity

The setup loop gives a clear Inventory → Configure → Verify → Audit sequence with an explicit checkpoint ('verify_pixel_ownership on key landing pages') and a safety guard ('Do not pause or scale campaigns... while pixel health is red'). It misses the 5 anchor's error-recovery feedback loop for what to do when verification fails, landing on 'clear sequence with most checkpoints present'.

4 / 5

Progressive Disclosure

A single-file skill under 50 lines with well-organized sections (Prerequisites, Core MCP tools, Setup loop, Related skills) and no external references needed; per the simple-skill guideline this merits a 5 on organization alone, and cross-references to sibling skills are one level deep and clearly signaled.

5 / 5

Total

15

/

20

Passed

Description

88%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, concise, with a clear capability statement and an explicit 'Use when...' clause carrying concrete triggers. Trigger synonym coverage is good rather than exhaustive, and 'fixing conversion tracking' slightly overlaps sibling audit/diagnostic skills.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — 'Set up Synter Pixel and server-side CAPI destinations', 'installing pixels, configuring CAPI forwarding, verifying pixel ownership, or fixing conversion tracking' — across named platforms (Meta, Google, TikTok), giving comprehensive coverage of the niche. The only hedge is 'and more', which is too minor to drop it to the 4 anchor's 'minor gaps in coverage'.

5 / 5

Completeness

Explicitly answers both: the 'what' ('Set up Synter Pixel and server-side CAPI destinations across Meta, Google, TikTok... via Synter MCP') and the 'when' ('Use when installing pixels, configuring CAPI forwarding, verifying pixel ownership, or fixing conversion tracking before scale') with concrete trigger phrases, exactly matching the 5 anchor.

5 / 5

Trigger Term Quality

Good natural keyword coverage: 'installing pixels', 'CAPI forwarding', 'conversion tracking', 'pixel ownership', plus platform names users actually say. Common synonyms like 'server-side tracking', 'Meta/Facebook Pixel', or 'Google Enhanced Conversions' are absent, so it falls short of the comprehensive-synonym coverage of the 5 anchor.

4 / 5

Distinctiveness Conflict Risk

The Synter-MCP-scoped pixel/CAPI setup niche is mostly distinct, but 'fixing conversion tracking' overlaps with the sibling skills the body itself names (pixel-capi-auditor, tracking-leak-detector), creating minor conflict risk with closely related skills rather than the 5 anchor's minimal risk.

4 / 5

Total

18

/

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/free-skills

Path

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