identity-verification-didit

Identity verification via phone/email OTP and AML screening using Didit API

Quality

69%

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/identity-verification-didit/SKILL.md

Quality

Content

72%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 body is highly actionable with complete curl examples and full parameter docs for every endpoint, and it is reasonably concise, but it inlines a large API reference instead of splitting it into reference files and lacks explicit send→check workflow sequencing with validation checkpoints.

Suggestions

Add an explicit end-to-end workflow (send email/phone code → check the returned code → interpret the response) with a validation step, especially for the OTP verification flow.

Move the bulky per-endpoint parameter tables into a references/ file (e.g. REFERENCE.md) and keep SKILL.md as an overview with one-line links, improving progressive disclosure.

Trim the marketing-style AML intro paragraph to a one-line purpose statement to tighten conciseness.

Dimension	Reasoning	Score
Conciseness	The body is mostly lean — capability list, parameter tables, and copy-paste curl per endpoint — with only minor padding such as the AML intro "This API provides real-time screening capabilities to detect potential matches and mitigate risks associated with financial fraud and terrorism", fitting 'efficient; minor instances of over-explanation that could be trimmed' rather than the fully lean anchor 5.	4 / 5
Actionability	Every endpoint has a complete, copy-paste-ready curl call with auth headers and a JSON body, and all parameters are enumerated with types and defaults, matching 'fully executable; copy-paste ready code or commands; specific examples cover the common cases'.	5 / 5
Workflow Clarity	The setup sequence is clear, but the core send-then-check OTP flow is only implied by separate endpoint sections, there are no validation checkpoints, and the AML/verification operations lack explicit verify-after-call feedback loops; per the destructive/batch cap guidance this fits anchor 3 ('sequence present but checkpoints missing or implicit') and cannot exceed it.	3 / 5
Progressive Disclosure	Structure is reasonable (Setup, Capabilities, Usage, Use Cases, Discover More) and the Discover More search/details calls defer detail well, but the long per-endpoint parameter references are all inlined in a ~165-line SKILL.md with no separate reference files, matching 'some structure but could be better organized; content that should be separate is inline'.	3 / 5
	Total	15 / 20 Passed

Description

66%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 specific and distinct, naming concrete verification actions and the Didit API, but it omits any 'Use when' trigger guidance and drops the Database Validation capability, capping completeness and limiting trigger-term breadth.

Suggestions

Add a 'Use when ...' clause naming concrete triggers, e.g. 'Use when verifying users via phone/email OTP codes, screening customers against AML/sanctions watchlists, or validating identity data for KYC compliance'.

Mention the Database Validation capability and natural synonyms (KYC, two-factor/2FA, sanctions screening) to broaden trigger coverage and completeness.

Keep third-person voice (already used) and avoid adding marketing language when extending the description.

Dimension	Reasoning	Score
Specificity	"Identity verification via phone/email OTP and AML screening using Didit API" lists several concrete actions (phone OTP, email OTP, AML screening), with the main gap being the omitted Database Validation capability, fitting 'lists several specific actions; minor gaps in coverage' rather than the comprehensive anchor 5.	4 / 5
Completeness	The 'what' is clear but there is no 'Use when...' or equivalent trigger clause, which per the judging guidelines caps completeness at 3; this matches the anchor 'has a clear what but when is missing or only weakly implied' and is below 4 where 'when' must be explicit.	3 / 5
Trigger Term Quality	Natural terms a user would say are present — "identity verification", "OTP", "AML screening", "phone/email" — but common synonyms like KYC, two-factor/2FA, and sanctions/watchlist screening are missing, matching 'good keyword coverage; a few natural terms missing'.	4 / 5
Distinctiveness Conflict Risk	The combination of phone/email OTP, AML screening, and the named Didit API carves a fairly distinct niche with minor overlap risk against generic identity/KYC skills, fitting 'mostly distinct; minor overlap risk' rather than the minimal-conflict anchor 5.	4 / 5
	Total	15 / 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/identity-verification-didit/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.