acquia
Acquia integration. Manage data, records, and automate workflows. Use when the user wants to interact with Acquia data.
49
53%
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/acquia/SKILL.mdQuality
Discovery
57%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 includes an explicit 'Use when' clause and names the specific platform (Acquia), which helps with completeness and some distinctiveness. However, the capabilities listed are extremely vague — 'manage data, records, and automate workflows' could describe dozens of different integrations. The description would benefit greatly from specifying what Acquia-specific actions are supported and including more natural trigger terms related to the Acquia ecosystem.
Suggestions
Replace vague terms like 'manage data, records, and automate workflows' with specific Acquia actions (e.g., 'deploy code to Acquia environments, manage Drupal sites, configure Cloud Platform settings, pull database backups').
Add Acquia-specific trigger terms users would naturally say, such as 'Drupal hosting', 'Acquia Cloud', 'site factory', 'Acquia environments', or 'Acquia CLI'.
Expand the 'Use when' clause with more specific trigger scenarios, e.g., 'Use when the user mentions Acquia Cloud, Acquia environments, Drupal deployments, or Acquia-hosted sites'.
| 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 kind of data, what records, or what workflows — these are generic terms that could apply to almost any integration. | 1 / 3 |
Completeness | It does answer both 'what' (manage data, records, automate workflows) and 'when' (Use when the user wants to interact with Acquia data), with an explicit 'Use when' clause. However, both parts are quite thin in detail. | 3 / 3 |
Trigger Term Quality | It includes 'Acquia' as a key trigger term which is specific to the platform, but lacks natural variations or specific Acquia-related terms users might say (e.g., Drupal, content management, hosting, environments, Cloud IDE, site factory). | 2 / 3 |
Distinctiveness Conflict Risk | 'Manage data, records, and automate workflows' is extremely generic and could overlap with many CRM, database, or integration skills. The mention of 'Acquia' provides some distinctiveness, but the rest of the description is not specific enough to clearly differentiate it. | 2 / 3 |
Total | 8 / 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 strong actionability with concrete, executable CLI commands for every operation, but suffers from verbosity — explaining what Acquia is, detailing connection states exhaustively, and including information Claude already knows. The workflow is reasonably clear but lacks explicit validation checkpoints, and the monolithic structure would benefit from splitting detailed reference material into separate files.
Suggestions
Remove the introductory paragraph explaining what Acquia is and who uses it — Claude already knows this. Start directly with the structural overview or working instructions.
Trim the connection state machine documentation to essential states (READY, CLIENT_ACTION_REQUIRED) with brief descriptions; move the full state reference to a separate REFERENCE.md file.
Add explicit validation steps after key operations (e.g., verify connection is READY before proceeding to action discovery, verify action output before reporting results).
Extract the proxy request options table and detailed clientAction type descriptions into a separate reference file to improve progressive disclosure.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The opening paragraph explains what Acquia is and who uses it — information Claude already knows. There's significant verbosity throughout: the authentication section explains headless environments in detail, the connection state machine is exhaustively documented with states Claude could infer, and the proxy request options table adds bulk. The 'Acquia Overview' hierarchy adds little value. | 1 / 3 |
Actionability | The skill provides fully executable, copy-paste-ready CLI commands for every step: installation, authentication, connection setup, action discovery, action execution, and proxy requests. Parameters and flags are clearly specified with concrete examples. | 3 / 3 |
Workflow Clarity | The connection workflow has a clear sequence (ensure → wait → check state → proceed) with state-based branching, but there are no explicit validation checkpoints or error recovery feedback loops. The overall flow from install → auth → connect → discover → run is implicit rather than explicitly sequenced with numbered steps and verification gates. | 2 / 3 |
Progressive Disclosure | The content is structured with headers and sections, but it's essentially a monolithic document with no references to external files. Content like the proxy request options table, the full connection state machine documentation, and the detailed clientAction type descriptions could be split into separate reference files. No bundle files are provided to support progressive disclosure. | 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.