acquire
Acquire integration. Manage data, records, and automate workflows. Use when the user wants to interact with Acquire data.
Install with Tessl CLI
npx tessl i github:membranedev/application-skills --skill acquire72
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
67%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 follows the correct structure with a 'Use when...' clause and uses third person voice appropriately. However, it lacks specificity in describing what concrete actions the skill can perform with Acquire, and the trigger terms are too generic beyond the product name itself. The description would benefit from listing specific Acquire operations and more natural user language.
Suggestions
Add specific concrete actions the skill can perform (e.g., 'Create contacts, sync customer records, trigger automation sequences, query deal pipelines').
Expand trigger terms with natural variations users might say (e.g., 'Acquire CRM, customer data sync, Acquire API, lead management').
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (Acquire integration) and mentions general actions ('Manage data, records, and automate workflows'), but these are not concrete specific actions - they're broad categories without detail on what specific operations are supported. | 2 / 3 |
Completeness | Has both 'what' (manage data, records, automate workflows) and 'when' (explicit 'Use when the user wants to interact with Acquire data'), though both parts are somewhat generic. | 3 / 3 |
Trigger Term Quality | Includes 'Acquire' as the key trigger term and mentions 'data', 'records', 'workflows', but lacks variations or specific feature names users might naturally say when working with Acquire (e.g., specific Acquire features, API operations, or common use cases). | 2 / 3 |
Distinctiveness Conflict Risk | 'Acquire' as a product name provides some distinctiveness, but 'manage data, records, and automate workflows' is generic enough to potentially conflict with other integration or data management skills. The term 'Acquire' itself could be ambiguous without more context. | 2 / 3 |
Total | 9 / 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 Acquire integration via Membrane, with good coverage of common operations. However, it wastes tokens on introductory context Claude doesn't need, lacks validation/error handling in workflows, and could benefit from better progressive disclosure by splitting the actions reference into a separate file.
Suggestions
Remove the introductory paragraph explaining what Acquire is - Claude already knows this context
Add error handling guidance: what to do if `membrane login` fails, if connection creation times out, or if actions return errors
Clarify or remove the cryptic 'Acquire Overview' bullet list (Company > Document > Version, User) - it's unclear what this represents
Move the 'Popular actions' table to a separate ACTIONS.md reference file to reduce main skill length
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill includes some unnecessary explanation (e.g., describing what Acquire is and who uses it - Claude knows this). The overview section with bullet points is cryptic and adds little value. However, the CLI commands and tables are reasonably efficient. | 2 / 3 |
Actionability | Provides fully executable CLI commands with clear syntax, including authentication, connection setup, action discovery, and proxy requests. The flag table and examples are copy-paste ready. | 3 / 3 |
Workflow Clarity | Steps for setup and connection are sequenced, but there are no validation checkpoints or error recovery guidance. The workflow assumes success at each step without explaining what to do if commands fail or connections don't work. | 2 / 3 |
Progressive Disclosure | Content is reasonably organized with clear sections, but everything is inline in one file. The popular actions table could be a separate reference file, and there are no links to additional documentation or examples for complex use cases. | 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.