Name: onespan
Rating: 60 (1 reviews)
Author: membranedev

onespan

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

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

Quality

Content

82%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 a tight, executable CLI guide with a well-sequenced connection workflow and explicit state-based checkpoints. Its main gaps are light over-explanation in the intro and shallow error-recovery guidance for failed connection states.

Suggestions

Add brief recovery guidance for CONFIGURATION_ERROR/SETUP_FAILED states beyond "check the error field," e.g. re-run `membrane connection ensure` or inspect logs.

Trim the opening OneSpan marketing paragraph to one line so the file leads with actionable setup steps.

Include one fully-worked action example with a concrete actionId and --input payload to anchor the abstract placeholders.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient CLI commands with operational detail, but the opening OneSpan overview paragraph and phrases like "so you can focus on the integration logic rather than auth plumbing" add minor over-explanation that could be trimmed.	4 / 5
Actionability	It provides copy-paste-ready commands covering the common cases — install, login, connection ensure/get with --wait, action list/run, and the proxy request flow with a full options table — all executable directly.	5 / 5
Workflow Clarity	A clear install → login → connect → poll → act sequence exists with explicit state checkpoints (READY/BUILDING/CLIENT_ACTION_REQUIRED) and a re-poll feedback loop, but error-state handling (CONFIGURATION_ERROR/SETUP_FAILED) only says to "check the error field" without recovery steps.	4 / 5
Progressive Disclosure	The single file is well organized into clearly headed sections (Overview, Install, Authentication, Connecting, Searching, Actions, Proxy, Best practices) with no nested references; appropriate for this scope, with only minor room to split a deeper reference out.	4 / 5
	Total	17 / 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 correctly names the OneSpan niche and includes an explicit "Use when" trigger, satisfying the what/when requirement. Its weakness is generic, non-concrete action verbs and thin keyword coverage of OneSpan's actual capabilities (e-signatures, identity verification, transactions).

Suggestions

Replace generic verbs with concrete OneSpan capabilities, e.g. "Create and send e-signature packages, verify identities, and manage transactions and records."

Broaden trigger terms to include natural phrasings users say, such as "e-signatures," "OneSpan transactions," or "identity verification."

Tighten the "when" clause to concrete triggers, e.g. "Use when the user wants to send documents for e-signature or manage OneSpan transactions."

Dimension	Reasoning	Score
Specificity	The actions named — "Manage data, records, and automate workflows" — are minimal and generic rather than concrete (no equivalents to "extracts text" or "fills forms"); it names the OneSpan domain but the verbs are abstract.	2 / 5
Completeness	Both "what" ("Manage data, records, and automate workflows") and "when" ("Use when the user wants to interact with OneSpan data") are present, but the "what" is generic and the "when" could name concrete trigger phrases.	4 / 5
Trigger Term Quality	"OneSpan" is a relevant keyword and "interact with OneSpan data" is a usable phrase, but natural variations and synonyms a user might say (e-signatures, transactions, identity verification) are missing.	3 / 5
Distinctiveness Conflict Risk	The "OneSpan" trigger is a clearly named product niche with minimal conflict risk, though the generic action verbs (manage data, records, workflows) leave minor overlap with broad data 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/onespan/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.