Octopus Deploy for Openclaw

Openclaw Skills for Octopus Deploy lets you safely inspect deployments, releases, environments, projects, spaces, and tasks through the oo CLI.

oomol
v1.0.1
Jul 30, 2026
0
262
0

Install & Download

1. ClawHub CLI

The fastest way to install a skill directly from the registry.

npx clawhub@latest install oo-octopus-deploy

2. Manual Installation

Copy the skill folder to one of these locations

Global
~/.openclaw/skills/
Workspace
<project>/skills/

Priority: Workspace > Local > Bundled

3. Prompt Installation

Copy this prompt to OpenClaw to install it automatically.

Help me install oo-octopus-deploy using Clawhub. If Clawhub is not installed, install it first (npm i -g clawhub).

Prefer to download?

Get the raw skill files in a ZIP archive.

What is Octopus Deploy?

Openclaw Skills for Octopus Deploy provides a secure, CLI-driven way to query Octopus Deploy through your OOMOL-connected account. Instead of calling the API directly or handling raw tokens, you use the oo CLI to inspect the live schema and run connector actions against the octopus_deploy service.

This skill is designed for reliable read operations across Octopus Deploy resources such as spaces, projects, releases, deployments, environments, and server tasks. Openclaw Skills emphasizes safe execution, schema-first payload construction, and credential handling managed server-side by OOMOL.

Octopus Deploy Use Cases

  • Look up the current connected Octopus Deploy user.
  • Fetch a specific deployment, release, project, environment, or task by ID.
  • List deployments, releases, projects, environments, spaces, or tasks with optional filters.
  • Verify deployment history or task status before troubleshooting.
  • Explore which spaces are visible to the connected API key.
  • Build automation or support workflows that need read-only Octopus Deploy data.
  • Validate the correct request shape before sending an action payload with Openclaw Skills.

How Octopus Deploy Works

  1. Inspect the live contract for the target action using oo connector schema "octopus_deploy" --action "<action_name>".
  2. Build a JSON payload that matches the returned schema, or omit the payload to send an empty object when supported.
  3. Run the action with oo connector run "octopus_deploy" --action "<action_name>" --data '<json>' --json.
  4. Read the response data and capture the execution ID from meta.executionId for traceability.
  5. If a command fails due to missing CLI, authentication, or connection issues, perform first-time setup only for the specific error condition.
  6. Treat untagged actions as read-only and confirm any future write or destructive actions with the user before execution.

Octopus Deploy Setup

  1. Install the oo CLI if it is not already available.
curl -fsSL https://cli.oomol.com/install.sh | bash
  1. On Windows PowerShell, use the platform-specific installer.
irm https://cli.oomol.com/install.ps1 | iex
  1. Sign in to your OOMOL account once if authentication is required.
oo auth login
  1. Connect Octopus Deploy in the OOMOL console if the connector is missing, expired, or lacks scope.
https://console.oomol.com/app-connections?provider=octopus_deploy
  1. Verify the exact input schema for the action before sending data.
oo connector schema "octopus_deploy" --action "list_projects"
  1. Run the action with a schema-aligned payload.
oo connector run "octopus_deploy" --action "list_projects" --data '{}' --json

Octopus Deploy Data Schema & Taxonomy

Openclaw Skills for Octopus Deploy organizes interactions around connector actions, each with its own live schema and JSON payload.

Core execution model

Element Purpose Notes
Connector octopus_deploy The service target used by the oo CLI
Schema lookup oo connector schema Authoritative source for input/output fields
Action execution oo connector run Executes a single Octopus Deploy action
Payload format JSON object Passed via --data or from a file path
Response format { "data": ..., "meta": { "executionId": "..." } } Execution ID is returned in meta.executionId

Resource taxonomy

  • Spaces: list_spaces
  • Projects: get_project, list_projects
  • Releases: get_release, list_releases
  • Deployments: get_deployment, list_deployments
  • Environments: get_environment, list_environments
  • Tasks: get_task, list_tasks
  • Identity: get_current_user

Action conventions

  • Untagged actions are read-only and safe to run directly.
  • Actions marked [write] modify Octopus Deploy state and require explicit confirmation.
  • Actions marked [destructive] may remove or overwrite data and require extra approval.
  • Always fetch the latest schema before constructing payloads, because field requirements are authoritative at runtime.

Metadata and safety signals

  • Execution tracking: meta.executionId
  • Credential handling: managed server-side by OOMOL, not exposed in the command payload
  • Fallback triggers: missing CLI, auth failure, expired connection, missing scope, billing issues

Octopus Deploy Advanced Features

  • Schema-first execution flow that reduces payload mismatches and runtime errors.
  • Server-side credential injection through OOMOL, so Openclaw Skills never requires raw token handling.
  • Safe read operations for discovery, audits, and support workflows.
  • Explicit safety model that separates read, write, and destructive actions.
  • Supports both inline JSON payloads and @path/to/file.json input for complex requests.
  • Returns an execution ID for traceability and debugging across runs.
  • Designed for agentic workflows that need reliable Octopus Deploy inspection without direct API integration.
  • One-time recovery paths for CLI installation, login, connection setup, and billing issues.

SKILL.md


Loading

Related Openclaw Skills

METADATA

Github Stars: 0
forks: 0

Featured*