!

Legal Disclaimer

PipeAgent is a data distribution gateway. We do not own, verify, or endorse the data provided by third-party creators. Use at your own discretion.

Docs/consumer / integration openclaw cli

OpenClaw: command-line install

This page covers installing a per-feed OpenClaw skill from the terminal. For a conversational workflow (search → metadata → install inside OpenClaw), see PipeAgent Pilot (OpenClaw). For how this differs from Pilot, see the OpenClaw Integration overview.

One-line install

By default, install.sh writes to ~/.openclaw/workspace/skills/<feed-folder>/SKILL.md. That requires an OpenClaw workspace at ~/.openclaw/workspace (create it via OpenClaw setup first). Otherwise pass --dest with your workspace root, or the script exits with an error. install.sh does not need your Read API key for download — it only fetches SKILL.md. Use --alias with the same value as the feed detail page ALIAS (the feed endpoint_path). Do not pass both --id and --alias.

bash
curl -fsSL https://pipeagent.dev/install.sh | bash -s -- --alias "your-endpoint-path"

If you prefer the feed UUID:

bash
curl -fsSL https://pipeagent.dev/install.sh | bash -s -- --id "00000000-0000-0000-0000-000000000000"
✨
IMPORTANT

Newer install.sh versions can help configure runtime env for you:

- After install, it can prompt to write PROVIDER_READ_API_KEY into OpenClaw env (default: ~/.openclaw/.env).

- You can also pass --key, or --env-file <path>, or run non-interactive with --yes.

- Restart OpenClaw Gateway after env changes so the key is loaded.

>

OpenClaw env precedence and locations: OpenClaw environment variables.

Optional flags

  • --skillname <name> — overrides only the YAML name: inside SKILL.md (letters, digits, _, -). The install directory still defaults from ALIAS / endpoint_path.
  • --dest <dir> — OpenClaw workspace root; the skill is installed to <dir>/skills/<feed-folder>/SKILL.md. Default workspace root is ~/.openclaw/workspace (must already exist unless you pass --dest).
  • --site <origin> — Override where SKILL.md is fetched from (default https://api.pipeagent.dev). When you use curl https://pipeagent.dev/install.sh, you normally omit this flag. Use --site only if PipeAgent support gives you a different API/web origin. Optional env on bash: PIPEAGENT_SITE (same meaning as --site).
  • --env-file <path> — write PROVIDER_READ_API_KEY to a custom OpenClaw env file (default is ~/.openclaw/.env).
  • --key <read_key> — provide the read key directly (script can also prompt interactively).
  • --yes — auto-confirm interactive prompts (useful for automation).

    • PipeAgent also exposes the raw skill for scripting:

    GET https://api.pipeagent.dev/public/feeds/{uuid_or_endpoint_path}/openclaw-skill (same path on https://pipeagent.dev if you use the web origin) with optional query ?skill_name=. Responses include X-Feed-Endpoint-Path when known.

    curl \| bash runs remote code. To inspect first: curl -fsSL https://pipeagent.dev/install.sh -o install-pipeagent.sh && less install-pipeagent.sh then execute locally.

    Directory layout

    text
    ~/.openclaw/workspace/       <-- OpenClaw workspace (default install target)
└── skills/
    └── your-feed-alias/
        └── SKILL.md          <-- One-line install writes here by default
    text
    my-agent/                      <-- Or a custom project layout with --dest my-agent
└── skills/
    └── pipeagent-finance/
        └── SKILL.md

    Workbench

    On any feed detail page, open the OpenClaw tab in the Agent Workbench. You can copy the one-line install block, copy the SKILL.md body, or download it.

    1. Browse to a feed (e.g. from Feeds).

    2. Open the OpenClaw tab.

    3. Prefer One-line install (uses --alias when the feed has an ALIAS / endpoint_path).

    4. Or use Download / Copy and place SKILL.md under ~/.openclaw/workspace/skills/<folder>/ (or your --dest workspace’s skills/ folder).

    5. Ensure PROVIDER_READ_API_KEY is set in the OpenClaw runtime (where the agent runs), not for the install command — see OpenClaw environment variables.

    6. The same tab includes a second one-liner to install the pipeagent-pilot controller skill via install-pipeagent-pilot.sh.

    Recommended quick path (beginner-friendly)

    1. Run install:

    bash
    curl -fsSL https://pipeagent.dev/install.sh | bash -s -- --alias "your-endpoint-path"

    2. If prompted, paste your PROVIDER_READ_API_KEY so script writes it to ~/.openclaw/.env.

    3. Restart OpenClaw Gateway.

    4. In chat, ask your agent: Please refresh skills and confirm <alias> is available.

    PipeAgent Pilot (controller) one-liner

    Installs ~/.openclaw/workspace/skills/pipeagent-pilot/SKILL.md (no Read key). Same --dest / workspace rules as feed install.sh.

    bash
    curl -fsSL https://pipeagent.dev/install-pipeagent-pilot.sh | bash

    More options: PipeAgent Pilot.

    Related

  • OpenClaw overview (two ways to integrate)
  • PipeAgent Pilot (conversation)
    • Version 1.0.4 - Premium Infrastructure