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

64%

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 actionable skill with excellent executable examples covering the full porting workflow. Its main weaknesses are verbosity (the Key Concepts and Common Patterns sections significantly inflate the file without proportional value) and the lack of explicit validation/error-recovery workflows despite porting being a multi-step process with many failure modes. The content would benefit from trimming redundant sections and adding structured error handling guidance.

Suggestions

Add explicit validation checkpoints and error recovery flows — e.g., 'If portability check returns non-portable numbers, exclude them before creating the order' and 'If order status shows REJECTED, check rejectReason and resubmit with corrected end-user info'.

Move the lengthy 'Key Concepts' and 'Common Patterns' sections into a separate REFERENCE.md file, keeping only the most critical concepts inline to reduce the SKILL.md size by ~40%.

Consolidate the 'Gotchas and Best Practices' section — several items repeat information already covered in examples or Key Concepts (e.g., E.164 format, portability check advice).

DimensionReasoningScore

Conciseness

The skill is fairly well-structured but includes some unnecessary verbosity. The 'Key Concepts' section explains many terms that could be trimmed (e.g., definitions of LOA, FOC, End User are somewhat obvious in context). The 'Common Patterns' section largely repeats what's already shown in the examples above. The 'Gotchas' section is valuable but could be more concise. Overall, the content is useful but could be tightened significantly — the file is quite long for what it conveys.

2 / 3

Actionability

The skill provides fully executable curl commands with realistic request/response examples for all major operations (portability check, order creation, tracking, activation). The examples are copy-paste ready with proper environment variable usage, headers, and JSON payloads. Field references and constraints are specific and concrete.

3 / 3

Workflow Clarity

The skill presents a logical sequence (check portability → create order → track → activate) with clear individual steps, but lacks explicit validation checkpoints and error recovery loops. For example, there's no guidance on what to do if the portability check returns non-portable numbers, no validation step after order creation, and no explicit feedback loop for handling rejected orders or mismatched end-user info. The 'Always check portability first' advice is mentioned but not integrated into a formal workflow with branching.

2 / 3

Progressive Disclosure

The skill has reasonable section organization and links to external documentation and an authentication skill. However, the content is quite monolithic — the Key Concepts, Common Patterns, and Gotchas sections are all inline and lengthy, making the file very long. Some of this content (especially the full Common Patterns reference and detailed Key Concepts) could be split into separate reference files. No bundle files are provided to support progressive disclosure.

2 / 3

Total

9

/

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 an excellent skill description that clearly defines the domain (Sinch Porting API), lists specific concrete capabilities, and provides an explicit 'Use when...' clause with comprehensive trigger terms. It is highly distinctive and would be easy for Claude to correctly select from a large pool of skills.

DimensionReasoningScore

Specificity

Lists multiple specific concrete actions: port-in order creation, portability checks, order tracking, on-demand activation, webhook notifications, uploading LOA documents, and configuring porting defaults.

3 / 3

Completeness

Clearly answers both 'what' (port phone numbers, automates order creation, portability checks, tracking, activation, webhooks) and 'when' with an explicit 'Use when...' clause listing seven specific trigger scenarios.

3 / 3

Trigger Term Quality

Includes strong natural trigger terms users would say: 'porting numbers', 'portability', 'port-in orders', 'port status', 'ported numbers', 'LOA documents', 'porting defaults', 'Sinch', 'Porting API'. These cover a wide range of natural user queries about number porting.

3 / 3

Distinctiveness Conflict Risk

Highly distinctive with a clear niche: Sinch Porting API for phone number porting. The domain-specific terminology (port-in orders, LOA documents, portability checks, Sinch) makes 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