all publishers

acquia

@acquia source repo

64 published skills

  1. ▌
    Pull Push 2 · acquia
    Use when syncing code, database, or files between local and Acquia Cloud environments, or pulling a Cloud database/files locally.
    18 repo stars
  2. ▌
    Scripting 2 · acquia
    Use when running acli commands non-interactively in scripts, CI/CD pipelines, or automation where interactive prompts must be suppressed.
    18 repo stars
  3. ▌
    Codestudio 2 · acquia
    Use when setting up a new Code Studio (GitLab CI/CD) project, changing PHP version in Code Studio builds. NOT for checking pipeline job status — use pipelines-cli-pipeline-operations for that.
    18 repo stars
  4. ▌
    Remote Access 2 · acquia
    Use when SSHing into a Cloud environment, running Drush commands remotely, or tailing live application logs.
    18 repo stars
  5. ▌
    Ide Management 2 · acquia
    Use when creating, listing, opening, deleting, or managing Cloud IDEs, or checking IDE hibernation status, changing PHP version in IDE, or sharing an IDE with teammates.
    18 repo stars
  6. ▌
    Getting Started 4 · acquia
    Use when acli is not installed, authentication fails, or user needs to install and authenticate acli for the first time.
    18 repo stars
  7. ▌
    Troubleshooting 2 · acquia
    Use when acli commands fail, return unexpected errors, authentication breaks, or the CLI behaves unexpectedly.
    18 repo stars
  8. ▌
    Ssh Key Management 2 · acquia
    Use when adding, listing, or deleting SSH keys for Acquia Cloud access, or when SSH access is denied due to missing keys.
    18 repo stars
  9. ▌
    Application Management 4 · acquia
    Use when listing Acquia Cloud applications, linking or unlinking a local repo to an application, opening an app in browser, checking VCS/branch deployment status, or exporting a site archive.
    18 repo stars
  10. ▌
    Environment Management 2 · acquia
    Use when listing, creating, deleting, or mirroring Cloud environments, managing CDEs, deploying code to an environment, or checking environment status.
    18 repo stars
  11. ▌
    Drupal Update Deploy 2 · acquia
    Use when user wants to update Drupal dependencies and deploy the changes to an Acquia environment, optionally triggering a pipeline build. Chains drupal-maintenance, acli, and pipelines-cli skills.
    18 repo stars
  12. ▌
    Security Updates 2 · acquia
    Use when user asks about fixing security vulnerabilities, composer audit failures, vulnerable Drupal packages, or CVE advisories in a Drupal codebase.
    18 repo stars
  13. ▌
    Dependency Updates 2 · acquia
    Use when user asks about updating outdated Drupal packages, upgrading Drupal core minor or patch versions, updating contrib modules, or resolving composer version conflicts.
    18 repo stars
  14. ▌
    Getting Started 3 · acquia
    Use when pipelines CLI is not installed, authentication fails, or user needs to set up pipelines-cli for the first time.
    18 repo stars
  15. ▌
    Pipeline Operations 2 · acquia
    Use when user asks about pipeline status, CI build status, triggering a build, streaming pipeline logs, terminating a job, or checking if a pipeline passed or failed. Use pipelines-cli, NOT acli.
    18 repo stars
  16. ▌
    Application Management 3 · acquia
    Use when finding a pipelines application ID or linking a repo before running any pipelines-cli command that needs --application-id.
    18 repo stars
  17. ▌
    Getting Started 2 · acquia
    Use when pipelines CLI is not installed, authentication fails, or user needs to set up pipelines-cli for the first time.
    18 repo stars
  18. ▌
    Application Management 2 · acquia
    Use when finding a pipelines application ID or linking a repo before running any pipelines-cli command that needs --application-id.
    18 repo stars
  19. ▌
    Pipeline Operations · acquia
    Use when user asks about pipeline status, CI build status, triggering a build, streaming pipeline logs, terminating a job, or checking if a pipeline passed or failed. Use pipelines-cli, NOT acli.
    18 repo stars
  20. ▌
    Meo Sites · acquia
    Use when listing, creating, updating, duplicating, recovering, or deleting MEO sites. Sites are the logical Drupal site definitions in a MEO multi-site subscription.
    18 repo stars
  21. ▌
    Pull Push · acquia
    Use when syncing code, database, or files between local and Acquia Cloud environments, or pulling a Cloud database/files locally.
    18 repo stars
  22. ▌
    Scripting · acquia
    Use when running acli commands non-interactively in scripts, CI/CD pipelines, or automation where interactive prompts must be suppressed.
    18 repo stars
  23. ▌
    Codestudio · acquia
    Use when setting up a new Code Studio (GitLab CI/CD) project, changing PHP version in Code Studio builds. NOT for checking pipeline job status — use pipelines-cli-pipeline-operations for that.
    18 repo stars
  24. ▌
    Meo Overview · acquia
    Use when determining whether to use ACE (V2) or MEO (V3) commands, or when starting work on a MEO multi-site subscription for the first time.
    18 repo stars
  25. ▌
    Meo Codebases · acquia
    Use when managing MEO codebases: listing, inspecting, updating, or deleting codebases, browsing git references, or managing domain patterns for a codebase.
    18 repo stars
  26. ▌
    Remote Access · acquia
    Use when SSHing into a Cloud environment, running Drush commands remotely, or tailing live application logs.
    18 repo stars
  27. ▌
    Ide Management · acquia
    Use when creating, listing, opening, deleting, or managing Cloud IDEs, or checking IDE hibernation status, changing PHP version in IDE, or sharing an IDE with teammates.
    18 repo stars
  28. ▌
    Getting Started · acquia
    Use when acli is not installed, authentication fails, or user needs to install and authenticate acli for the first time.
    18 repo stars
  29. ▌
    Meo Deployments · acquia
    Use when monitoring, stopping, or terminating MEO deployments. Deployments represent a code deploy operation running in a MEO environment.
    18 repo stars
  30. ▌
    Troubleshooting · acquia
    Use when acli commands fail, return unexpected errors, authentication breaks, or the CLI behaves unexpectedly.
    18 repo stars
  31. ▌
    Meo Cdn Security · acquia
    Use when managing MEO CDN domains, security rulesets, IP rules, custom security rules, rate limiting rules, failover groups, or purging CDN cache for a subscription or environment.
    18 repo stars
  32. ▌
    Meo Environments · acquia
    Use when managing MEO environments: inspecting environment details, enabling or disabling protection mode, clearing caches, managing deployments, site instances, egress IPs, private networks, trusted proxies, or domain patterns.
    18 repo stars
  33. ▌
    Meo Site Instances · acquia
    Use when managing MEO site instances: inspecting a site in a specific environment, managing domains, databases, backups, protection mode, or scheduling a site instance for deletion.
    18 repo stars
  34. ▌
    Ssh Key Management · acquia
    Use when adding, listing, or deleting SSH keys for Acquia Cloud access, or when SSH access is denied due to missing keys.
    18 repo stars
  35. ▌
    Meo Identity Access · acquia
    Use when managing MEO federated authentication: SSO domains, identity providers, and SSO policies. Enables customers to configure SAML-based single sign-on for their MEO subscription.
    18 repo stars
  36. ▌
    Application Management · acquia
    Use when listing Acquia Cloud applications, linking or unlinking a local repo to an application, opening an app in browser, checking VCS/branch deployment status, or exporting a site archive.
    18 repo stars
  37. ▌
    Environment Management · acquia
    Use when listing, creating, deleting, or mirroring Cloud environments, managing CDEs, deploying code to an environment, or checking environment status.
    18 repo stars
  38. ▌
    Drupal Update Deploy · acquia
    Use when user wants to update Drupal dependencies and deploy the changes to an Acquia environment, optionally triggering a pipeline build. Chains drupal-maintenance, acli, and pipelines-cli skills.
    18 repo stars
  39. ▌
    Security Updates · acquia
    Use when user asks about fixing security vulnerabilities, composer audit failures, vulnerable Drupal packages, or CVE advisories in a Drupal codebase.
    18 repo stars
  40. ▌
    Dependency Updates · acquia
    Use when user asks about updating outdated Drupal packages, upgrading Drupal core minor or patch versions, updating contrib modules, or resolving composer version conflicts.
    18 repo stars
  41. ▌
    Dogfood · acquia bundle
    Systematically explore and test a web application to find bugs, UX issues, and other problems. Use when asked to "dogfood", "QA", "exploratory test", "find issues", "bug hunt", "test this app/site/platform", or review the quality of a web application. Produces a structured report with full reproduction evidence -- step-by-step screenshots, repro videos, and detailed repro steps for every issue -- so findings can be handed directly to the responsible teams.
    18 repo stars
  42. ▌
    Agent Browser · acquia bundle
    Browser automation CLI for AI agents. Use when the user needs to interact with websites, including navigating pages, filling forms, clicking buttons, taking screenshots, extracting data, testing web apps, or automating any browser task. Triggers include requests to "open a website", "fill out a form", "click a button", "take a screenshot", "scrape data from a page", "test this web app", "login to a site", "automate browser actions", or any task requiring programmatic web interaction.
    18 repo stars
  43. ▌
    Canvas Regions · acquia
    Use for any task touching site chrome — header, footer, sidebar, or global navigation that repeats across pages — and for any region-spec work (create, modify, review, validate region JSON, or the project-level layout component). Also load when a task creates or edits multiple pages that share chrome, or asks for a "site" or "navigation between pages"; shared chrome belongs in regions, never inlined into page JSON.
    18 repo stars
  44. ▌
    Canvas Workbench · acquia bundle
    Use when work must be verified in local Canvas Workbench, or when the user asks to run, open, check, or author component mocks or page previews in Workbench. Verifies that Canvas Workbench is available through the project's package runner, starts the local Workbench dev server, and keeps Workbench verification as part of the implementation workflow.
    18 repo stars
  45. ▌
    Implement Design · acquia
    Translates Figma designs into production-ready code with 1:1 visual fidelity. Use when implementing UI from Figma files, when user mentions "implement design", "generate code", "implement component", "build Figma design", provides Figma URLs, or asks to build components matching Figma specs. Requires Figma MCP server connection.
    18 repo stars
  46. ▌
    Nebula Scrape Url · acquia
    Capture web page screenshots and HTML for design reference. Use when the user provides a URL and asks to build, recreate, or implement a design. Runs `scripts/scrape-page.js` to capture desktop/tablet/mobile screenshots and HTML. Not for Figma, GitHub, or documentation URLs.
    18 repo stars
  47. ▌
    Canvas Data Fetching · acquia
    Fetch and render Drupal content in Canvas components with JSON:API and SWR patterns. Use when building content lists, integrating with SWR, querying related entities, or constructing/changing any JSON:API request — every generated request must be executed and verified to return the expected results before rendering logic is written against it. Covers JsonApiClient, DrupalJsonApiParams, relationship handling, filter patterns, and request verification.
    18 repo stars
  48. ▌
    Canvas Component Push · acquia
    Push validated Canvas component changes to Drupal Canvas and recover from common push failures. Use only when the user explicitly requests a push/publish/sync action. Handles dependency-related push failures that require retry.
    18 repo stars
  49. ▌
    Canvas Component Utils · acquia
    Use utility components to render formatted text and media correctly. Use when (1) Rendering HTML text content from props, (2) Displaying images, (3) Working with formatted text or media. Covers FormattedText and Image utilities.
    18 repo stars
  50. ▌
    Canvas Page Definition · acquia
    Start here for any Canvas page-spec task. Use for create, modify, refactor, review, migrate, or validate work on page JSON files that sync with Canvas and render in Workbench. Establishes the canonical Canvas page-spec contract, including placement, structure, format constraints, and validation.
    18 repo stars
  51. ▌
    Nebula Workbench Pages · acquia
    Nebula-specific overlay for Canvas Workbench pages. Use when you need the repository-local rule that `examples/pages/` is reference-only and active Workbench pages belong in `pages/`.
    18 repo stars
  52. ▌
    Canvas Content Templates · acquia
    Create and modify content templates that map Drupal content entities to Canvas component layouts. Use when asked to (1) Create a new content template, (2) Modify an existing content template, (3) Add or change entity field mappings in a template, (4) Compose components in a content template via slots. Content templates live in the configured `contentTemplatesDir` (default `content-templates/`) and define how Drupal entity types, bundles, and view modes render as Canvas component trees.
    18 repo stars
  53. ▌
    Nebula Project Structure · acquia
    Project folder structure and package manager detection for Nebula. Reference when navigating the codebase, running commands, or determining which package manager to use (npm/yarn/pnpm/bun).
    18 repo stars
  54. ▌
    Canvas Component Metadata · acquia
    Define valid component.yml metadata for Canvas components, including props, slots, and enums. Use when (1) Creating a new component, (2) Adding or modifying props, (3) Troubleshooting "not a valid choice" or prop type errors, (4) Mapping enums to CVA variants.
    18 repo stars
  55. ▌
    Nebula Component Creation · acquia
    Create React components by copying and modifying examples from `examples/components/`. Use when asked to (1) Create, add, or build a new component, (2) Copy an example component to `src/components/`, (3) Add a component with dependencies. Handles dependency resolution and ensures each component has `index.jsx` and `component.yml`.
    18 repo stars
  56. ▌
    Nebula Node Page Scaffold · acquia
    Scaffolds Canvas UI for individual Drupal node pages (single-entity detail views) via components, component.yml, and one example pages/ spec—not list or index views. Does not wire those detail pages through remote APIs, Source MCP, or per-node page creation. Use for article/product/event detail templates, one-node screens, and “skip API/MCP page assembly for each node”; do not use this skill for blog grids, search results, or other list UIs.
    18 repo stars
  57. ▌
    Canvas Styling Conventions · acquia
    Style Canvas components with Tailwind CSS 4 theme tokens and approved utility patterns. Use when (1) Creating a new component, (2) Adding colors or styling to components, (3) Working with Tailwind theme tokens, (4) Adding or updating design tokens in global.css, (5) Creating color/style props, (6) Any change where component props are added/removed/renamed/retyped and can affect rendered styles. Covers @theme variables, CVA variants, and cn() utility.
    18 repo stars
  58. ▌
    Nebula Visual Verification · acquia bundle
    Focused visual QA for changed Canvas components and pages in local Canvas Workbench. Use only when the user explicitly asks for visual verification, visual QA, or Workbench rendering review of a changed component or page.
    18 repo stars
  59. ▌
    Canvas Component Definition · acquia bundle
    Start here for any React component task to enforce the canonical Canvas component contract. Use for create, modify, refactor, review, migrate, or validate work. Establishes the canonical Canvas component contract, assuming repository components are Canvas targets, and guides either (1) transforming existing components to meet Canvas requirements or (2) creating new Canvas-ready components.
    18 repo stars
  60. ▌
    Canvas Design Decomposition · acquia bundle
    Plans structure for a component library with props/slots and right-sized component granularity. Run before building or adding Canvas components (new `src/components/` folders, component.yml, React), or for plan-only / breakdown-only work, whenever UI must map to a coherent tree. Mandatory for every new Figma frame or greenfield screen—repository drafts do not replace phases A–G.
    18 repo stars
  61. ▌
    Nebula Component Validation · acquia
    Validate components after creating or modifying components, and after page work that changes rendered output, before considering work complete. Runs `npm run code:fix` for static validation.
    18 repo stars
  62. ▌
    Canvas Navigation Components · acquia bundle
    Plans and builds Drupal Canvas navigation UI (main nav, footer links, sidebar nav, mobile drawers, breadcrumbs) using design decomposition for structure and props/slots, then JSON:API menu or page-context patterns from canvas-data-fetching. Use when the user asks for navigation, header or footer links, menus, menu_items, mobile nav, or breadcrumb trails. Run after canvas-design-decomposition for layout and API sketches; follow canvas-data-fetching for SWR, JsonApiClient, sortMenu, and menu fallbacks.
    18 repo stars
  63. ▌
    Acquia Source Navigation Menus · acquia
    Acquia Source only. Create and edit Drupal menus in the CMS via Source MCP. Do not use for non-Source sites; production nav should still be authored in Drupal, not only in component code.
    18 repo stars
  64. ▌
    Canvas Component Composability · acquia bundle
    Design Canvas-ready React components with slots and decomposition-first patterns. Use when (1) Designing a component's prop/slot structure, (2) A component is growing too large, (3) Deciding between props vs slots, (4) Refactoring monolithic components, (5) Modeling repeatable list/grid content, (6) Reusing, composing, or wrapping existing workspace components. Ensures Canvas compatibility.
    18 repo stars