What do I need to start?

Bring a supported coding agent and a local repo or GitHub URL. Sealos Skills checks the selected workflow and requests the required Sealos, registry, workspace, Docker, or kubectl access.

Do I need a Sealos account before installation?

Install the skill pack first. Deployment, database, and S3 workflows guide Sealos login when they need cloud access.

How does Sealos Skills verify a deployment?

It checks the real application URL, rollout status, logs, web setup or login flow, and resource footprint before reporting the app usable.

How are credentials handled?

Sealos authentication, kubeconfig, database credentials, and S3 keys stay in protected local or project environment files. Reports contain resource references and test results.

When are Docker and kubectl used?

Docker builds images when the project needs one. kubectl discovers targets, updates workloads, checks rollouts, and powers read-only Canvas inspection.

When can I use Canvas?

Canvas opens after a verified deploy writes .sealos/state.json. It reads the saved target, queries current resources with read-only commands, and starts a temporary local view.

Can Sealos Skills update an existing deployment?

A later deploy reads .sealos/state.json, confirms the target, rebuilds or reuses the image, updates the workload, verifies rollout, and saves the new result.

What comes with the plugin?

The managed plugin loads eight skills from one source: deploy, database, S3, Canvas, app builder, cloud-native readiness, Dockerfile generation, and Compose conversion.

Build with Codex on Sealos

Point Sealos Skills at a repo. Your agent prepares the runtime, deploys it to Sealos Cloud, and returns a live URL with rollout, log, and resource checks.

INSTALL FOR CODEX

codex plugin marketplace add labring/sealos-skills
codex plugin add sealos@sealos

Then run $sealos deploy this repo to Sealos Cloud.

View source on GitHub

8

skills from one source

9

Agent-specific guides

URL + rollout

checked before handoff

.sealos/

inspectable run evidence

AGENT GUIDES

Connect Sealos Skills to your coding agent.

Choose your agent for the exact install path, invocation, example prompts, update guidance, and deployment evidence.

9 Agent guides. One shared skill source.

Managed plugin

OpenAI

Codex

Native plugin for Codex CLI and Codex App.

View Codex guide

Managed plugin

Anthropic

Claude Code

Managed plugin install with the same eight root skills.

View Claude Code guide

Context extension

Google

Gemini CLI

Context extension. Ask Gemini to use Sealos Skills.

View Gemini CLI guide

ClawHub bundle

ClawHub

OpenClaw

Install from ClawHub. Command exposure follows the host runtime.

View OpenClaw guide

Context extension

Qwen

Qwen Code

Context extension. Ask Qwen to use Sealos Skills.

View Qwen Code guide

Repository import

Moonshot AI

Kimi Code

Copy the root skills into the project .agents/skills directory.

View Kimi Code guide

Repository import

Sourcegraph

Amp

Import the shared repository through the native Amp skill command.

View Amp guide

Packaged plugin

Qoder

Build the package, import dist/sealos-1.2.5.zip, then run /sealos.

View Qoder guide

Marketplace plugin

CodeBuddy

Register the Sealos marketplace. Command exposure follows the host runtime.

View CodeBuddy guide

Install through skills.sh

Use the direct skill-pack path when your coding agent already supports the skills.sh ecosystem. Start with /sealos-deploy.

Open skills.sh guide

From prompt to evidence.

Every workflow shows what Sealos Skills did, what it checked, and what you can review before you call it done.

Your prompt

$sealos deploy this repo to Sealos Cloud

What Sealos Skills does

Inspect runtime, ports, dependencies, and cloud readiness
Reuse an image or build one, then generate the Sealos template
Deploy or update the target and run rollout checks

Evidence you get

>.sealos/analysis.json

>.sealos/template/index.yaml

>.sealos/state.json

>Live application URL and workload status

Verified resultDeployment verified

CLOUD CAPABILITIES

The cloud work between your repo and a live app.

Prepare the runtime, connect the services your app needs, deploy, update, and inspect the result from the same agent.

sealos-deploy

Deploy and verify your app

Inspect the repo, prepare its runtime, deploy to Sealos Cloud, and check the live result.

Live URL, healthy rollout, and saved run state

sealos-database

Connect a managed database

Create or reuse Postgres, MySQL, MongoDB, or Redis and wire only the environment values the app needs.

Connected service and tested app path

sealos-s3

Add private object storage

Create a private bucket, place credentials safely, and verify the app's real object-storage path.

Working S3 path with protected credentials

sealos-canvas

Inspect live resources

Read saved deployment state and open a temporary, read-only view of current Sealos resources.

Local canvas backed by live resource data

sealos-app-builder

Build for Sealos Desktop

Apply Sealos SDK and platform conventions while the agent builds the app.

Desktop app foundation ready for Sealos

cloud-native-readiness

Find deployment blockers

Check runtime, state, storage, configuration, and operations before deployment.

Prioritized blockers and next steps

dockerfile-skill

Create a production Dockerfile

Generate and build-check a Dockerfile for the detected framework and runtime.

Build-tested container definition

docker-to-sealos

Convert Compose into Sealos

Turn Docker Compose services into a reviewable Sealos template and run quality checks.

Validated Sealos template

Before the first run

Start with a project. Set up the rest as you go.

Sealos Skills checks the tools and access each workflow needs, then guides login, registry, and workspace setup.

A project and a supported agent

Start with a local repo or GitHub URL in a documented coding agent.

Sealos Cloud access

Sign in when a workflow needs to create or inspect resources in your Sealos workspace.

A container registry for deploys

Use Docker Hub, GHCR, or an existing image path when deployment needs an image.

Tools checked on demand

Preflight asks for Docker or kubectl when the selected workflow uses them.

Deploy your repo. Keep the evidence.

Install Sealos Skills in Codex, run $sealos, and review the live result before you call it shipped.

View all install paths

GitHub source MIT license

Build withBuild with Codex on Sealoson Sealos