Skip to content
Back to search

sealos-skills

MarketplaceWorks with Claude CodeGitHub

Sealos agent skills for deploying, configuring, monitoring, and troubleshooting apps on Sealos Cloud from Claude Code.

Safety scan

A static text scan, not a guarantee. Select the badge to see what was scanned and every finding.

Checked today
Badge for your README
findsafeskills safety rating

Markdown

[![findsafeskills safety rating](/api/listings/labring--sealos-skills/badge.svg)](/listings/labring--sealos-skills)

HTML

<a href="/listings/labring--sealos-skills"><img src="/api/listings/labring--sealos-skills/badge.svg" alt="findsafeskills safety rating" /></a>

Install

Install instructions from the README

As written by the repo's author. findsafeskills has not verified these steps.

Cursor

From a published GitHub repo: **Settings → Plugins**, paste the repository URL in **Search or Paste Link**, open the Sealos plugin, click **Add to Cursor**.

For local development, symlink the skill into your personal skills folder:

ln -sfn "$(pwd)/plugins/sealos/skills/use-sealos" ~/.cursor/skills/use-sealos

Claude Code

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

Use `/sealos` for interactive work. The marketplace also accepts a local checkout path.

Codex

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

In Codex CLI, invoke `$sealos`; in Codex App, select Sealos under Plugins. The marketplace source is `.agents/plugins/marketplace.json`; the plugin manifest is `plugins/sealos/.codex-plugin/plugin.json`. A repository-root Codex manifest is also included for direct importers.

Qoder

In Qoder, open the plugin **Marketplace** (Settings → Plugins → Marketplace), click **+ Create Plugin**, choose **import from a local folder**, and select `plugins/sealos` from a clone of this repository.

To distribute, zip the contents of `plugins/sealos` (the zip root must contain `.qoder-plugin/plugin.json`) as `sealos-2.0.0.zip` and share or publish it through the Qoder marketplace.

Use `/sealos` in Qoder after installation.

DeepSeek Harness

This repository is a dsh profile bundle. After `npx @deepseek-ai/dsh web` works, install the plugin into the same `web` profile (`pnpm` must be on `PATH`):

npx @deepseek-ai/dsh plugin --profile web add github:labring/sealos-skills
npx @deepseek-ai/dsh web

A local checkout:

npx @deepseek-ai/dsh plugin --profile web add /path/to/sealos-skills

`use-sealos` appears in the session skill catalog. Say "deploy X to Sealos"; the model loads the skill via the `skill` tool, then runs `scripts/sealos-api.py` / `kubectl` through bash.

Login writes `~/.sealos/kubeconfig`; grant the host's required filesystem access when prompted.

Add the GitHub topic `dsh-plugin` on the public repo so it shows up in the harness plugin index.

OpenClaw

Install the plugin directory, not the repository root:

openclaw plugins install /path/to/sealos-skills/plugins/sealos

OpenClaw loads it as a Cursor bundle and exposes `use-sealos`. Slash-command exposure is not claimed. Say "deploy X to Sealos".

Do not install the repo root. OpenClaw sees root `package.json` first, treats the checkout as a native plugin, and fails because that package has no `openclaw.extensions`. Root `openclaw.plugin.json` is not used on that path.

CodeBuddy

/plugin marketplace add labring/sealos-skills

Command exposure depends on the CodeBuddy runtime.

Gemini CLI

Context-only extension. Slash commands are not claimed.

gemini extensions install https://github.com/labring/sealos-skills

Ask Gemini to deploy to Sealos Cloud. It loads `CLAUDE.md`, which points at `use-sealos`.

Qwen Code

Context-only extension. Slash commands are not claimed.

qwen extensions install https://github.com/labring/sealos-skills

skills.sh

npx skills add labring/sealos-skills

The pack installs three skills: `use-sealos` (the interactive entry — say "deploy X to Sealos"), plus `sealos-deploy` and `k8s-kaniko-job`, which are inert outside a managed sandbox (see below).

Brain (managed sandbox)

