CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

quickstart

Sign in through OAuth, confirm the workspace, and run a first report or campaign plan.

Quality

76%

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

Fix and improve this skill with Tessl

tessl review fix ./skills/quickstart/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.

A tight, well-sequenced quickstart that names exact tools, builds in error recovery for sign-in and account checks, and gates mutations behind explicit approval. The only notable issues are a redundant duplicate-URL sentence and reporting guidance that covers GA4 but not other connected platforms.

DimensionReasoningScore

Conciseness

The body is lean and assumes Claude's competence ("Call `get_connection_status`... then retry"), but "Cursor uses https://mcp.synterai.com; Claude uses https://mcp.synterai.com" repeats an identical URL and the closing OAuth sentence restates sign-in details from step 1 — minor instances that could be trimmed, matching anchor 4 rather than the every-token-earns-its-place anchor 5.

4 / 5

Actionability

Guidance names exact tools (`get_connection_status`, `list_connected_accounts`, `ga4_get_properties`, `ga4_get_report`) with concrete fallbacks ("If sign-in fails, reconnect from the client's plugin settings"), but only the GA4 reporting path is specified — step 2 mentions other platforms yet gives no tool guidance for them, a minor gap consistent with anchor 4 rather than fully covering the common cases (anchor 5).

4 / 5

Workflow Clarity

A clear 4-step sequence with explicit feedback loops at the fragile points — "Complete the client's browser OAuth prompt if requested, then retry. If sign-in fails, reconnect" and "If an account is missing, use the **connect** skill" — plus an approval gate before mutations ("obtain explicit approval before account mutations or spend changes"), matching anchor 5; no destructive/batch cap applies since no mutation workflow is described.

5 / 5

Progressive Disclosure

The skill is under 50 lines, single-purpose, with no external references needed; content is well organized into numbered steps, connection details, and a permissions note, and cross-skill pointers (**connect**, **help**) are clearly signaled — this meets the rubric's simple-skill exception allowing a 5 with well-organized sections.

5 / 5

Total

18

/

20

Passed

Description

55%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 states concrete onboarding actions in third person, but it answers only 'what' and leaves 'when' entirely unstated, and it lacks the domain keywords (GA4, ads, analytics) that would let a user's natural request trigger it. It is serviceable but below the rubric's good examples, which pair an action list with an explicit "Use when..." clause.

Suggestions

Add an explicit trigger clause, e.g. "Use when the user wants to set up, connect, or start using Synter for the first time."

Include natural domain keywords users would actually say — "GA4", "Google Ads", "analytics", "connect accounts" — so the description triggers on real requests.

Mention the product name (Synter) or another domain anchor to reduce overlap with generic reporting/marketing skills.

DimensionReasoningScore

Specificity

"Sign in through OAuth", "confirm the workspace", and "run a first report or campaign plan" list several concrete actions with minor gaps (anchor 4) — not 5 because coverage misses capabilities the body reveals (GA4 reports, audience review, ad-copy-generation), and not 3 because it goes beyond 1-2 actions and all are concrete.

4 / 5

Completeness

The 'what' is clear and concrete (sign in, confirm workspace, run a first report or campaign plan), but there is no "Use when..." clause or equivalent trigger guidance anywhere, which caps completeness at 3 per the rubric guideline; anchor 4 is ruled out because 'when' is not even weakly present.

3 / 5

Trigger Term Quality

"report" and "campaign plan" are natural user phrases, but the description omits the domain vocabulary users would actually say — "GA4", "Google Ads", "analytics", "connect", "get started" — matching anchor 3 (relevant keywords missing common variations) rather than anchor 4's good coverage.

3 / 5

Distinctiveness Conflict Risk

The OAuth/workspace onboarding sequence is somewhat specific, but "run a first report or campaign plan" overlaps with generic reporting and marketing skills and no product name (Synter) or domain anchor (GA4, ads) appears — anchor 3 rather than 4, since closely related analytics skills could plausibly trigger on the same phrasing.

3 / 5

Total

13

/

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/plugin

Path

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