CtrlK
BlogDocsLog inGet started
Tessl Logo

twilio-identity-verification-advisor

Planning skill for identity verification and fraud prevention. Qualifies the developer's needs across authentication method, channel selection, fraud risk level, and user experience to recommend the right Twilio Verify + Lookup architecture. Handles login, signup, password reset, and risk-adaptive verification.

61

Quality

72%

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 ./plugins/twilio-developer-kit/skills/twilio-identity-verification-advisor/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

77%Weight 40%Scale 1-3

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

The body is a strong, actionable advisory skill with a clear sequenced workflow and concrete install recommendations, but it is somewhat padded by repeated Verify-vs-custom messaging and is a monolithic file that could offload reference detail to bundled files.

Suggestions

Consolidate the 'use the Verify API rather than building custom OTP logic' guidance into one location instead of repeating it in Step 1, Level 1, and Decision Rules.

Move the detailed Lookup Intelligence package reference and the per-channel description tables into a references/ file linked once from the body to improve progressive disclosure and trim the core SKILL.md.

Tighten channel one-liners (e.g. drop 'Growing.' and rationale prose) to lift token efficiency without losing the decision signal.

DimensionReasoningScore

Conciseness

The decision framework earns its place, but the 'use Verify, don't build custom OTP' recommendation is repeated across Step 1, Level 1, and Decision Rules, and channel descriptions like 'WhatsApp → Growing. Good for international users...' could be tightened, placing it at mostly-efficient rather than lean.

2 / 3

Actionability

Concrete and copy-paste ready: named skills to install (twilio-verify-send-otp, twilio-lookup-phone-intelligence), specific API calls (Lookup v2 with line_type_intelligence), a concrete error code (60202), and a ready-to-emit Output Format template — actionable guidance for an instruction-only skill.

3 / 3

Workflow Clarity

A clearly sequenced advisory workflow (Step 1 mode detection → Step 2 four qualifying questions → Step 3 verification ladder → Decision Rules → Output Format) with an explicit mode-routing checkpoint and qualification checklist; no destructive/batch operations require validation feedback loops.

3 / 3

Progressive Disclosure

Sections are well-organized with clear headers, but at ~167 lines the skill is a single monolithic file with no bundle files or references; detailed Lookup-package and channel reference material that could be split out is inline rather than one-level-deep.

2 / 3

Total

10

/

12

Passed

Description

67%Weight 40%Scale 1-3

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 specific, third-person, and distinctively scoped to Twilio Verify + Lookup, but stops short of an explicit 'Use when' trigger clause and omits the most common natural trigger terms (OTP, 2FA, MFA). Adding a trigger clause with those keywords would lift completeness and trigger-term quality.

Suggestions

Append an explicit 'Use when...' clause naming common triggers, e.g. 'Use when adding OTP, 2FA/MFA, phone/email verification, or fraud prevention to signup, login, or password-reset flows.'

Add the high-frequency natural terms (OTP, verification code, 2FA, MFA, two-factor, phone verification) into the description so the trigger_term_quality coverage reaches the full set.

Keep the third-person voice already in use; avoid drifting into 'you can use this' phrasing.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — 'Qualifies the developer's needs across authentication method, channel selection, fraud risk level, and user experience', 'recommend the right Twilio Verify + Lookup architecture', and 'Handles login, signup, password reset, and risk-adaptive verification' — matching the multi-action anchor.

3 / 3

Completeness

Clearly states what the skill does, but lacks an explicit 'Use when...' trigger clause; per the guidelines, a missing explicit trigger caps completeness at 2.

2 / 3

Trigger Term Quality

Includes some natural terms a developer would say ('identity verification', 'fraud prevention', 'login, signup, password reset'), but omits the most common variations (OTP, 2FA, MFA, phone verification) that appear only in the body, so coverage is incomplete.

2 / 3

Distinctiveness Conflict Risk

The narrow framing — 'recommend the right Twilio Verify + Lookup architecture' for identity verification — carves a clear niche unlikely to conflict with generic skills.

3 / 3

Total

10

/

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
openai/plugins
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.