acuant
Acuant integration. Manage data, records, and automate workflows. Use when the user wants to interact with Acuant data.
66
58%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Advisory
Suggest reviewing before use
Optimize this skill with Tessl
npx tessl skill review --optimize ./skills/acuant/SKILL.mdQuality
Discovery
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 relies heavily on the 'Acuant' brand name for identification but fails to explain what Acuant actually does or what specific capabilities the skill provides. The actions listed are generic placeholders that could apply to virtually any integration, and the 'Use when' clause merely restates the obvious without providing meaningful trigger guidance.
Suggestions
Replace vague actions with specific Acuant capabilities, e.g., 'Verify identity documents, authenticate IDs, perform facial recognition matching, check document validity' (or whatever Acuant-specific operations are supported).
Expand trigger terms to include domain-specific keywords users would naturally say, such as 'identity verification', 'ID authentication', 'document scanning', 'KYC', or 'identity proofing'.
Strengthen the 'Use when' clause with concrete scenarios, e.g., 'Use when the user needs to verify identity documents, authenticate IDs, or perform KYC checks through Acuant.'
| 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, nor what specific operations can be performed. | 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 just restating the what. The trigger guidance is too generic to be useful. | 2 / 3 |
Trigger Term Quality | It includes 'Acuant' as a key trigger term, which is specific to the integration. However, it lacks natural variations or related terms users might say (e.g., identity verification, document authentication, ID scanning) that would help Claude match user requests to this skill. | 2 / 3 |
Distinctiveness Conflict Risk | 'Acuant' as a proper noun provides some distinctiveness, but 'manage data, records, and automate workflows' is so generic it could overlap with dozens of other integration skills. Without specifying Acuant's domain (identity verification/document authentication), it's hard to distinguish from other data management skills. | 2 / 3 |
Total | 7 / 12 Passed |
Implementation
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 integration skill with excellent actionability and workflow clarity — every step has concrete CLI commands and state transitions are well-documented with error handling paths. The main weaknesses are unnecessary introductory context about Acuant that Claude already knows, and the cryptic 'Acuant Overview' section that lists entities without explanation or connection to the rest of the skill.
Suggestions
Remove the introductory paragraph explaining what Acuant is — Claude already knows this. Start directly with the working instructions.
Either explain the 'Acuant Overview' section (Credential, Face, Backside, Result, Settings, Log) with actionable context or remove it, as it currently adds no value.
Trim filler phrases like 'so you can focus on the integration logic rather than auth plumbing' and 'This will burn less tokens and make communication more secure' to improve token efficiency.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The opening paragraph explaining what Acuant is (identity verification platform, industries, etc.) is unnecessary context Claude already knows. The Membrane CLI workflow sections are mostly efficient but include some redundant explanations like 'Membrane handles authentication and credentials refresh automatically — so you can focus on the integration logic rather than auth plumbing.' | 2 / 3 |
Actionability | The skill provides concrete, copy-paste-ready CLI commands for every step: installation, authentication, connection management, action discovery, action creation, and action execution. Input parameters and flags are clearly specified with examples. | 3 / 3 |
Workflow Clarity | Multi-step processes are clearly sequenced with explicit state-checking and polling loops. The connection flow handles BUILDING, READY, CLIENT_ACTION_REQUIRED, and error states with clear next steps for each. The action creation flow similarly includes validation via polling until ready. | 3 / 3 |
Progressive Disclosure | The content is reasonably structured with clear sections, but the 'Acuant Overview' section listing Credential/Face/Backside/Result/Settings/Log is cryptic and unexplained. The document is somewhat long and could benefit from splitting detailed reference material (like state handling) into separate files. | 2 / 3 |
Total | 10 / 12 Passed |
Validation
90%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
- Commit
88db8c5
- 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.