Name: jumio
Rating: 57.599999999999994 (1 reviews)
Author: membranedev

Blog Docs Log in Get started

jumio

Jumio integration. Manage data, records, and automate workflows. Use when the user wants to interact with Jumio data.

Quality

66%

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/jumio/SKILL.md

Quality

Content

75%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 delivers mostly executable, well-organized guidance for connecting to Jumio and running or proxying actions, with a clear state-driven connection workflow. It is held back from the top band by light filler, an abstract intent placeholder, and slightly inconsistent step labeling.

Dimension	Reasoning	Score
Conciseness	The body is mostly lean with tight, executable command blocks, but the intro paragraph and lines like 'so you can focus on the integration logic rather than auth plumbing' add minor over-explanation that could be trimmed.	4 / 5
Actionability	Concrete, copy-paste-ready commands cover install, auth, connection, action search/run, and proxying, with a clear flag table; minor gaps remain around the abstract '--intent "QUERY"' placeholder and the lack of a full end-to-end run example with real parameters.	4 / 5
Workflow Clarity	The connection flow is well sequenced with explicit state checkpoints (READY / CLIENT_ACTION_REQUIRED / CONFIGURATION_ERROR) and a poll-after-action feedback loop; the inconsistent '1b' and 'Step 2' labeling and absence of one overarching numbered workflow keep it from a 5.	4 / 5
Progressive Disclosure	The single file is well organized into clear headed sections with no nested or broken references, and no bundle files are needed; minor gaps like the inlined proxy flag table and the thin stub 'Jumio Overview' section keep it from a 5.	4 / 5
	Total	16 / 20 Passed

Description

57%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 answers both what and when and anchors clearly on the Jumio service, but its capabilities are stated as generic verbs rather than concrete identity-verification actions, and trigger coverage relies almost entirely on the single word 'Jumio'.

Suggestions

Replace generic verbs with concrete Jumio actions, e.g. 'Initiate identity and document verification, retrieve verification status and records, and automate KYC workflows.'

Expand trigger terms to include natural synonyms users say, such as 'identity verification', 'KYC', 'document verification', or 'Jumio checks'.

Make the 'when' clause more concrete, e.g. 'Use when the user wants to run Jumio identity/KYC verifications or retrieve verification records.'

Dimension	Reasoning	Score
Specificity	The description names the Jumio domain but its actions — 'Manage data, records, and automate workflows' — are generic verbs with no concrete operations, matching the anchor 'Names the domain but actions are minimal or generic'.	2 / 5
Completeness	Both a 'what' ('Jumio integration. Manage data, records, and automate workflows.') and an explicit 'when' ('Use when the user wants to interact with Jumio data.') are present; the 'when' is somewhat generic, so it is not a 5.	4 / 5
Trigger Term Quality	'Jumio' and 'Jumio data' are natural terms a user would say, but coverage stops there — identity-verification, KYC, and verification synonyms are absent, leaving common variations missing.	3 / 5
Distinctiveness Conflict Risk	Naming the specific Jumio service gives it a clear niche with low conflict risk, but the generic 'manage data, records, automate workflows' verbs create minor overlap with other data-management skills.	4 / 5
	Total	13 / 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: membranedev/application-skills
Path: skills/jumio/SKILL.md
Commit: f484c82

Reviewed: 5 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.