acquire
Acquire integration. Manage data, records, and automate workflows. Use when the user wants to interact with Acquire data.
52
41%
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/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 extremely vague and provides almost no useful information for skill selection. It relies entirely on the product name 'Acquire' for distinctiveness without explaining what Acquire is, what specific operations are supported, or what natural language triggers should activate it. The 'Use when' clause is tautological and adds no real selection guidance.
Suggestions
Explain what 'Acquire' is (e.g., a CRM, customer support platform, etc.) and list specific concrete actions like 'create contacts, update deal records, trigger automated email sequences'.
Add meaningful trigger terms users would naturally say, such as specific entity names (contacts, leads, tickets), operations (sync, import, lookup), or domain context (customer support, sales pipeline).
Rewrite the 'Use when' clause with specific scenarios, e.g., 'Use when the user mentions Acquire CRM, needs to look up customer records, or wants to automate support ticket workflows.'
| 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 a tautology that restates the 'what' without adding meaningful trigger guidance. | 2 / 3 |
Trigger Term Quality | The only potentially useful trigger term is 'Acquire,' which is a proper noun but extremely generic as a word. There are no natural keywords a user would say beyond the product name itself—no mention of specific features, file types, or domain-specific terms. | 1 / 3 |
Distinctiveness Conflict Risk | 'Manage data, records, and automate workflows' is extremely generic and could overlap with dozens of other integration or data management skills. Only the word 'Acquire' provides any distinctiveness, but it's not well-contextualized. | 1 / 3 |
Total | 5 / 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.
The skill provides solid, actionable CLI commands for interacting with Acquire via Membrane, making it practically useful. However, it wastes tokens on explaining what Acquire is, includes a nearly empty 'Overview' section and an actions table with blank descriptions, and lacks explicit validation checkpoints in the main workflow. Tightening the content and adding verification steps would significantly improve quality.
Suggestions
Remove the introductory paragraph explaining what Acquire is — Claude already knows this, and the skill description covers it.
Either populate the Description column in the Popular Actions table or remove it; empty cells waste tokens and provide no guidance.
Add explicit validation/verification steps to the main workflow (e.g., verify connection succeeded before searching actions, confirm action run output before proceeding).
Flesh out or remove the 'Acquire Overview' bullet list (Company → Document → Version, User) — it's too cryptic to be useful in its current form.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The opening paragraph explaining what Acquire is (customer communication platform, used by sales/marketing/support teams, etc.) is unnecessary context Claude already knows. The Membrane CLI instructions are mostly efficient but the 'Acquire Overview' section with its sparse bullet list adds little value. Some tightening possible throughout. | 2 / 3 |
Actionability | Provides fully executable CLI commands for every step: installation, authentication, connecting, searching actions, creating actions, running actions with parameters. Commands are copy-paste ready with clear placeholder conventions. | 3 / 3 |
Workflow Clarity | The workflow follows a logical sequence (install → authenticate → connect → search → run), but there are no explicit validation checkpoints or error recovery loops for the main workflow. The action creation section does include polling and state checking, which is good, but the overall flow lacks numbered steps and verification points. | 2 / 3 |
Progressive Disclosure | Content is reasonably structured with clear headers, but the popular actions table with empty descriptions adds bulk without value. The 'Acquire Overview' section is cryptic and unhelpful. Links to official docs are provided but no references to supplementary 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 | |
- Repository
- membranedev/application-skills
- Commit
56d7336
- 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.