{
  "markdown": "# Sealos Skills\n\n<!-- README-I18N:START -->\n\n**English** | [简体中文](./readmes/README.zh-CN.md) | [繁體中文](./readmes/README.zh-TW.md) | [日本語](./readmes/README.ja.md) | [한국어](./readmes/README.ko.md) | [Español](./readmes/README.es.md) | [Français](./readmes/README.fr.md) | [Deutsch](./readmes/README.de.md) | [Português (Brasil)](./readmes/README.pt-BR.md) | [Русский](./readmes/README.ru.md) | [العربية](./readmes/README.ar.md) | [हिन्दी](./readmes/README.hi.md) | [Bahasa Indonesia](./readmes/README.id.md)\n\n<!-- README-I18N:END -->\n\nDeploy projects to [Sealos Cloud](https://sealos.io) from your AI agent.\n\nSealos Skills is a plugin-first skill pack centered on Sealos Cloud development and deployment. It helps an AI agent inspect a project, prepare missing deployment artifacts, connect Sealos Cloud databases and object storage for development, build or reuse a container image, ship the app to Sealos Cloud, and view deployed resources in a local read-only canvas.\n\nThe recommended Codex path is native Codex plugin installation. Cross-host plugin installs, `skills.sh`, and context-only extension hosts such as Gemini CLI and Qwen Code use the same root `skills/**` source.\n\n## Quick Start\n\n### Recommended: install in Codex\n\nAdd this repository as a Codex marketplace, then install the Sealos plugin:\n\n```bash\ncodex plugin marketplace add labring/sealos-skills\ncodex plugin add sealos@sealos\n```\n\nOne 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`.\n\nFor compatibility and local Codex testing, install the same plugin with:\n\n```bash\nnpx plugins add https://github.com/labring/sealos-skills --target codex\n```\n\nAfter installation in Codex, use the plugin from Codex:\n\n- **Codex CLI:** type `$sealos`\n- **Codex App:** click the **+** button in the lower-left corner of the chat input, choose **Plugins**, then choose **Sealos**\n\n![Select the Sealos plugin in Codex App](./assets/codex-sealos.png)\n\nCodex examples:\n\n```text\n$sealos deploy this repo to Sealos Cloud\n$sealos deploy /path/to/project\n$sealos deploy https://github.com/labring-sigs/kite\n$sealos create a cloud Postgres database for this repo and wire DATABASE_URL\n$sealos create private S3 object storage for uploads and wire env vars\n```\n\n### Install in Claude Code\n\nAdd this repository as a Claude Code marketplace, then install the Sealos plugin:\n\n```bash\nclaude plugin marketplace add labring/sealos-skills\nclaude plugin install sealos@sealos\n```\n\nFor compatibility with cross-host plugin installers, install the same plugin with:\n\n```bash\nnpx plugins add https://github.com/labring/sealos-skills --target claude-code\n```\n\nIf you only use one detected agent tool on the machine, you can let `plugins` choose the target:\n\n```bash\nnpx plugins add https://github.com/labring/sealos-skills\n```\n\nAfter installation in Claude Code, use `/sealos`:\n\n```text\n/sealos deploy this repo to Sealos Cloud\n/sealos deploy /path/to/project\n/sealos deploy https://github.com/labring-sigs/kite\n/sealos create a cloud Postgres database for this repo and wire DATABASE_URL\n/sealos create private S3 object storage for uploads and wire env vars\n```\n\n### Test in Qoder\n\nBuild the Qoder plugin package from the repository root:\n\n```bash\npython3 scripts/package-qoder-plugin.py\n```\n\nImport `dist/sealos-1.2.5.zip` into Qoder. The package exposes the same eight root-level skills as the Codex plugin and provides `/sealos` as its command entry point.\n\nQoder examples:\n\n```text\n/sealos deploy this repo to Sealos Cloud\n/sealos create a cloud Postgres database for this repo and wire DATABASE_URL\n/sealos create private S3 object storage for uploads and wire env vars\n/sealos show the resources created by the last deployment\n```\n\n### Install in DeepSeek Harness\n\nThis repository is a dsh profile bundle over the same root `skills/**` source. After `npx @deepseek-ai/dsh web` works, install it into the same `web` profile (`pnpm` must be on `PATH`):\n\n```sh\nnpx @deepseek-ai/dsh plugin --profile web add github:labring/sealos-skills\nnpx @deepseek-ai/dsh web\n```\n\nA local checkout:\n\n```sh\nnpx @deepseek-ai/dsh plugin --profile web add /path/to/sealos-skills\n```\n\nThe eight root skills appear in the session skill catalog. Ask the agent to deploy to Sealos Cloud; it loads `sealos-deploy` (and sibling skills as needed) through the `skill` tool, then runs `kubectl` / `sealos-cli` through bash.\n\nThe default bash sandbox blocks writes outside the workspace. Login writes `~/.sealos/kubeconfig`, so those commands need `sandbox_permissions: danger-full-access`.\n\n### Other supported AI tools\n\n| Tool | Install | Usage |\n| --- | --- | --- |\n| Codex CLI / Codex App | `codex plugin marketplace add labring/sealos-skills` then `codex plugin add sealos@sealos` | `$sealos` in Codex CLI, or **+** → **Plugins** → **Sealos** in Codex App |\n| Claude Code | `claude plugin marketplace add labring/sealos-skills` then `claude plugin install sealos@sealos` | `/sealos` |\n| Claude Code compatibility path | `npx plugins add https://github.com/labring/sealos-skills --target claude-code` | `/sealos` |\n| Qoder | Build with `python3 scripts/package-qoder-plugin.py`, then import the ZIP | `/sealos` or automatic skill selection |\n| DeepSeek Harness | `npx @deepseek-ai/dsh plugin --profile web add github:labring/sealos-skills` | Ask the agent to use Sealos skills; there is no `/sealos` slash command |\n| OpenClaw / ClawHub | `clawhub install labring/sealos-skills` | Host command exposure depends on the ClawHub runtime |\n| CodeBuddy | `/plugin marketplace add labring/sealos-skills` | Host command exposure depends on the CodeBuddy runtime |\n| Gemini CLI | `gemini extensions install https://github.com/labring/sealos-skills` | Context-only extension; ask Gemini to use Sealos Skills |\n| Qwen Code | `qwen extensions install https://github.com/labring/sealos-skills` | Context-only extension; ask Qwen to use Sealos Skills |\n| Amp / Kimi / generic repo importers | Import `https://github.com/labring/sealos-skills.git` | Host-dependent |\n\nGemini CLI and Qwen Code manifests provide repository context through `CLAUDE.md`; they do not claim slash-command support.\n\n### Alternative: install as a `skills.sh` skill pack\n\nIf your agent uses `skills.sh` directly, install the same skills pack with:\n\n```bash\nnpx skills add labring/sealos-skills\n```\n\nThen run the deploy skill directly:\n\n```text\n/sealos-deploy\n/sealos-deploy /path/to/project\n/sealos-deploy https://github.com/labring-sigs/kite\n/sealos-database create a cloud Postgres database for this repo and wire DATABASE_URL\n/sealos-s3 create private object storage for uploads and wire env vars\n```\n\nAfter a project has been deployed and `.sealos/state.json` contains verified `last_deploy` runtime evidence, use the `sealos-canvas` skill through your installed plugin entry point for a local read-only view. Canvas stays plugin-pack mediated because it consumes verified deployment state.\n\n`/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.\n\n## Why Use the Plugin\n\nPrefer the plugin install for Codex, Claude Code, and Qoder because it:\n\n- installs all Sealos skills as one managed package\n- exposes the same skills across supported agent tools\n- keeps the plugin metadata, logo, prompts, commands, and capabilities together\n- avoids maintaining a separate packaged copy of the skills\n\n## Plugin Distribution\n\nThe Codex integration follows [OpenAI's Codex plugin build guide](https://developers.openai.com/codex/plugins/build):\n\n- `.codex-plugin/plugin.json` contains plugin identity, discovery metadata, interface copy, default prompts, brand metadata, and asset paths relative to the repository root.\n- `.agents/plugins/marketplace.json` registers this repo-local plugin for local Codex marketplace testing.\n- `.claude-plugin/plugin.json` and `.claude-plugin/marketplace.json` define the Claude Code-compatible plugin surface.\n- `.qoder-plugin/plugin.json` defines the Qoder plugin surface and explicitly exposes all eight Codex skills.\n- `qoder.md` provides Qoder-level routing and safety instructions without copying skill implementations.\n- `distribution/platforms.json` records platform support claims and evidence.\n- `marketplaces/README.md` owns marketplace rules and prevents command-support overclaims.\n- `scripts/validate-codex-plugin.py` validates the Codex manifest, Claude Code metadata, repo marketplaces, platform registry, and asset paths.\n- `scripts/package-qoder-plugin.py` builds a Qoder-compatible ZIP with the plugin manifest at the archive root.\n- `skills/**/SKILL.md` remains the only skill source; do not add a second packaged copy of the skills.\n- `package.json`, `cordis.patch.yml`, and `index.js` register that same root skill tree as a DeepSeek Harness profile bundle.\n\nValidate plugin metadata before publishing or pushing manifest changes:\n\n```bash\npython3 scripts/validate-codex-plugin.py\npython3 -m json.tool .codex-plugin/plugin.json >/dev/null\npython3 -m json.tool plugin.json >/dev/null\npython3 -m json.tool .agents/plugins/marketplace.json >/dev/null\npython3 -m json.tool marketplace.json >/dev/null\npython3 -m json.tool .claude-plugin/plugin.json >/dev/null\npython3 -m json.tool .claude-plugin/marketplace.json >/dev/null\npython3 -m json.tool .qoder-plugin/plugin.json >/dev/null\npython3 -m json.tool distribution/platforms.json >/dev/null\n```\n\n## How Setup Works\n\nYou only need a plugin-compatible or `skills.sh` compatible AI agent and a project to deploy.\n\nDuring the deploy, database, and object-storage flows, Sealos Skills will:\n\n- check whether tools such as Docker and `kubectl` are available\n- guide the user through Sealos login when needed\n- use `sealos-cli` for Sealos Cloud database creation, connection details, and database operations\n- use `sealos-cli s3` for Sealos object storage buckets, credentials, quota checks, object operations, and presigned URLs\n- use or help prepare a container registry path such as Docker Hub or GHCR\n\nFor 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.\n\n## What Sealos Deploy Handles\n\nOn a typical deploy, the agent will:\n\n- assess the project structure and runtime needs\n- reuse an existing image or build one when needed\n- generate a Sealos template\n- deploy and verify rollout\n- verify the actual Sealos App URL, logs, login/setup flow for web apps, and resource footprint before reporting the app as usable\n\nLater runs can switch to an in-place update flow when an existing deployment is detected.\n\n## What Sealos Database Handles\n\nFor a local project or Devbox that needs a cloud database, the agent will:\n\n- detect database signals such as `DATABASE_URL`, Prisma, Drizzle, MongoDB, MySQL, or Redis\n- use `sealos-cli database` to list, create, inspect, and connect Sealos Cloud databases\n- write only the required local env key without exposing secrets in chat\n- verify the app's real database path through migrations, introspection, or startup checks\n- manage public access only after confirmation\n\n## What Sealos S3 Handles\n\nFor a local project or Devbox that needs S3-compatible object storage, the agent will:\n\n- detect object-storage signals such as S3 env keys, AWS SDK usage, MinIO, upload paths, or presigned URL code\n- use `sealos-cli s3` from `zjy365/sealos-cli#28` to list, create, inspect, and update object storage buckets\n- initialize S3 credentials only when needed and keep access keys out of chat\n- wire the smallest required local env keys for bucket, endpoint, access key, secret key, region, and path-style settings\n- verify upload, list, download, delete, or presigned URL behavior with the project's real storage path\n- make buckets public or rotate credentials only after confirmation\n\n## What Sealos Canvas Handles\n\nFor a repository already deployed by Sealos Deploy, the agent will:\n\n1. Read `.sealos/state.json` to locate the deployed app.\n2. Query the Sealos namespace with read-only `kubectl get` commands.\n3. Start a temporary `127.0.0.1` canvas UI.\n4. Output and open the local UI address for inspection.\n\nIf the project has not been deployed yet, Sealos Canvas stops and directs the user to deploy the project first.\n\n## Included Skills\n\nThe plugin and `skills.sh` pack expose the same skill source:\n\n- `sealos-deploy` — deploy a local or GitHub project to Sealos Cloud\n- `sealos-database` — create, connect, and operate Sealos Cloud databases for development\n- `sealos-s3` — create buckets, connect credentials, check quota, and operate Sealos S3-compatible object storage\n- `sealos-canvas` — view deployed Sealos resources in a local read-only canvas UI\n- `sealos-app-builder` — build Sealos Desktop apps with SDK integration\n- `cloud-native-readiness` — assess deployment readiness\n- `dockerfile-skill` — generate production-ready Dockerfiles\n- `docker-to-sealos` — convert Docker Compose services into Sealos templates\n\n## Repository\n\n[`skills/`](./skills) is the single source of truth for Sealos deploy, Sealos canvas, and the supporting skills used during the deploy flow. The same root-level skills directory serves `skills.sh` installs and every plugin or extension manifest in this repository.\n\nImportant distribution files:\n\n- [`.codex-plugin/plugin.json`](./.codex-plugin/plugin.json) — Codex plugin manifest\n- [`.agents/plugins/marketplace.json`](./.agents/plugins/marketplace.json) — local Codex marketplace entry\n- [`.claude-plugin/plugin.json`](./.claude-plugin/plugin.json) — Claude Code-compatible plugin manifest\n- [`.qoder-plugin/plugin.json`](./.qoder-plugin/plugin.json) — Qoder plugin manifest\n- [`qoder.md`](./qoder.md) — Qoder plugin routing and safety instructions\n- [`marketplace.json`](./marketplace.json) and [`.claude-plugin/marketplace.json`](./.claude-plugin/marketplace.json) — Claude-compatible marketplace entries\n- [`.codebuddy-plugin/marketplace.json`](./.codebuddy-plugin/marketplace.json) — CodeBuddy marketplace entry\n- [`gemini-extension.json`](./gemini-extension.json) — Gemini CLI context extension\n- [`qwen-extension.json`](./qwen-extension.json) — Qwen Code context extension\n- [`openclaw.plugin.json`](./openclaw.plugin.json) — OpenClaw / ClawHub bundle pointer\n- [`package.json`](./package.json), [`cordis.patch.yml`](./cordis.patch.yml), and [`index.js`](./index.js) — DeepSeek Harness profile bundle; registers root `skills/**` on `ctx.skills`\n- [`commands/sealos.md`](./commands/sealos.md) — `/sealos` plugin command entry for compatible hosts\n- [`distribution/platforms.json`](./distribution/platforms.json) — platform support registry\n- [`marketplaces/README.md`](./marketplaces/README.md) — marketplace rules and support-claim ownership\n- [`scripts/validate-codex-plugin.py`](./scripts/validate-codex-plugin.py) — Codex plugin validation\n- [`scripts/package-qoder-plugin.py`](./scripts/package-qoder-plugin.py) — Qoder ZIP packager\n\nDo not add a second packaged copy of the skills. Root `skills/**` is the only skill source for all installation paths.\n\n## License\n\nMIT\n",
  "bytes": 15424,
  "sha": "a36f92f8f9edf8483a71ed52a38dedf7e0fda3ab66486380c1167d87daa2d3fd",
  "repo_slug": "labring/sealos-skills",
  "fonte": "repo",
  "truncated": false,
  "api": "https://agentalog.com/api/listings/plg_labring_sealos_skills_d0014176/readme"
}