菜单
Comprehensive knowledge about Octopus Deploy, including core concepts, deployment processes, variables, releases, lifecycles, tenants, runbooks, AI-powered features, and best practices. Trigger when user mentions Octopus Deploy or general software deployment concepts.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Instructions on how to diagnose deployment or runbook failures using Octopus MCP or API. Use this skill when a user asks to analyze a deployment failure, failed task or a live production issue related to an Octopus Deploy project.
Use this skill when a user asks to produce audit reports or compliance evidence from Octopus Deploy event data through the Octopus MCP server. It covers questions about who deployed, who edited which variables, when a release shipped, why a permission changed, and what activity happened in a Space over a given window. Trigger on phrasing such as audit report, audit trail, change log, who changed what, who deployed, compliance evidence, SOC 2, GDPR, HIPAA, security investigation, access review, user activity, or runbook history.
Guides a user through their first Octopus Deploy setup — connecting a code repository, registering a deployment target (Kubernetes, Azure App Service, AWS ECS, Lambda, on-prem Tentacle, etc.), wiring up packages from their existing CI, and reaching their first real deployment. Prefers the Octopus MCP server's tools and resources when connected, and falls back to direct Octopus REST API calls when not. Trigger on "set up Octopus", "deploy my service", "connect my repo to Octopus", "first Octopus deployment", "Octopus project setup", "onboard to Octopus", "configure Octopus deployments", or any conversation where a user has Octopus credentials in hand and wants to stand up a working deployment from scratch — even if they don't use those exact phrases.
Authoritative guide to writing OCL (Octopus Configuration Language) for Octopus Deploy Config-as-Code projects. Use when authoring or editing any .ocl file under .octopus/ — deployment processes, runbooks, variables, deployment settings, schema_version, or process templates. Covers full OCL syntax (HCL-like), the property key namespace for every action_type, slug rules for entity references (accounts, feeds, environments, worker pools, channels, tenant tags, teams), and the canonical file layout. Trigger on "OCL", "octopus configuration language", ".ocl", "deployment_process.ocl", "runbook.ocl", "variables.ocl", "config-as-code", "CaC", or any request to author Octopus deployment processes/runbooks declaratively.
| name | octopus-deploy-knowledge |
| description | Comprehensive knowledge about Octopus Deploy, including core concepts, deployment processes, variables, releases, lifecycles, tenants, runbooks, AI-powered features, and best practices. Trigger when user mentions Octopus Deploy or general software deployment concepts. |
This skill provides comprehensive knowledge about Octopus Deploy, a deployment automation platform that enables continuous delivery for complex application deployments. Use this knowledge when helping users understand Octopus Deploy concepts, troubleshoot deployments, or design deployment pipelines.
Octopus Deploy is a deployment automation server that takes packages and artifacts from build servers and deploys them to various targets (Windows, Linux, Azure, AWS, Kubernetes, and more) using safe, consistent, and repeatable processes. It sits between your CI/CD build server and your deployment targets, providing:
Package Repository → Project → Release → Deployment → Environment → Deployment Targets
↓
Deployment Process
(Steps with Variables)
The central orchestration hub responsible for:
Deployment Options:
Spaces partition an Octopus Server for multi-team isolation. Each space has completely separate:
Key Point: Resources in Space-A are NOT accessible to projects in Space-B. Use the Default Space if you don't need isolation.
A Project is the primary container for deploying an application, service, or database. Each project contains:
Project Groups: Organize related projects together (e.g., "Online Store" containing Website, API, Database projects).
Environments represent stages in your deployment pipeline where software is deployed:
Key Points:
Physical or virtual destinations where software is deployed:
Target Types:
Target Tags (Roles): Logical groupings like "web-server", "database-server" used to target steps at specific machines.
Machines that execute deployment work that doesn't run on deployment targets:
Worker Types:
The recipe for deploying software, consisting of Steps that contain Actions:
Step Types:
Execution:
Store configuration that varies between environments, targets, or tenants:
Variable Types:
Scoping: Variables can be scoped to:
Variable Sets: Shared variable collections reusable across multiple projects.
System Variables: Built-in variables like Octopus.Environment.Name, Octopus.Release.Number, Octopus.Machine.Name.
A Release is a snapshot of:
Key Points:
Control how releases progress through environments:
Phases: Ordered stages containing one or more environments
Progression Rules:
Common Lifecycles:
Allow different release strategies within a single project:
Use Cases:
Deploy to multiple customers, regions, or instances without duplicating projects:
Tenant Features:
Use Cases:
Automate operations tasks that aren't deployments:
Characteristics:
Use Cases:
Packages: Archives containing application files
Feeds: Package repositories
Deploy to servers one-by-one instead of all at once:
Maintain two production environments (blue and green):
Release to a small subset of targets/users first:
Deploy to multiple geographic regions:
Store project configuration in Git repositories:
Benefits:
Octopus Deploy integrates AI to enhance continuous delivery workflows:
Intelligent companion integrated into the Octopus interface:
Model Context Protocol server for AI assistant integration:
AI-powered rapid recovery from deployment failures:
Security: Customer data never used to train models. Sensitive variables never exposed to AI. All interactions auditable.
Octopus is API-first - everything in the UI is available via API:
/api/{spaceId}/projectsOctopus CLI: Command-line interface for common operations
Octopus uses #{VariableName} syntax for variable substitution in steps and templates:
Basic: #{MyVariable} Nested: #{Outer#{Inner}} Escaped(literal) : ##{NotReplaced} renders as #{NotReplaced}
Conditionals: #{if Octopus.Environment.Name == "Production"}production config#{/if} #{if EnableFeature}enabled#{else}disabled#{/if} #{unless IsDisabled}active#{/unless}
Falsy values: undefined, empty string, "False", "No", "0"
Iteration(comma-separated or indexed variables) : #{each server in Servers} - #{server} #{/each} Loop variables: Octopus.Template.Each.Index, .First, .Last
Filters: #{Octopus.Environment.Name | ToLower} Available: ToLower, ToUpper, ToBase64, FromBase64, HtmlEscape, XmlEscape, JsonEscape, Markdown, Trim, Truncate, Replace
Index lookup: #{MyPassword[#{UserName}]} Calculations: #{calc Value1 + Value2}
Scripts can set output variables that subsequent steps can read.
Reading output from a previous step uses the pattern: Octopus.Action[StepName].Output.VariableName
In variable binding/substitution: #{Octopus.Action[StepA].Output.TestResult}
When directing user to navigate Octopus Deploy UI, refer to the following locations accurately:
Tenants Tenant Tag Sets Variable Sets Overview Deployment Targets Environments Machine Policies Machine Proxies Workers Worker Pools Accounts Build Information Certificates External Feeds Git Credentials Lifecycles Packages Script Modules Step Templates Dashboard Process Channels Releases Feature Toggles Triggers Freezes Settings Operations Runbooks Runbook Triggers Ephemeral Environments Project Variables Tenant Variables Variable Sets All Variables Variable Preview Tenants Tasks Insights Project Settings Version ControlWhen directing users to UI locations, you MUST follow these formatting rules:
Use the actual project name from context: The <SpecificProject name="{ReplaceWithProjectName}"> placeholder means you should use the ACTUAL project name provided in the OctopusContext. Never say "ReplaceWithProjectName" or "In" - use the real project name.
Format navigation paths with arrows: Use the format "ItemName -> SubItem -> Action"
Examples of CORRECT navigation instructions:
Examples of INCORRECT navigation instructions:
When to bold entity names: Bold the project name, step names, and other specific entity names in your instructions for clarity. Example: "Edit step Run a Script in MyProject -> Process"
For detailed information on specific topics, refer to these companion files: