Octo Deploy
Guide the promotion of an OctoMesh-powered app from local dev to the shared test-2 environment — publish the CK model and blueprint to the shared GitHub catalogs (octo-ckc / octo-bpm), push the app image to <registry>, register a test-2 octo-cli context, install + deploy on the target tenant, and verify everything WITHOUT kubectl access. Covers both the repeatable CI lane (azure-pipelines publishing on main) and the manual first-time lane, plus test-2-specific triage (server-side catalog cache refresh, ImagePullBackOff via lastDeploymentError, Tailscale reachability). Staging and production ar
Install
/plugin marketplace add meshmakers/octo-claude-skillsThe repo is a Claude Code plugin marketplace. Run /plugin afterwards to pick the plugin that includes this skill.
npx skills add meshmakers/octo-claude-skills --skill octo-deploygit clone --depth 1 https://github.com/meshmakers/octo-claude-skills.git /tmp/octo-claude-skills
mkdir -p ~/.claude/skills
cp -r /tmp/octo-claude-skills/skills/octo-deploy ~/.claude/skills/octo-deployPersonal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.
From the SKILL.md
# OctoMesh Deploy — local → test-2
> **Hostnames are placeholders.** The concrete domains of the shared environments (`<test-2-domain>`, `<staging-domain>`, `<prod-1-domain>`, `<prod-2-domain>`, `<legacy-domain>`, `<registry>`, `<rancher-url>`) are internal. If the plugin `octo-claude-pm` is installed, see its `agent-operating-rules/references/environments.md`; otherwise ask a colleague.
Promote an app built with `octo-app-builder` (CK model + blueprint + pipelines +
Application workload) from local dev to the shared **test-2** cluster.
**Staging and production are deliberately out of scope** — do not extrapolate
these instructions to them.
## Routing
| For... | Use |
|---|---|
| Building the app/blueprint artifacts in the first place | `Skill("octo-app-builder", ...)` |
| Individual octo-cli commands, status checks, tenant admin | `Skill("octo", ...)` |
| Operator/Helm internals (what the operator does with a workload) | `Skill("octo-operator", ...)` |
| Something broke and needs deep investigation | `Skill("octo-agent", ...)` |
## What actually has to move (and what doesn't)
A blueprint built per octo-app-builder is **environment-portable by design** —
the seed itself needs NO changes for the target cluster:
| Seed element | Why it ports |
|---|---|
| `${octo.tenantId}` in hostname/upstreamUrl | resolved at blueprint apply, per tenant |Details
- Skill name
octo-deploy- Repository
- meshmakers/octo-claude-skills
- Path
skills/octo-deploy/SKILL.md- Repo updated
- 17 November 2026
FAQ
What does the Octo Deploy skill do?
Guide the promotion of an OctoMesh-powered app from local dev to the shared test-2 environment — publish the CK model and blueprint to the shared GitHub catalogs (octo-ckc / octo-bpm), push the app image to <registry>, register a test-2 octo-cli context, install + deploy on the target tenant, and verify everything WITHOUT kubectl access. Covers both the repeatable CI lane (azure-pipelines publishing on main) and the manual first-time lane, plus test-2-specific triage (server-side catalog cache refresh, ImagePullBackOff via lastDeploymentError, Tailscale reachability). Staging and production ar
How do I install the Octo Deploy skill?
Claude Code plugin: /plugin marketplace add meshmakers/octo-claude-skills. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.
Is Octo Deploy popular?
It lives in meshmakers/octo-claude-skills, which has 10 GitHub stars and 0 forks.
Related skills
Octo
10meshmakers/octo-claude-skills
Primary entry point and router for ALL OctoMesh tasks. Drives the octo-cli for platform administration (users, roles, groups, tenants, clients, identity providers, blueprints, CK catalog/library management, stream-data archives, communication adapters/pipelines, AI services) and explores the data model and runtime instances via GraphQL. Routes specialized work to sibling skills. When unsure which OctoMesh skill to use, start here. Trigger on: OctoMesh, octo-cli, CLI command, environment switch, auth/login, AuthStatus, tenant, temporary tenant, test tenant, user, role, group, client credentials
Octo Agent
10meshmakers/octo-claude-skills
Debugging and investigation agent for OctoMesh — diagnoses CK model failures (ResolveFailed, modelState 2, broken dependencies, version-bump cascades), blueprint install failures, and CK migration problems; inspects MongoDB tenant databases directly; runs selective DebugL builds and targeted tests to isolate a regression; and manages Docker volume backups for safe rollback. Use it when something broke after a build, version bump, merge, or upgrade and you need to find the root cause safely. Trigger on: help me fix, investigate this bug, what broke, isolate the issue, why is the model broken, R
Octo App Builder
10meshmakers/octo-claude-skills
Build a complete OctoMesh-powered application end to end — a custom Construction Kit data model published to the CK catalog, an HTTP API made of dataflow pipelines on the tenant's Mesh Adapter, an optional containerized web app the Communication Operator rolls out to Kubernetes, and a blueprint that packages all of it so a single InstallBlueprint provisions any tenant. Encodes the verified build sequence (model → pipelines → app image → blueprint → install → deploy → verify) and the pitfalls that silently break it (blueprint catalog cache, pipeline registration rotation, HTTP response shaping,
Octo Devtools
10meshmakers/octo-claude-skills
Drives OctoMesh local development through the octo-tools PowerShell cmdlets — building repos in dependency order, starting and stopping services (always non-interactively for agents via Start-Octo -nonInteractive $true / Stop-Octo), managing Docker or local kind Kubernetes infrastructure, syncing and branching git repos, NuGet package propagation, certificates, and octo-cli context/auth setup. Use it for any OctoMesh dev-environment or DevOps task. Trigger on build, compile, feature environment, New-OctoEnvironment, Invoke-BuildEnvironment, lane isolation, dotnet build, start services, stop se
Octo Operator
10meshmakers/octo-claude-skills
Use this skill for developing and operating the OctoMesh Communication Operator — the .NET 10 KubeOps Kubernetes operator that watches CommunicationPool CRDs, connects to the Communication Controller over SignalR (/operatorHub), and runs helm upgrade/uninstall for Adapter and Application workloads. Covers edge vs central deployment modes, the Helm values layering model (context < base < overrides), secret injection tiers, CRD generation, the TUnit + Microsoft.Testing.Platform test workflow on .NET 10, and the local kind cluster developer loop. Also covers the octo-helm-core chart repository (o
Hex Project
8hex-inc/hex-skills
Full lifecycle management of Hex projects and apps from CoCo. Create, edit, run, deploy, and publish Hex projects. Manage cells, runs, connections, and app deployments. Use when: creating a Hex project, adding cells, running notebooks, deploying apps, publishing Hex apps, managing Hex connections, exporting/importing projects. Triggers: create hex project, new hex project, hex project, hex app, hex cell, hex run, deploy hex, publish hex, hex notebook, run hex, export hex, import hex, hex connection, hex data source, add cell, create cell, run cell, hex publish app.
Browse the most popular Claude skills, all devops & cloud skills, or write your own with the skills generator.