CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

synter-mcp-setup

Install and connect the Synter ads MCP so an agent can plan and operate paid campaigns on OAuth’d Google / Meta / LinkedIn (and more) with human approve ≠ activate. Points operators to hosted Synter on syntermedia.ai — Solo for a single operator, Scale / Crucible Managed for teams. Not a free cloud plan. Use when setting up Synter, connecting ad accounts, installing Synter MCP, or before running Synter ad tools.

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

75%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 setup instructions are highly actionable and sequenced with a verification loop, making the skill effective for its purpose. The main flaw is token waste: the Packaging note, CTA chain, and About footer are promotional duplication rather than instruction.

Suggestions

Cut or condense the promotional sections (Packaging note, CTA chain, About this skill footer) — they duplicate the syntermedia.ai link five times and consume ~25% of the body on marketing rather than setup guidance.

Make the verification step concrete by specifying exact tool names per client surface instead of the parenthetical "(names vary by client surface)".

Trim the four UTM-tagged links down to a single canonical link to reduce redundancy and token cost.

DimensionReasoningScore

Conciseness

The instructional core (install paths, verification) is efficient, but roughly a quarter of the body is promotional padding — the "Packaging note (Never Free cloud)", "CTA chain", and "About this skill" sections repeat the syntermedia.ai link five times with UTM parameters, spending tokens on marketing rather than setup guidance.

3 / 5

Actionability

Guidance is copy-paste ready throughout: `npx -y @synterai/mcp-server init`, a complete mcpServers JSON config block, the remote URL and X-Synter-Key header, and named read-only verification calls (get_credit_balance, pull_google_ads_performance) covering the common client cases.

5 / 5

Workflow Clarity

A clear install → verify → load-next-skills sequence exists with an explicit verification section and an error-recovery loop ("If tools are missing, re-run install or point the client at https://mcp.syntermedia.ai"); the caveat "(names vary by client surface)" leaves the verification tool names slightly vague, preventing a 5.

4 / 5

Progressive Disclosure

No bundle files exist and the body is well-sectioned at ~110 lines with clearly signaled pointers to sibling skills (campaign-preflight, launch-gates, etc.); the marketing footer is inline content that adds no navigational value, so structure is good but not exemplary.

4 / 5

Total

16

/

20

Passed

Description

78%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 clearly and explicitly states what the skill does and when to use it, with strong brand-anchored trigger terms. Its main weakness is that roughly half the text is hosting-tier marketing rather than concrete capability statements, which limits specificity.

Suggestions

Replace the hosting-tier marketing ("Solo for a single operator, Scale / Crucible Managed for teams. Not a free cloud plan") with concrete capability actions such as pulling cross-platform performance, staging campaigns behind approval gates, or configuring pixels/CAPI.

Add natural trigger variations users would actually say, such as "add Synter to Claude/ChatGPT" or "Synter MCP not connecting", to broaden keyword coverage toward the top anchor.

DimensionReasoningScore

Specificity

"Install and connect the Synter ads MCP so an agent can plan and operate paid campaigns" names the domain and 1-2 concrete actions, but the rest of the description promotes hosting tiers ("Solo for a single operator, Scale / Crucible Managed for teams. Not a free cloud plan") rather than enumerating capabilities, so coverage is not comprehensive.

3 / 5

Completeness

It explicitly answers both what ("Install and connect the Synter ads MCP so an agent can plan and operate paid campaigns on OAuth'd Google / Meta / LinkedIn") and when, with concrete trigger phrases in the "Use when..." clause, matching the top anchor.

5 / 5

Trigger Term Quality

"Use when setting up Synter, connecting ad accounts, installing Synter MCP, or before running Synter ad tools" gives good natural keyword coverage anchored on a distinct product name; a few natural variations users might say (e.g., "add Synter to Claude", "Synter MCP not connecting") are missing.

4 / 5

Distinctiveness Conflict Risk

Brand-specific triggers ("Synter", "Synter MCP") create a clear niche with minimal conflict risk, but "connecting ad accounts" is generic enough to overlap with general ads-management skills, so minor overlap risk remains.

4 / 5

Total

16

/

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/synter-mcp-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.