agentleFS
acquiaacquia/acquia-skills-private/skills/pipelines-cli/getting-started/SKILL.md

getting-started

Skill1 starsChanged 7 months agoMITView on GitHub

Use when pipelines CLI is not installed, authentication fails, or user needs to set up pipelines-cli for the first time.

35 other projects use a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

6 rules. 0 are common, 5 are distinctive, and 1 is very specific to this project.

  • 0

    Common

    Most of the 33 edited versions we read keep these.

  • 5

    Distinctive

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Use pipelines-cli for pipeline jobs.

    line 31
  2. Distinctive:

    Only needed if you are not using the default Acquia Cloud endpoint:

    line 80
  3. Distinctive:

    If your credentials change or you need to reconfigure:

    line 88
  4. Distinctive:

    After configuring, confirm your environment is set up correctly:

    line 100
  5. Distinctive:

    Run this periodically to get bug fixes and new features.

    line 158
  6. Very specific:

    When using --no-interaction, you must pass both --key and --secret:

    line 199

“Common” is measured: kept by at least 6 in 10 of the 33 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Getting Started with Acquia Pipelines CLI

Use when:

  • Installing the Pipelines CLI for the first time
  • Configuring API credentials
  • Verifying your connection to Acquia Cloud
  • Updating the CLI to the latest version

Tool Overview

Two separate CLIs exist for Acquia Cloud operations:

ToolPurpose
pipelines-cliCI/CD pipeline operations: trigger builds, check job status, stream logs
acliGeneral Cloud management: applications, environments, IDEs, SSH keys, code/DB sync

Use pipelines-cli for pipeline jobs. Use acli for everything else.


Installation

Download the binary

wget https://cloud.acquia.com/pipelines-client/download -O pipelines
chmod +x pipelines
sudo mv pipelines /usr/local/bin

Verify installation

pipelines --version
pipelines help

Authentication

Configure credentials interactively

pipelines configure

You will be prompted for your Acquia Cloud API key and API secret:

Please enter your Acquia Cloud API key: <your-key>
Please enter your Acquia Cloud API secret: <hidden>
Configuration successful.

Configure credentials non-interactively

Useful for CI/CD environments where interactive prompts are not available:

pipelines configure --key=YOUR_KEY --secret=YOUR_SECRET

Configure with a custom endpoint

Only needed if you are not using the default Acquia Cloud endpoint:

pipelines configure --key=YOUR_KEY --secret=YOUR_SECRET --endpoint=https://your-custom-endpoint.com

Reset credentials

If your credentials change or you need to reconfigure:

pipelines reset-credentials

Then run pipelines configure again.


Verify Your Connection

After configuring, confirm your environment is set up correctly:

pipelines show-connection <application_id>

Output confirms whether the connection and application access are working.

To find your application ID first:

pipelines list-applications

Common First Steps

Step 1: Install

wget https://cloud.acquia.com/pipelines-client/download -O pipelines
chmod +x pipelines
sudo mv pipelines /usr/local/bin

Step 2: Configure credentials

pipelines configure

Step 3: Find your application

pipelines list-applications

Step 4: Verify connection

pipelines show-connection <application_id>

Step 5: Start your first pipeline

pipelines start --application-id=<application_id>

Keeping the CLI Updated

pipelines self-update

Run this periodically to get bug fixes and new features.


Getting Help

# List all available commands
pipelines

# Help for a specific command
pipelines help start
pipelines help configure

# Version (include in bug reports)
pipelines --version

Troubleshooting

"command not found: pipelines"

The binary is not in your PATH. Ensure you moved it to /usr/local/bin or another directory on your PATH:

which pipelines
export PATH="/usr/local/bin:$PATH"

"Configuration failed. Please check your credentials and try again."

Your API key or secret is incorrect. Verify them in the Acquia Cloud UI under API Keys, then re-run:

pipelines configure

"Non-interactive mode can only be used when key and secret are provided as cli options."

When using --no-interaction, you must pass both --key and --secret:

pipelines configure --no-interaction --key=YOUR_KEY --secret=YOUR_SECRET

Next Steps

  • Manage applications — Find application IDs, link repos
  • Run pipeline jobs — Start, monitor, and manage builds

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.