Brain's GitHub-deploy pipeline installs this pack into a Devbox with `npx skills add <repo> -y` and drives the `sealos-deploy` skill in managed mode (`SEALAI_DEPLOY_MODE=managed`, MCP handshake via `template_ready` / `deployment_completed`, source builds via a `k8s-kaniko-job` Kaniko Job). Point Brain's `DEPLOY_SKILL_SOURCE` env at this repository. The design and the full control-plane contract live in `BRAIN-ADAPTATION.md`.

Amp / Kimi / generic repo importers

What was scanned

The files the safety scan read, as written by the repository's author and shown as plain text. Lines with a finding are marked.

.claude-plugin/marketplace.json · Manifest · 21 lines

View this file on GitHub (read at the repository's current version: the scan did not record which commit it read)

  1. {
  2. "$schema": "https://anthropic.com/claude-code/marketplace.schema.json",
  3. "name": "sealos-skills",
  4. "description": "Sealos agent skills for deploying, configuring, monitoring, and troubleshooting apps on Sealos Cloud from Claude Code.",
  5. "owner": {
  6. "name": "Sealos",
  7. "email": "contact@sealos.io"
  8. },
  9. "plugins": [
  10. {
  11. "name": "sealos",
  12. "description": "Sealos agent skills for deploying, configuring, monitoring, and troubleshooting apps on Sealos Cloud from Claude Code. Deploy from the template store, official Docker images, or project source; manage databases, object storage, networking, and logs.",
  13. "author": {
  14. "name": "Sealos"
  15. },
  16. "source": "./plugins/sealos",
  17. "category": "deployment",
  18. "homepage": "https://sealos.io"
  19. }
  20. ]
  21. }
README.md · README · 225 lines

View this file on GitHub (read at the repository's current version: the scan did not record which commit it read)

  1. # sealos-skills
  2. Agent plugin for deploying and operating apps on [Sealos Cloud](https://sealos.io),
  3. packaged in the [Agent Plugins](https://agent-plugins.org/) format and as a
  4. [DeepSeek Harness](https://github.com/deepseek-ai/deepseek-harness) profile bundle.
  5. The same `use-sealos` skill is also installable through Codex, Claude Code,
  6. Cursor, Qoder, `skills.sh`, OpenClaw / ClawHub, CodeBuddy, Gemini CLI, Qwen
  7. Code, and generic repo importers.
  8. Say "deploy X to Sealos" (or "帮我把 X 部署到 Sealos") in a compatible agent
  9. and the `use-sealos` skill handles the rest: sign-in, picking the fastest
  10. deploy path, databases, storage, public HTTPS, and post-deploy verification.
  11. ## What's inside
  12. ```
  13. package.json # DeepSeek Harness bundle manifest (`dsh.bundle`)
  14. cordis.patch.yml # inserts the skill provider into a dsh profile
  15. index.js # registers `use-sealos` on `ctx.skills`
  16. CLAUDE.md # context-only hosts (Gemini, Qwen, Amp / Kimi)
  17. gemini-extension.json # Gemini CLI extension
  18. qwen-extension.json # Qwen Code extension
  19. openclaw.plugin.json # unused on OpenClaw's native package.json path; install plugins/sealos instead
  20. .codex-plugin/plugin.json # root Codex import manifest
  21. .agents/plugins/marketplace.json # Codex marketplace entry
  22. .codebuddy-plugin/marketplace.json # CodeBuddy marketplace
  23. skills/ # skills.sh entries (symlinks → plugins/sealos/skills/*)
  24. plugins/sealos/
  25. ├── .codex-plugin/plugin.json # Codex marketplace plugin manifest
  26. ├── .claude-plugin/plugin.json # Claude Code manifest
  27. ├── .cursor-plugin/plugin.json # Cursor manifest
  28. ├── .qoder-plugin/plugin.json # Qoder manifest
  29. ├── commands/sealos.md # /sealos for compatible plugin hosts
  30. └── skills/
  31. ├── use-sealos/
  32. │ ├── SKILL.md # intent router + execution rules
  33. │ ├── references/ # loaded on demand
  34. │ │ ├── deploy.md # three deploy paths (store / image / source)
  35. │ │ ├── build.md # Dockerfile, linux/amd64 build, registry push
  36. │ │ ├── databases.md # KubeBlocks clusters + credentials
  37. │ │ ├── platform.md # manifest contract (labels, Ingress, storage, quota)
  38. │ │ ├── operate.md # status, logs, debugging, deletion
  39. │ │ └── recipes.md # per-app recipes for popular self-hosted software
  40. │ └── scripts/
  41. │ ├── sealos-api.py # auth (OAuth2 device flow) + Template API, stdlib only
  42. │ └── wait-app.sh # post-deploy readiness + URL verification
  43. ├── sealos-deploy/SKILL.md # Brain managed-mode entry (MCP-gated pipeline)
  44. └── k8s-kaniko-job/ # sandbox build executor (Kaniko Job → GHCR)
  45. ├── SKILL.md
  46. └── scripts/kaniko-build.py
  47. ```
  48. ## Installation
  49. ### Cursor
  50. From a published GitHub repo: **Settings → Plugins**, paste the repository
  51. URL in **Search or Paste Link**, open the Sealos plugin, click **Add to
  52. Cursor**.
  53. For local development, symlink the skill into your personal skills folder:
  54. ```bash
  55. ln -sfn "$(pwd)/plugins/sealos/skills/use-sealos" ~/.cursor/skills/use-sealos
  56. ```
  57. ### Claude Code
  58. ```text
  59. claude plugin marketplace add labring/sealos-skills
  60. claude plugin install sealos@sealos-skills
  61. /reload-plugins
  62. ```
  63. Use `/sealos` for interactive work. The marketplace also accepts a local
  64. checkout path.
  65. ### Codex
  66. ```sh
  67. codex plugin marketplace add labring/sealos-skills
  68. codex plugin add sealos@sealos
  69. ```
  70. In Codex CLI, invoke `$sealos`; in Codex App, select Sealos under Plugins.
  71. The marketplace source is `.agents/plugins/marketplace.json`; the plugin
  72. manifest is `plugins/sealos/.codex-plugin/plugin.json`. A repository-root
  73. Codex manifest is also included for direct importers.
  74. ### Qoder
  75. In Qoder, open the plugin **Marketplace** (Settings → Plugins → Marketplace),
  76. click **+ Create Plugin**, choose **import from a local folder**, and select
  77. `plugins/sealos` from a clone of this repository.
  78. To distribute, zip the contents of `plugins/sealos` (the zip root must
  79. contain `.qoder-plugin/plugin.json`) as `sealos-2.0.0.zip` and share or
  80. publish it through the Qoder marketplace.
  81. Use `/sealos` in Qoder after installation.
  82. ### DeepSeek Harness
  83. This repository is a dsh profile bundle. After `npx @deepseek-ai/dsh web` works, install the plugin into the same `web` profile (`pnpm` must be on `PATH`):
  84. ```sh
  85. npx @deepseek-ai/dsh plugin --profile web add github:labring/sealos-skills
  86. npx @deepseek-ai/dsh web
  87. ```
  88. A local checkout:
  89. ```sh
  90. npx @deepseek-ai/dsh plugin --profile web add /path/to/sealos-skills
  91. ```
  92. `use-sealos` appears in the session skill catalog. Say "deploy X to Sealos"; the model loads the skill via the `skill` tool, then runs `scripts/sealos-api.py` / `kubectl` through bash.
  93. Login writes `~/.sealos/kubeconfig`; grant the host's required filesystem
  94. access when prompted.
  95. Add the GitHub topic `dsh-plugin` on the public repo so it shows up in the harness plugin index.
  96. ### OpenClaw
  97. Install the plugin directory, not the repository root:
  98. ```sh
  99. openclaw plugins install /path/to/sealos-skills/plugins/sealos
  100. ```
  101. OpenClaw loads it as a Cursor bundle and exposes `use-sealos`. Slash-command
  102. exposure is not claimed. Say "deploy X to Sealos".
  103. Do not install the repo root. OpenClaw sees root `package.json` first, treats
  104. the checkout as a native plugin, and fails because that package has no
  105. `openclaw.extensions`. Root `openclaw.plugin.json` is not used on that path.
  106. ### CodeBuddy
  107. ```text
  108. /plugin marketplace add labring/sealos-skills
  109. ```
  110. Command exposure depends on the CodeBuddy runtime.
  111. ### Gemini CLI
  112. Context-only extension. Slash commands are not claimed.
  113. ```sh
  114. gemini extensions install https://github.com/labring/sealos-skills
  115. ```
  116. Ask Gemini to deploy to Sealos Cloud. It loads `CLAUDE.md`, which points at
  117. `use-sealos`.
  118. ### Qwen Code
  119. Context-only extension. Slash commands are not claimed.
  120. ```sh
  121. qwen extensions install https://github.com/labring/sealos-skills
  122. ```
  123. ### skills.sh
  124. ```sh
  125. npx skills add labring/sealos-skills
  126. ```
  127. The pack installs three skills: `use-sealos` (the interactive entry — say
  128. "deploy X to Sealos"), plus `sealos-deploy` and `k8s-kaniko-job`, which are
  129. inert outside a managed sandbox (see below).
  130. ### Brain (managed sandbox)
  131. Brain's GitHub-deploy pipeline installs this pack into a Devbox with
  132. `npx skills add <repo> -y` and drives the `sealos-deploy` skill in managed
  133. mode (`SEALAI_DEPLOY_MODE=managed`, MCP handshake via `template_ready` /
  134. `deployment_completed`, source builds via a `k8s-kaniko-job` Kaniko Job).
  135. Point Brain's `DEPLOY_SKILL_SOURCE` env at this repository. The design and
  136. the full control-plane contract live in `BRAIN-ADAPTATION.md`.
  137. ### Amp / Kimi / generic repo importers
  138. Import `https://github.com/labring/sealos-skills.git`. Behavior is
  139. host-dependent. Context is `CLAUDE.md`; the skill lives at `skills/use-sealos`
  140. and `plugins/sealos/skills/use-sealos`.
  141. ### First run
  142. Say "deploy X to Sealos". The skill checks credentials
  143. (`sealos-api.py status`) and, if needed, signs you in via OAuth2 device flow —
  144. or paste a kubeconfig from the Sealos web console into `~/.sealos/kubeconfig`.
  145. ## Deploy strategy
  146. 1. **Template store** — 200+ one-click templates, deployed via the Template
  147. API (~3 min).
  148. 2. **Official Docker image** — a generated template (workloads + KubeBlocks
  149. databases + Ingress) for self-hosted apps not in the store (~5-10 min).
  150. 3. **Source build** — Dockerfile → `docker buildx --platform linux/amd64` →
  151. registry push → image deploy (for the user's own projects).
  152. All three paths go through the Sealos Template API, so every deployment is
  153. tracked as an instance: visible in the Sealos UI and removable as a unit.
  154. ## Requirements
  155. - `kubectl`, `python3` (stdlib only); `docker` + `gh` only for the source path
  156. - A Sealos account — the skill signs in via OAuth2 device flow, or paste a
  157. kubeconfig from the Sealos web console into `~/.sealos/kubeconfig`
  158. ## Development
  159. Scratch clones, test dumps, and other local-only artifacts go in
  160. `validation-assets/` (gitignored).
  161. This 2.0 release replaces the previous eight-skill implementation. The
  162. standalone Canvas, Sealos Desktop app builder, cloud-native readiness,
  163. Dockerfile, and Compose-conversion skills are archived on the
  164. `codex/backup-before-next-20260928` branch. Deployment, database, object
  165. storage, and operations now route through `use-sealos`; Brain's managed
  166. deployment has its own `sealos-deploy` and `k8s-kaniko-job` skills.

Ratings and comments

Sign in to rate this skill.

Sign in

Free to use. If it’s helped, pass it on.