CtrlK
BlogDocsLog inGet started
Tessl Logo
PluginPublic

synter/outbound-replies

Triage and answer replies to cold email campaigns in Synter Outbound — separate real humans from auto-responders, classify intent, draft a reply in the sender's voice, and route opt-outs to suppression. Use when a user asks about outbound replies, their unibox, who responded to a campaign, or wants to answer a prospect.

Quality

97%

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

Overview
Quality
Evals
Security
Files

Quality

Content

100%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 an exemplary instruction-only skill: lean, concrete, and sequenced with explicit validation gates and error-recovery loops. Nothing explained that Claude already knows, and every instruction is directly executable against named tools.

DimensionReasoningScore

Conciseness

Every line is operational — the campaign-216 statistic, the classification table, tool names, and voice rules all carry instructions Claude does not already know, with zero padding or explanation of familiar concepts.

5 / 5

Actionability

Concrete tool invocations (outbound_reply_queue, outbound_approve_reply, action_card with domain/action parameters), verbatim example phrases per classification, and a copy-paste reporting template fully cover the common cases; per the rubric's scoring notes, an instruction-only skill needs actionable guidance, not code, and this delivers it.

5 / 5

Workflow Clarity

The body sequences filter → classify → draft → approval → book → report, with an explicit approval checkpoint ('Every reply to a real person needs explicit approval before it goes') and a dedicated error-recovery section covering rejected drafts and ambiguous classifications — textbook feedback loops.

5 / 5

Progressive Disclosure

A single-purpose skill of ~60 well-organized lines with no external files needed; sections are clearly headed, the one cross-reference (outbound-research) is clearly signaled, and all content appropriately lives inline.

5 / 5

Total

20

/

20

Passed

Description

92%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: concrete third-person actions, an explicit 'Use when' clause with natural trigger phrases, and clear product scoping. The only gap is a few missing everyday synonyms for reply-related requests.

DimensionReasoningScore

Specificity

The description lists five concrete actions — 'separate real humans from auto-responders, classify intent, draft a reply in the sender's voice, and route opt-outs to suppression' — giving comprehensive coverage of the skill's capabilities with no generic filler.

5 / 5

Completeness

It explicitly answers both 'what' (triage, classify, draft, route opt-outs) and 'when' with a concrete 'Use when...' clause listing specific trigger scenarios, matching the top anchor exactly.

5 / 5

Trigger Term Quality

Triggers include natural phrases users would say ('outbound replies, their unibox, who responded to a campaign, or wants to answer a prospect'), but common synonyms like 'email responses' or 'replied to my email' are missing, keeping it just below comprehensive coverage.

4 / 5

Distinctiveness Conflict Risk

Scoping to 'Synter Outbound' with distinct triggers (unibox, campaign replies, opt-outs) creates a clear niche with minimal risk of triggering for the wrong skill.

5 / 5

Total

19

/

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.

Reviewed

On this page