acuant
Acuant integration. Manage data, records, and automate workflows. Use when the user wants to interact with Acuant data.
Install with Tessl CLI
npx tessl i github:membranedev/application-skills --skill acuant55
Does it follow best practices?
If you maintain this skill, you can automatically optimize it using the tessl CLI to improve its score:
npx tessl skill review --optimize ./path/to/skillValidation for skill structure
Discovery
25%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 too vague to be useful for skill selection. It fails to explain what Acuant actually does (identity verification/document authentication platform) and relies entirely on users already knowing the brand name. The generic phrases 'manage data' and 'automate workflows' provide no meaningful differentiation from dozens of other potential integration skills.
Suggestions
Specify what Acuant actually does - add concrete actions like 'Verify identity documents, authenticate IDs, perform KYC checks, scan driver's licenses and passports'
Add natural trigger terms users would say: 'identity verification', 'ID scanning', 'document authentication', 'KYC', 'identity check', 'verify ID'
Expand the 'Use when' clause with specific scenarios: 'Use when verifying customer identity, scanning ID documents, performing compliance checks, or authenticating credentials'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description uses vague language like 'Manage data, records, and automate workflows' without specifying concrete actions. It doesn't explain what Acuant is or what specific operations can be performed (e.g., identity verification, document scanning, credential management). | 1 / 3 |
Completeness | It has a basic 'what' (manage data, records, automate workflows) and includes a 'Use when' clause, but both are extremely vague. The 'when' only says 'interact with Acuant data' which doesn't provide meaningful trigger guidance. | 2 / 3 |
Trigger Term Quality | The only trigger term is 'Acuant' which is a proper noun/brand name. There are no natural keywords users might say like 'identity verification', 'ID scanning', 'document authentication', or 'KYC'. Users unfamiliar with Acuant wouldn't know to trigger this skill. | 1 / 3 |
Distinctiveness Conflict Risk | The Acuant brand name provides some distinctiveness, but 'manage data, records, and automate workflows' is generic enough to overlap with many integration or data management skills. Without specifying Acuant's domain (identity verification), it could conflict with other CRM or data management tools. | 2 / 3 |
Total | 6 / 12 Passed |
Implementation
64%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill provides solid, actionable CLI commands for Acuant integration via Membrane, with good coverage of authentication, connection management, and proxy requests. However, it wastes tokens on introductory content Claude doesn't need, includes a cryptic overview section, and lacks validation steps for confirming successful operations.
Suggestions
Remove the introductory paragraph explaining what Acuant is and the 'Acuant Overview' bullet list - Claude doesn't need this context
Add validation steps after key operations (e.g., 'Verify connection succeeded by running membrane connection list --json and confirming the new connectionId appears')
Include error handling guidance for common failure scenarios like authentication timeout or invalid credentials
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill includes some unnecessary explanation about what Acuant is (Claude knows this), and the overview section listing entities without context adds little value. However, the CLI commands and examples are reasonably efficient. | 2 / 3 |
Actionability | Provides fully executable CLI commands with clear syntax, including authentication flow, connection setup, action discovery, and proxy requests. Commands are copy-paste ready with proper flags documented. | 3 / 3 |
Workflow Clarity | Steps for setup and connection are sequenced but lack validation checkpoints. No guidance on verifying successful connection, handling failed authentication, or confirming action execution succeeded before proceeding. | 2 / 3 |
Progressive Disclosure | Content is reasonably organized with clear sections, but the 'Acuant Overview' section with bullet points serves no clear purpose and could be removed or linked to external docs. No references to additional files for advanced topics. | 2 / 3 |
Total | 9 / 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 | |
- 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.