Sealos AI 工作流

Recommended: install as a plugin

Install the Sealos plugin into Codex:

npx plugins add https://github.com/labring/sealos-skills --target codex

Install the Sealos plugin into Claude Code:

npx plugins add https://github.com/labring/sealos-skills --target claude-code

If you only use one detected agent tool on the machine, you can let plugins choose the target:

npx plugins add https://github.com/labring/sealos-skills

After installation, use the plugin from your agent:

• Codex CLI: type $sealos
• Codex App: click the + button in the lower-left corner of the chat input, choose Plugins, then choose Sealos
• Claude Code: type /sealos

Plugin examples:

$sealos deploy this repo to Sealos Cloud
$sealos deploy /path/to/project
$sealos deploy https://github.com/labring-sigs/kite
$sealos create a cloud Postgres database for this repo and wire DATABASE_URL

For Claude Code, use the same requests with /sealos:

/sealos deploy this repo to Sealos Cloud
/sealos deploy /path/to/project
/sealos deploy https://github.com/labring-sigs/kite
/sealos create a cloud Postgres database for this repo and wire DATABASE_URL

In Codex App, select Sealos from Plugins, then describe what you want to deploy.

How Setup Works

You only need a plugin-compatible or skills.sh compatible AI agent and a project to deploy.

During the deploy and database flows, Sealos Skills will:

• check whether tools such as Docker and kubectl are available
• guide the user through Sealos login when needed
• use sealos-cli for Sealos Cloud database creation, connection details, and database operations
• use or help prepare a container registry path such as Docker Hub or GHCR

For an actual deployment, you will still need a Sealos Cloud account and access to a container registry, but these do not need to be fully set up before the skill starts. For database work, you need a Sealos Cloud account and a workspace that can create database resources.

What Sealos Deploy Handles

On a typical deploy, the agent will:

• assess the project structure and runtime needs
• reuse an existing image or build one when needed
• generate a Sealos template
• deploy and verify rollout

Later runs can switch to an in-place update flow when an existing deployment is detected.

Quick Start

Why Use the Plugin

Prefer the plugin install for Codex and Claude Code because it:

• installs all Sealos skills as one managed package
• exposes the same skills across supported agent tools
• keeps the plugin metadata, logo, prompts, commands, and capabilities together
• avoids maintaining a separate packaged copy of the skills

Plugin Distribution

The Codex integration follows OpenAI's Codex plugin build guide:

• .codex-plugin/plugin.json contains plugin identity, discovery metadata, interface copy, default prompts, brand metadata, and asset paths relative to the repository root.
• .agents/plugins/marketplace.json registers this repo-local plugin for local Codex marketplace testing.
• distribution/platforms.json records platform support claims and evidence.
• marketplaces/README.md owns marketplace rules and prevents command-support overclaims.
• scripts/validate-codex-plugin.py validates the Codex manifest, repo marketplace, platform registry, and asset paths.
• skills/**/SKILL.md remains the only skill source; do not add a second packaged copy of the skills.

Validate plugin metadata before publishing or pushing manifest changes:

python3 scripts/validate-codex-plugin.py
python3 -m json.tool .codex-plugin/plugin.json >/dev/null
python3 -m json.tool .agents/plugins/marketplace.json >/dev/null
python3 -m json.tool distribution/platforms.json >/dev/null

Alternative: install as a `skills.sh` skill pack

If your agent uses skills.sh directly, install the same skills pack with:

npx skills add labring/sealos-skills

Then run the deploy skill directly:

/sealos-deploy
/sealos-deploy /path/to/project
/sealos-deploy https://github.com/labring-sigs/kite

After a project has been deployed, run a local Sealos resource canvas UI:

/sealos-canvas

/sealos-deploy is the direct skills.sh skill entry. Plugin usage should go through $sealos in Codex or /sealos in Claude Code.