CtrlK
BlogDocsLog inGet started
Tessl Logo

phone-verification

Verify phone numbers using SMS one-time codes via the Didit API. Use when you need to confirm a user owns a phone number, implement SMS-based 2FA, or validate phone during signup/onboarding flows.

62

Quality

73%

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/research-tools/capabilities/phone-verification/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

57%

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

A compact, well-organized skill that is easy to navigate, but it is undercut by non-executable examples (the duplicated two-`-d` Workflow curls and an empty TypeScript config) and the absence of any failure/retry handling in the verification flow.

Suggestions

Fix the Workflow curl examples: they use two -d flags whose payloads collide; consolidate each into a single -d with the full JSON body as in Quick Start.

Complete the TypeScript integration example by populating the Orthogonal client config instead of leaving `new Orthogonal({})` empty.

Add the failure response shape and a short retry/expiry note to the Verify Code step so the workflow has an explicit validation checkpoint.

DimensionReasoningScore

Conciseness

The body is mostly lean, but the send/check curl invocations are duplicated almost verbatim between Quick Start and Workflow, and the Use Cases list is light padding that could be trimmed.

2 / 3

Actionability

Quick Start gives correct, copy-paste-ready curl, but the Workflow examples are broken (two -d flags, which merge into invalid JSON) and the TypeScript example leaves the client config empty, so key examples are not executable as written.

2 / 3

Workflow Clarity

The send-then-check sequence is clearly numbered, but only success responses are shown with no failure case, retry guidance, or validation checkpoint when a code is wrong or expired.

2 / 3

Progressive Disclosure

This is a single self-contained SKILL.md with no bundle files and clean section organization (Setup, Quick Start, Workflow, Format, Use Cases, Integration), which is appropriately structured for a skill of this size.

3 / 3

Total

9

/

12

Passed

Description

90%

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 well-constructed description: explicit "Use when" triggers, natural vocabulary, and a distinct niche. The only gap is that it foregrounds one core action rather than enumerating several concrete capabilities.

DimensionReasoningScore

Specificity

It names a concrete domain and mechanism ("Verify phone numbers using SMS one-time codes via the Didit API") but centers on a single action rather than listing multiple distinct concrete actions like the level-3 anchor (extract/fill/merge).

2 / 3

Completeness

It explicitly answers both what (verify phone numbers via SMS one-time codes through Didit) and when ("Use when you need to confirm a user owns a phone number, implement SMS-based 2FA, or validate phone during signup/onboarding flows").

3 / 3

Trigger Term Quality

It surfaces natural terms a user would actually say — "phone numbers", "SMS", "2FA", "signup/onboarding", "verification" — giving good coverage of common phrasings.

3 / 3

Distinctiveness Conflict Risk

Phone-number verification via SMS OTP through a named API is a clear niche with distinct triggers (2FA, signup phone validation) that is unlikely to fire for unrelated skills.

3 / 3

Total

11

/

12

Passed

Validation

93%

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

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository
gooseworks-ai/goose-skills
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.