Name: acuant
Rating: 52.8 (1 reviews)
Author: membranedev

Blog Docs Log in Get started

acuant

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

Quality

58%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./skills/acuant/SKILL.md

Quality

Content

77%

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

This is a solid, actionable skill that provides clear CLI commands and a well-structured connection workflow with proper state handling. Its main weaknesses are some unnecessary introductory content about Acuant that wastes tokens, and a cryptic 'Acuant Overview' section that lists entities without explanation or context. The Membrane CLI integration pattern is well-documented with good error handling guidance.

Suggestions

Remove or drastically shorten the introductory paragraph about what Acuant is—Claude already knows this, and the skill description covers it.

Either explain the 'Acuant Overview' bullet list (Credential, Face, Backside, Result, Settings, Log) with actionable context or remove it entirely, as it currently adds confusion without value.

Dimension	Reasoning	Score
Conciseness	The skill includes some unnecessary explanation (e.g., describing what Acuant is, what industries use it) that Claude already knows. The Membrane CLI instructions are reasonably efficient but could be tightened—some sections like the overview of Acuant and the best practices contain filler. The proxy request table and connection state explanations are useful but slightly verbose.	2 / 3
Actionability	The skill provides concrete, executable CLI commands for every step: installation, authentication, connection setup, action discovery, action execution, and proxy requests. Commands are copy-paste ready with clear flag descriptions and JSON output options.	3 / 3
Workflow Clarity	The multi-step connection workflow is clearly sequenced with explicit state checks (READY, BUILDING, CLIENT_ACTION_REQUIRED, errors), polling instructions with --wait flag, and clear branching logic for each state. The flow from install → authenticate → connect → discover actions → run actions is well-structured with validation checkpoints.	3 / 3
Progressive Disclosure	The content is a single monolithic file with no references to supporting documents. The Acuant Overview section with its bullet list (Credential, Face, Backside, Result, Settings, Log) is cryptic and unexplained—it could benefit from linking to detailed documentation. However, for a skill of this size (~120 lines), the inline structure is acceptable, though the overview section adds confusion rather than clarity.	2 / 3
	Total	10 / 12 Passed

Description

40%

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

This description is weak across most dimensions. While it technically includes a 'Use when' clause and names a specific platform (Acuant), the capabilities described are extremely generic and could apply to almost any integration. The description fails to communicate what Acuant actually does (identity verification, document authentication) or what specific actions the skill enables.

Suggestions

Replace generic phrases like 'manage data, records, and automate workflows' with specific Acuant capabilities such as 'verify identity documents, authenticate IDs, perform KYC checks, scan driver licenses and passports'.

Expand the 'Use when' clause with natural trigger terms users would actually say, e.g., 'Use when the user mentions Acuant, identity verification, document authentication, ID scanning, KYC, or needs to validate government-issued IDs'.

Add domain-specific context to distinguish this from other integration skills, e.g., mentioning that Acuant is an identity verification and document authentication platform.

Dimension	Reasoning	Score
Specificity	The description uses vague language like 'manage data, records, and automate workflows' without specifying any concrete actions. It doesn't explain what kind of data, records, or workflows are involved with Acuant.	1 / 3
Completeness	It has a 'Use when' clause ('Use when the user wants to interact with Acuant data'), but the 'what' is extremely vague ('manage data, records, and automate workflows') and the 'when' is essentially a tautology that doesn't add meaningful trigger guidance.	2 / 3
Trigger Term Quality	It includes 'Acuant' as a specific trigger term which is useful for brand-specific queries, but lacks natural keywords users might say such as 'identity verification', 'document authentication', 'ID scanning', or 'KYC' which are Acuant's core domain.	2 / 3
Distinctiveness Conflict Risk	The mention of 'Acuant' provides some distinctiveness as a brand-specific integration, but 'manage data, records, and automate workflows' is so generic it could overlap with virtually any integration or data management skill.	2 / 3
	Total	7 / 12 Passed

Validation

90%

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 — 10 / 11 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	10 / 11 Passed

Repository: membranedev/application-skills
Path: skills/acuant/SKILL.md
Commit: f484c82

Reviewed: 1 day 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.