acquia
Acquia integration. Manage data, records, and automate workflows. Use when the user wants to interact with Acquia data.
Install with Tessl CLI
npx tessl i github:membranedev/application-skills --skill acquia72
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 correctly follows the structure with a 'Use when' clause and uses third person voice, but lacks specificity in describing Acquia's actual capabilities. The generic terms 'data, records, and workflows' don't help Claude understand what makes this skill unique compared to other data management integrations.
Suggestions
Add specific Acquia capabilities like 'manage Drupal sites, deploy code, access Site Factory environments, monitor cloud infrastructure'
Include more trigger terms users might say: 'Drupal hosting', 'Acquia Cloud', 'Site Factory', 'content staging', 'Acquia DAM'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (Acquia) and mentions some actions ('Manage data, records, and automate workflows'), but these are generic and not comprehensive - doesn't specify what kind of data, records, or workflows. | 2 / 3 |
Completeness | Has both 'what' (manage data, records, automate workflows) and explicit 'when' clause ('Use when the user wants to interact with Acquia data'), though both parts are somewhat generic. | 3 / 3 |
Trigger Term Quality | Includes 'Acquia' as a key trigger term which users would say, but lacks common variations or related terms (e.g., Drupal hosting, cloud platform, content management, specific Acquia products like Site Factory, Cloud Platform). | 2 / 3 |
Distinctiveness Conflict Risk | 'Acquia' is a specific platform which helps distinctiveness, but 'manage data, records, and automate workflows' is generic enough to potentially overlap with other CRM or data management skills. | 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 Acquia integration via Membrane, with good coverage of common operations. However, it wastes tokens explaining what Acquia is, lacks error handling/validation guidance, and the 'Acquia Overview' hierarchy is unexplained and unhelpful.
Suggestions
Remove the opening paragraph explaining what Acquia is - Claude already knows this context
Either explain the Acquia Overview hierarchy diagram (Sites > Environments > Applications etc.) or remove it entirely
Add validation steps: how to verify a connection succeeded, what errors look like, and recovery steps for common failures
Add example output snippets showing what successful command responses look like
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The opening paragraph explains what Acquia is, which Claude likely already knows. The Membrane CLI setup instructions are necessary but could be tighter. Some sections like 'Best practices' add value without bloat. | 2 / 3 |
Actionability | Provides fully executable CLI commands throughout - installation, login, connection creation, action discovery, and proxy requests are all copy-paste ready with concrete examples and flag documentation. | 3 / 3 |
Workflow Clarity | Steps are listed for setup and connection flows, but validation checkpoints are missing. No guidance on what to do if commands fail or how to verify successful connection beyond noting the connection ID. | 2 / 3 |
Progressive Disclosure | Content is reasonably organized with clear sections, but everything is inline in one file. The Acquia Overview hierarchy diagram is cryptic without explanation. No references to external detailed docs 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.