CtrlK
BlogDocsLog inGet started
Tessl Logo

sinch-partnerships-ecosystems/sinch-skills

Official Sinch API skills for AI coding agents — SMS, Voice, Verification, Numbers, Mailgun email, and more.

71

Quality

88%

Does it follow best practices?

Impact

No eval scenarios have been run

SecuritybySnyk

Advisory

Suggest reviewing before use

This plugin was archived by the owner on Jun 4, 2026

Reason: we moved this to another workspace

Overview
Quality
Evals
Security
Files

Quality

Content

72%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

This is a comprehensive and well-organized skill for the Sinch Conversation API that excels in actionability with executable examples and progressive disclosure with well-signaled references. Its main weaknesses are moderate verbosity with some repeated information across sections (region mismatch warnings appear at least 3 times) and the lack of explicit validation checkpoints in the workflow, particularly for credential verification and error recovery loops.

Suggestions

Consolidate repeated warnings (region mismatch, Content-Type header) into a single 'Gotchas' entry rather than restating them in the Getting Started section and elsewhere.

Add an explicit validation step after credential setup, e.g., 'Verify setup: GET /v1/projects/$SINCH_PROJECT_ID/apps — expect 200 with your app listed. If 404, check region. If 401, re-check OAuth token.'

DimensionReasoningScore

Conciseness

The skill is generally informative but includes some redundant explanations (e.g., repeating the Content-Type header requirement, restating region mismatch warnings multiple times across sections, explaining what DISPATCH mode does in multiple places). Some sections like 'Key Concepts' border on reference documentation that could be offloaded. However, most content is relevant and not padded with things Claude already knows.

2 / 3

Actionability

The skill provides fully executable curl examples, concrete environment variable setup, specific script invocations with flags, and precise API endpoints. The first API call example is copy-paste ready, and the common patterns section gives concrete JSON structures for recipients and message types.

3 / 3

Workflow Clarity

The 'Agent Instructions' section provides a clear initial decision tree (SDK vs API, language choice), and the getting started flow is sequential. However, there are no explicit validation checkpoints — for example, no step to verify credentials work before sending messages, no verification step after webhook registration, and no feedback loop for handling common errors like 404 region mismatches during setup.

2 / 3

Progressive Disclosure

The skill is well-structured as an overview with clear one-level-deep references to external files (references/templates.md, references/batch.md, references/channels/*.md, references/webhooks/triggers/), sibling skills (sinch-sdks, sinch-authentication), and external documentation. Navigation is clearly signaled with descriptive link text and organized by topic.

3 / 3

Total

10

/

12

Passed

Description

100%

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

This is a strong skill description that clearly communicates what the skill does (send/receive messages across multiple channels via Sinch Conversation API), when to use it (explicit 'Use when' clause with diverse trigger terms), and is highly distinctive due to the specific platform and channel references. The description is concise yet comprehensive, covering both the unified API concept and the specific message types supported.

DimensionReasoningScore

Specificity

Lists multiple specific concrete actions: sends and receives omnichannel messages, and enumerates specific message types like rich cards, carousels, templates, batch messages, and multi-channel messaging.

3 / 3

Completeness

Clearly answers both 'what' (sends and receives omnichannel messages via Sinch Conversation API across multiple channels) and 'when' (explicit 'Use when' clause listing specific trigger scenarios like sending texts, WhatsApp messages, rich cards, etc.).

3 / 3

Trigger Term Quality

Excellent coverage of natural terms users would say: SMS, WhatsApp, RCS, MMS, Viber, Messenger, texts, WhatsApp messages, rich cards, carousels, templates, batch messages, multi-channel messaging. These are all terms a user would naturally use.

3 / 3

Distinctiveness Conflict Risk

Highly distinctive with clear niche: Sinch Conversation API for omnichannel messaging. The specific platform names (Sinch), channel types (WhatsApp, RCS, Viber), and message formats (rich cards, carousels) make it very unlikely to conflict with other skills.

3 / 3

Total

12

/

12

Passed

Validation

90%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation10 / 11 Passed

Validation for skill structure

CriteriaDescriptionResult

metadata_field

'metadata' should map string keys to string values

Warning

Total

10

/

11

Passed

Reviewed

Table of Contents