Sealos AI 工作流

Recommended: install in Codex

Add this repository as a Codex marketplace, then install the Sealos plugin:

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

One Sealos plugin installs the deploy, database, S3, canvas, app-builder, and supporting cloud-native skills from root skills/**: sealos-deploy, sealos-database, sealos-s3, sealos-canvas, sealos-app-builder, cloud-native-readiness, dockerfile-skill, and docker-to-sealos.

For compatibility and local Codex testing, install the same plugin with:

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

After installation in Codex, use the plugin from Codex:

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

Codex 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
$sealos create private S3 object storage for uploads and wire env vars

Install in Claude Code

Add this repository as a Claude Code marketplace, then install the Sealos plugin:

claude plugin marketplace add labring/sealos-skills
claude plugin install sealos@sealos

For compatibility with cross-host plugin installers, install the same plugin with:

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 in Claude Code, use /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
/sealos create private S3 object storage for uploads and wire env vars

How Setup Works

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

During the deploy, database, and object-storage 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 sealos-cli s3 for Sealos object storage buckets, credentials, quota checks, object operations, and presigned URLs
• 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 and object-storage work, you need a Sealos Cloud account and a workspace that can create the requested 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
• verify the actual Sealos App URL, logs, login/setup flow for web apps, and resource footprint before reporting the app as usable

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.
• .claude-plugin/plugin.json and .claude-plugin/marketplace.json define the Claude Code-compatible plugin surface.
• 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, Claude Code metadata, repo marketplaces, 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 plugin.json >/dev/null
python3 -m json.tool .agents/plugins/marketplace.json >/dev/null
python3 -m json.tool marketplace.json >/dev/null
python3 -m json.tool .claude-plugin/plugin.json >/dev/null
python3 -m json.tool .claude-plugin/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
/sealos-database create a cloud Postgres database for this repo and wire DATABASE_URL
/sealos-s3 create private object storage for uploads and wire env vars

After a project has been deployed, use the sealos-canvas skill through your installed plugin entry point.

/sealos-deploy, /sealos-database, and /sealos-s3 are direct skills.sh skill entries. Plugin usage should go through $sealos in Codex or /sealos in Claude Code.