Cloud Platform AI skills act as an interface between your intent and Acquia developer tools. After you provide a natural language command, the AI agent uses these skills to identify the correct Command Line Interface (CLI) command, parameter, or Application Programming Interface (API) call that must execute the task.
Skills function as guidance artifacts rather than enforcement tools. They bundle Acquia operational best practices and procedural safety policies into machine-readable instructions. While skills provide the logic for a task, they rely on your existing infrastructure permissions. An agent cannot execute a skill-based action unless the authenticated user already possesses the underlying credentials, such as Secure Shell (SSH) keys or API tokens, for that specific environment.
Manage environments and applications.
Deploy code and synchronize databases.
Trigger builds and stream logs to diagnose failures.
Manage Drupal dependencies and security updates.
Manage Integrated Development Environment (IDE) and developer workflows.
To use skills:
Run the following command in the command line tool:
npx skills add acquia/acquia-skillsTo ensure environment stability, skills include built-in safety gates for destructive or irreversible operations.
Confirmation Prompts: For actions such as database trims, environment wipes, or production deployments, the Skill instructs the agent to pause and request explicit user approval.
Context Awareness: Skills evaluate the environment impact, such as the difference between a Dev and Prod environment, before they propose an action.
Cloud Platform AI skills adhere to emerging industry standards for agentic discovery:
llms.txt: Provides a concise index of available tools for Large Language Model (LLM) consumption.
AGENTS.md: Defines the behavior, constraints, and instructions for AI agents that interact with Acquia ecosystem.
Versioning: Skill logic versions align with major releases of Acquia CLI and Pipelines CLI to ensure command compatibility.
Use natural language to trigger complex workflows:
Deploy the feature-login branch to the staging environment.
Create a new Drupal 10 module skeleton named Event Tracker.
Diagnose why the last pipeline build failed and fix the PHP linting error.
Display all applications currently connected to your GitHub organization.
If this content did not answer your questions, try searching or contacting our support team for further assistance.
If this content did not answer your questions, try searching or contacting our support team for further assistance.