CtrlK
BlogDocsLog inGet started
Tessl Logo

idnow

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

55

Quality

62%

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 ./skills/idnow/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

67%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 strong executable CLI guidance with a clear connection workflow and state-based error handling. Its main weaknesses are the large padded 'IDnow Overview' bullet tree and minor workflow-labeling inconsistencies that slightly hurt conciseness and clarity.

Suggestions

Trim or collapse the 'IDnow Overview' bullet tree (lines 21–65) into a brief pointer — it adds ~40 lines of structure with little actionable value.

Fix the dangling step references: label the connection steps consistently (1, 2, ...) so 'skip to Step 2' and '1b' resolve to real headers.

Add a brief validation/check step before running actions or proxy requests (e.g., confirm connection state is READY and verify the actionId from `action list` before `action run`).

DimensionReasoningScore

Conciseness

The CLI commands are lean, but the 40-line 'IDnow Overview' bullet tree and asides like 'so you can focus on the integration logic rather than auth plumbing' are padding that could be trimmed, fitting 'mostly efficient but includes some unnecessary explanation'.

3 / 5

Actionability

Concrete, copy-paste-ready `membrane` commands cover login, connection ensure, polling, action list/run, and proxy requests with a flag table; only minor abstract guidance like 'Use action names and parameters as needed' keeps it from a 5.

4 / 5

Workflow Clarity

The connect → poll → search → run sequence is clear with state-based branching (READY / CLIENT_ACTION_REQUIRED / CONFIGURATION_ERROR) and a retry loop, but dangling 'Step 2' and '1b' labels and the absence of pre-action validation are minor gaps.

4 / 5

Progressive Disclosure

With no bundle files present, the single SKILL.md is organized into clear sections (Install, Authentication, Connecting, Searching, Popular actions, Best practices); the inlined overview bullet tree is the main organization gap keeping it from 5.

4 / 5

Total

15

/

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 pairs a 'what' with an explicit 'Use when' trigger and targets a distinct named platform, but its capability verbs are generic ('manage data, records, automate workflows') rather than concrete IDnow-specific actions. Tightening the action list to specific IDnow operations would lift specificity and completeness.

Suggestions

Replace generic verbs ('Manage data, records, automate workflows') with concrete IDnow capabilities (e.g., 'Start and monitor identity verifications, retrieve identification documents, manage transaction types and tags').

Add natural trigger variations beyond 'IDnow data' — e.g., 'identity verification', 'KYC checks', 'video identification' — to improve trigger-term coverage.

DimensionReasoningScore

Specificity

The description names the IDnow domain but its actions — "Manage data, records, and automate workflows" — are generic and abstract rather than concrete capabilities, matching the 'names the domain but actions are minimal or generic' anchor.

2 / 5

Completeness

It has both a 'what' ("Manage data, records, and automate workflows") and an explicit 'when' ("Use when the user wants to interact with IDnow data"), but the 'what' is generic so it does not reach the fully concrete anchor 5.

4 / 5

Trigger Term Quality

The relevant keyword "IDnow" appears in both the what and the "Use when..." clause, but no synonyms or natural variations are offered, fitting 'some relevant keywords but missing common variations'.

3 / 5

Distinctiveness Conflict Risk

IDnow is a distinct named platform and the trigger "interact with IDnow data" is specific, leaving only minor overlap risk from the generic 'manage data/records/workflows' verbs.

4 / 5

Total

13

/

20

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
membranedev/application-skills
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.