acquire
Acquire integration. Manage data, records, and automate workflows. Use when the user wants to interact with Acquire data.
36
33%
Does it follow best practices?
Impact
—
No eval scenarios have been run
Advisory
Suggest reviewing before use
Optimize this skill with Tessl
npx tessl skill review --optimize ./skills/acquire/SKILL.mdQuality
Discovery
17%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 a generic template that could apply to almost any integration skill. It lacks specific actions, meaningful trigger terms, and concrete use cases that would help Claude distinguish this skill from other data/workflow/integration skills. The 'Use when' clause is circular and provides no real guidance.
Suggestions
List specific concrete actions the Acquire integration supports, e.g., 'Create and update customer records, track conversations, manage agent assignments, pull interaction history from Acquire.'
Add natural trigger terms users would actually say, such as 'live chat', 'customer support platform', 'Acquire CRM', 'chat widget', or whatever Acquire's domain-specific features are.
Expand the 'Use when' clause with specific scenarios, e.g., 'Use when the user mentions Acquire, live chat management, customer support tickets, or wants to pull conversation data from their Acquire account.'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description uses vague language like 'manage data, records, and automate workflows' without specifying any concrete actions. There are no specific capabilities listed—what kind of data? What workflows? 'Manage' and 'interact with' are abstract verbs. | 1 / 3 |
Completeness | It has a weak 'what' (manage data, records, automate workflows) and a 'when' clause ('Use when the user wants to interact with Acquire data'), but the 'when' is essentially circular—it just restates the skill name rather than providing meaningful trigger guidance. | 2 / 3 |
Trigger Term Quality | The only meaningful trigger term is 'Acquire' which is a proper noun for the integration. Generic terms like 'data', 'records', and 'workflows' are overly broad and would conflict with many other skills. No natural user language or specific Acquire-related terms are included. | 1 / 3 |
Distinctiveness Conflict Risk | Terms like 'manage data', 'records', and 'automate workflows' are extremely generic and would overlap with dozens of other integration or data management skills. Only 'Acquire' provides any distinctiveness, but the rest of the description creates high conflict risk. | 1 / 3 |
Total | 5 / 12 Passed |
Implementation
50%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
The skill provides actionable, executable CLI commands for interacting with Acquire via Membrane, which is its primary strength. However, it suffers from significant verbosity — the introductory explanation of Acquire, generic Membrane boilerplate (shared across many integration skills), and the sparse 'Acquire Overview' section waste tokens. The workflow is reasonably clear but lacks explicit validation steps after running actions.
Suggestions
Remove the introductory paragraph explaining what Acquire is — Claude already knows this, and the skill description covers it.
Trim or remove the generic Membrane CLI installation and authentication boilerplate, or reference a shared Membrane setup guide instead of repeating it inline.
Add descriptions to the popular actions table — the empty Description column wastes space without providing value.
Add a validation/verification step after running actions (e.g., checking the output field for errors) to improve workflow clarity.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The opening paragraph explains what Acquire is and who uses it — information Claude already knows or can infer. The Membrane CLI setup, authentication flow, and connection management sections are largely boilerplate shared across many integration skills, adding significant token overhead. The 'Acquire Overview' section with its sparse bullet list adds almost no value. | 1 / 3 |
Actionability | The skill provides fully executable CLI commands for every step: installing the CLI, authenticating, creating connections, searching for actions, running actions, and making proxy requests. Commands are copy-paste ready with clear flag descriptions and JSON parameter examples. | 3 / 3 |
Workflow Clarity | The connection setup workflow has a clear sequence with state-based branching (READY, CLIENT_ACTION_REQUIRED, CONFIGURATION_ERROR), but there are no explicit validation checkpoints or feedback loops for action execution. The overall flow from install → auth → connect → discover → run is implicit rather than explicitly sequenced. | 2 / 3 |
Progressive Disclosure | The content is a single monolithic file with no references to supporting files. The popular actions table, proxy request details, and connection state handling could be split into separate reference files. However, for a skill of this size (~150 lines), the inline approach is borderline acceptable, though the structure could be tighter. | 2 / 3 |
Total | 8 / 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
f484c82
- 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.