CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

synter

Use when the user asks about ad performance, campaign reports, budgets, or approved changes on Google, Meta, LinkedIn, TikTok, Reddit, X, Microsoft and other ad platforms. Loads the Synter MCP server.

Quality

84%

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

SKILL.md
Quality
Evals
Security

Quality

Content

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

An exemplary lean skill body: it adds only what Claude could not know (pricing, approval flow, auth handling, platform scope) and organizes it cleanly for a simple skill. The one notable gap is onboarding — the hosted MCP server URL and API key are mentioned without instructions for connecting, which is the main thing keeping actionability and workflow clarity from 5.

DimensionReasoningScore

Conciseness

Roughly twenty lean lines covering pricing, safety, auth, example prompts, and rules with no padding and no explanation of concepts Claude already knows. Every token earns its place, matching anchor 5 rather than anchor 4 (which reserves room for minor over-explanation).

5 / 5

Actionability

Concrete example prompts and executable rules ("Start with read tools. Show the plan for any write and get explicit approval first") give mostly actionable guidance, but the setup gap — the MCP server URL and SYNTER_API_KEY are named without any instruction for how to actually connect the server — keeps it from anchor 5's fully copy-paste-ready coverage.

4 / 5

Workflow Clarity

A clear read-first sequence with an explicit approval checkpoint before money-spending writes, plus expired-connection recovery guidance. It lacks the full validate → fix → retry feedback loop of anchor 5, fitting "clear sequence with most checkpoints; minor validation gaps" at anchor 4.

4 / 5

Progressive Disclosure

The skill is under 50 lines with no need for external references, and its sections (overview, good first prompts, agent rules) are well organized and easy to navigate. Per the rubric's simple-skill guidance, this earns anchor 5.

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.

A strong, concise description with an explicit trigger clause and excellent distinctiveness from named ad platforms. Its main weakness is that the stated capability is only "Loads the Synter MCP server" — what the server actually does (reports, approved changes) is left implicit in the trigger list — and a few natural trigger terms ("ads", "advertising", "spend") are missing.

Suggestions

State the concrete capabilities alongside the trigger, e.g. "Pulls performance reports and executes approved budget/campaign changes across ad platforms, then list "ads", "advertising", and "spend" among trigger terms to catch more natural user phrasings.

Trim the platform list slightly (e.g. "Google, Meta, LinkedIn, TikTok, and other ad platforms") to free description space for stating what the skill does, since the body already claims 43-platform coverage.

DimensionReasoningScore

Specificity

The only explicitly stated capability is "Loads the Synter MCP server"; "ad performance, campaign reports, budgets, or approved changes" are trigger topics rather than stated actions. This names the domain with one concrete action, matching anchor 3, not 4 which requires several specific listed actions.

3 / 5

Completeness

The "Use when the user asks about..." clause gives a strong, explicit 'when', and "Loads the Synter MCP server" provides a 'what', but the what is thin — it never states the server performs reports or approved changes. Both present with one weaker side matches anchor 4; anchor 3 would require a missing or only implied 'when', which is not the case.

4 / 5

Trigger Term Quality

"ad performance, campaign reports, budgets, approved changes" plus eight named platforms (Google, Meta, LinkedIn, TikTok, Reddit, X, Microsoft) are natural user phrases, but common variations like "ads", "advertising", "spend", or "CPA/ROAS" are missing. Good coverage with a few natural terms absent fits anchor 4 rather than 5.

4 / 5

Distinctiveness Conflict Risk

A clear niche (ad-platform performance and approved changes) with named-platform triggers; no plausible overlap with generic skills. This matches anchor 5 (clear niche with distinct triggers, minimal conflict risk).

5 / 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/synter-amp-orbs-starter

Path

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