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.

Quality

70%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

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

Quality

Content

53%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 content is well-structured and mostly actionable, but suffers from duplicated curl examples, a broken `-d` usage in the Workflow section, an incomplete TypeScript constructor, and absent error-handling guidance for the verification flow.

Suggestions

Fix the Workflow curl examples: the two `-d` flags produce malformed JSON — merge the body into a single `-d` JSON object as done in Quick Start.

Remove the duplicated curl blocks between Quick Start and Workflow, or have Quick Start reference the Workflow steps to avoid redundancy.

Add a failure-handling section covering wrong/expired codes and resends, plus complete the TypeScript `Orthogonal({})` constructor with required configuration.

Consider moving the TypeScript integration example into a separate reference file to keep SKILL.md a lean overview.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient and free of beginner-concept padding, but the same curl request is duplicated across Quick Start and the Workflow section, which could be tightened into a single canonical example.	3 / 5
Actionability	Quick Start curl examples are executable, but the Workflow 'Send Verification Code'/'Verify Code' examples use two `-d` flags producing malformed JSON, and the TypeScript example has an empty `Orthogonal({})` constructor, so key details are missing rather than merely minor gaps.	3 / 5
Workflow Clarity	The send-then-verify sequence is clearly numbered, but there are no validation checkpoints or feedback loops for failure cases (wrong/expired code, rate limits, resend), leaving error handling implicit.	3 / 5
Progressive Disclosure	Well-organized into clear sections with no nested references and no bundle files present, though the TypeScript integration example is sizeable enough that it could arguably live in a separate reference file.	4 / 5
	Total	13 / 20 Passed

Description

87%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 is strong: it concisely states the capability and gives explicit, varied trigger conditions in third person. It is clearly distinguishable and actionable with only minor keyword-coverage gaps.

Dimension	Reasoning	Score
Specificity	Lists several concrete actions ('Verify phone numbers using SMS one-time codes', 'confirm a user owns a phone number', 'implement SMS-based 2FA', 'validate phone') with only minor coverage gaps, fitting the 'several specific actions' anchor rather than the fully comprehensive 5.	4 / 5
Completeness	Explicitly states both what it does ('Verify phone numbers using SMS one-time codes via the Didit API') and when to use it via a concrete 'Use when...' clause with multiple trigger phrases, matching the top anchor.	5 / 5
Trigger Term Quality	Good natural keyword coverage ('phone numbers', 'SMS', 'one-time codes', '2FA', 'signup/onboarding') that users would say, though synonyms like 'OTP' or 'verification code' are missing, keeping it just below 5.	4 / 5
Distinctiveness Conflict Risk	Occupies a clear niche (SMS phone verification via Didit) with distinct triggers (2FA, signup/onboarding, ownership confirmation) and minimal overlap with other skills.	5 / 5
	Total	18 / 20 Passed

Validation

93%

Warnings & errors only

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

Validation — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

Repository: gooseworks-ai/goose-skills
Path: skills/research-tools/capabilities/phone-verification/SKILL.md
Commit: 2523432

Reviewed: 7 days ago

Table of Contents

Discovery Implementation Validation

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.