Deploy and operate apps on Sealos Cloud: sign in to a Sealos account, deploy any project or self-hosted app (from the template store, an official Docker image, or project source code), provision…

Apache-2.0Auto-check passedDatabases

Install Use Sealos

skills CLI
$ npx skills add hashgraph-online/awesome-codex-plugins --skill use-sealos -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install hashgraph-online/awesome-codex-plugins use-sealos --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/hashgraph-online/awesome-codex-plugins.git skills-src && mkdir -p .claude/skills && cp -r skills-src/plugins/labring/sealos-skills/plugins/sealos/skills/use-sealos .claude/skills/use-sealos && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
use-sealos
GitHub stars
1.3k
Token cost
~2.2k tokens
SKILL.md length
849 words
Files
10 (incl. scripts, references)
Skills in repo
716
Repo updated
First seen
Licence
Apache-2.0

At a glance

Deploy and operate apps on Sealos Cloud: sign in to a Sealos account, deploy any project or self-hosted app (from the template store, an official Docker image, or project source code), provision…

  • Works in 3 steps: Known self-hosted product (Uptime Kuma,… → User's own project (has source code):… → Just a database / bucket: databases.md /
  • The user mentions Sealos (in any language
  • SKILL.md covers Sealos resource model, Tools, Preflight and Deploy decision tree (the…, plus 4 more sections
  • Runs Python and Shell scripts from its folder; calls kubectl, python3 and bash

What it does

Use Sealos is an agent skill from hashgraph-online/awesome-codex-plugins. Deploy and operate apps on Sealos Cloud: sign in to a Sealos account, deploy any project or self-hosted app (from the template store, an official Docker image, or project source code), provision managed databases (PostgreSQL, MySQL, MongoDB, Redis, Kafka), create S3-compatible object storage, expose public HTTPS domains, check status and logs, and troubleshoot failures. Use this skill whenever the user mentions Sealos (in any language, e.g. "部署到 Sealos"), or asks to deploy, host, or self-host an application…

Its SKILL.md is about 2.2k tokens, which your agent loads only when the skill is triggered. The skill folder holds 11 other files, including scripts and reference files (for example `references/build.md`, `references/databases.md` and `references/deploy.md`).

It sits in Databases, covering File uploads and storage, NoSQL databases and Event-driven systems. It works with Docker, MongoDB, MySQL and PostgreSQL. The repository describes itself as: A curated list of awesome OpenAI Codex / ChatGPT plugins, skills, and resources. The 1 Codex Marketplace. See live plugins at: https://hol.org/plugins/best-codex-plugins. The licence is Apache-2.0.

When your agent uses it

  • The user mentions Sealos (in any language
  • Tasks that involve File uploads and storage
  • Tasks that involve NoSQL databases

Example prompts

  • “部署到 Sealos”
  • “deploy X to Sealos”
  • “帮我把 X 部署到 Sealos”
  • “/use-sealos”

Requirements

  • Python 3
  • A Bash shell
  • Docker
  • Pre-approved tools (allowed-tools): Bash(kubectl:*), Bash(python3:*), Bash(docker:*), Bash(curl:*), Bash(bash:*), Bash(git:*), Bash(gh:*), Bash(command:*)

Workflow steps

3 steps, taken from the first numbered list in SKILL.md.

  1. Known self-hosted product (Uptime Kuma, Metabase, n8n, ...)
  2. User's own project (has source code): look for an existing
  3. Just a database / bucket: databases.md /

What it can do on your machine

Read from SKILL.md and the folder at commit 3e1456a. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves these tools, so the agent can use them without asking each time:

    • Bash(kubectl:*)
    • Bash(python3:*)
    • Bash(docker:*)
    • Bash(curl:*)
    • Bash(bash:*)
    • Bash(git:*)
    • Bash(gh:*)
    • Bash(command:*)

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Ships 3 files in scripts/ (Python and Shell), which the agent can run.

    Shell commands in SKILL.md call:

    • kubectl
    • python3
    • bash
    • docker

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md. Its commands use kubectl and docker, which can reach the network depending on how they are called.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Use Sealos loads about 2.2k tokens when it runs, and up to ~12k if it reads all its reference files. Until then it costs about 160 tokens; SKILL.md has 849 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~160
When it runs · the whole SKILL.md, loaded when a task matches
~2.2k
With references · SKILL.md plus every file in references/, read only if the agent opens them
~12k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); the scripts in this folder are not scanned.

SKILL.md

The full file from hashgraph-online/awesome-codex-plugins at commit 3e1456a, republished under its Apache-2.0 licence (© hashgraph-online). 849 words, ~2,195 tokens.

Download SKILL.mdSave it as .claude/skills/use-sealos/SKILL.md (or your agent's skills folder). This skill also uses 9 other files; get the full folder from GitHub.
name
use-sealos
description
Deploy and operate apps on Sealos Cloud: sign in to a Sealos account, deploy any project or self-hosted app (from the template store, an official Docker image, or project source code), provision managed databases (PostgreSQL, MySQL, MongoDB, Redis, Kafka), create S3-compatible object storage, expose public HTTPS domains, check status and logs, and troubleshoot failures. Use this skill whenever the user mentions Sealos (in any language, e.g. "部署到 Sealos"), or asks to deploy, host, or self-host an application, website, or database without naming another platform. Typical trigger: "deploy X to Sealos" / "帮我把 X 部署到 Sealos".
allowed-tools
Bash(kubectl:*), Bash(python3:*), Bash(docker:*), Bash(curl:*), Bash(bash:*), Bash(git:*), Bash(gh:*), Bash(command:*)

Use Sealos

Sealos resource model

Sealos Cloud is a multi-tenant Kubernetes platform. Everything a user owns lives in one namespace (ns-xxx) per workspace, accessed with a restricted kubeconfig (~/.sealos/kubeconfig). Within the namespace:

  • Apps are ordinary Deployments/StatefulSets + Service + Ingress, labeled cloud.sealos.io/app-deploy-manager: <app> so the Sealos "App Launchpad" UI can manage them. Public HTTPS comes free via <host>.<region-domain> and a wildcard cert.
  • Databases are KubeBlocks Cluster CRs managed by the "Database" UI.
  • Template store hosts 200+ one-click templates (sealos-api.py store-list); deployed templates are tracked as instances and appear in the UI.
  • Object storage buckets are ObjectStorageBucket CRs with S3-compatible credentials in managed secrets.
  • A region is one cluster + domain (e.g. usw-1.sealos.io for international, bja.sealos.run etc. for China). The Template API lives at https://template.<region-domain>.

Tools

Resolve scripts/ and references/ against this skill's directory, not the project working directory.

  • scripts/sealos-api.py — auth (status, login, workspaces, switch) and the Template API (deploy, store-list). Deploying through the Template API (not raw kubectl apply) is what makes resources show up as a deletable unit in the Sealos UI.
  • kubectl with export KUBECONFIG=~/.sealos/kubeconfig — all reads, debugging, and deletions. The kubeconfig is namespace-scoped; you cannot see or touch other tenants.
  • scripts/wait-app.sh — post-deploy verification (workload readiness + URL probe + failure diagnostics).
  • docker buildx — only for the source-build path.

Preflight

If SEALAI_DEPLOY_MODE is managed (a Brain-managed sandbox), stop here and follow ../sealos-deploy/SKILL.md instead — that mode forbids login and interactive prompts. Everything below is the local interactive path.

bash
python3 scripts/sealos-api.py status
  • authenticated: true → proceed; note namespace and region_domain.
  • Not authenticated → run python3 scripts/sealos-api.py login in the background, watch its stderr, and relay the sign-in URL to the user the moment it prints (the code expires; never sit silently until the command ends). Users can alternatively paste a kubeconfig from the Sealos web console (top-left avatar → kubeconfig) into ~/.sealos/kubeconfig.
  • Wrong region? login --region <url>. Wrong workspace? workspaces + switch <name>.

Deploys, database creation, and storage consume the account's quota/balance — if a deploy is rejected with a quota error, report it; do not silently retry with smaller numbers.

Deploy decision tree (the 15-minute path)

When the user wants something deployed, classify it FIRST — the wrong path wastes the whole time budget:

  1. Known self-hosted product (Uptime Kuma, Metabase, n8n, ...): python3 scripts/sealos-api.py store-list --search <name>.
    • Store hit → deploy the store template (deploy.md, Path A). Fastest and battle-tested; done in ~3 min.
    • No store hit → check recipes.md for a ready-made recipe, else use the official Docker image and write a template (deploy.md, Path B). Never build a product from source when an official image exists.
  2. User's own project (has source code): look for an existing Dockerfile/compose file, else generate one, build for linux/amd64, push, then deploy the image (build.md then deploy.md Path B).
  3. Just a database / bucket: databases.md / platform.md's object storage section — deploy as a minimal template.

After ANY deploy, verify before reporting:

bash
bash scripts/wait-app.sh -u https://<host>.<region-domain> deployment/<name> [cluster/<name>-pg ...]

On *.sealos.io regions, local deploys also claim a Brain Project in-script; if brain_adoption.ok is false, or warnings still lists incompleteResourceSet after verify, run sealos-api.py adopt <instance> — never redeploy. On *.sealos.run this is skipped (brain_adoption.reason: not-sealos-io). See deploy.md.

Quick operations

bash
export KUBECONFIG=~/.sealos/kubeconfig
kubectl get deploy,sts,pods                                   # what's running
kubectl get clusters.apps.kubeblocks.io                       # databases
kubectl get ingress -o custom-columns='NAME:.metadata.name,HOST:.spec.rules[0].host'  # public URLs
kubectl logs deploy/<name> --tail=100                         # app logs
kubectl describe pod <pod>                                    # scheduling/pull issues
kubectl get events --field-selector type=Warning --sort-by=.lastTimestamp | tail -20
kubectl scale deploy/<name> --replicas=2                      # scale
python3 scripts/sealos-api.py store-list --search <query>     # template store
Show full SKILL.md (347 more words)Show less

Routing

IntentReference
Deploy anything (store template, image, or built artifact)deploy.md
Dockerfile / image build / registry push for user sourcebuild.md
Provision or connect PostgreSQL/MySQL/MongoDB/Redis/Kafkadatabases.md
Manifest rules when writing template YAML (labels, Ingress, storage, quota ladder, object storage)platform.md
Status, logs, debugging, scaling, deletion, cost hygieneoperate.md
Per-app recipes for popular self-hosted softwarerecipes.md
Brain managed sandbox (SEALAI_DEPLOY_MODE=managed)../sealos-deploy/SKILL.md

Load only what the task needs — usually one reference, two at most.

Execution rules

  1. Never report a deploy as successful without evidence: wait-app.sh exits 0 AND the public URL returns a real page (2xx/3xx, and for SSR apps the body is not an error page). If verification fails, triage via operate.md — do not re-deploy blindly.
  2. Production images are built and pushed as linux/amd64 (docker buildx build --platform linux/amd64). Apple Silicon defaults produce arm64 images that crash-loop on Sealos with exec format error.
  3. Resource requests/limits follow the platform ladder (platform.md); requests are derived from limits, and memory always uses Mi values.
  4. Deploy through the Template API. Fall back to kubectl apply only for single resources during debugging, and remember kubectl apply rejects Deployment+volumeClaimTemplates (use StatefulSet).
  5. Destructive actions (deleting apps, databases, buckets; switching workspace on a shared machine), public-access changes, credential rotation, and system-tool installation require explicit user confirmation first.
  6. Never print secret values. Read them into shell variables or pipe them; show the user only names and how to fetch values.
  7. After mutations, read back state (kubectl get ...) before describing it.
  8. One deploy at a time per app name; name collisions in a shared namespace break selectors. Random suffixes (-a1b2c3d4) are there for a reason — keep them.
  9. If the agent sandbox blocks writes outside the workspace, escalate file access for writing ~/.sealos/kubeconfig, using the Docker socket, and any command that must read that kubeconfig.

Response format

After each operation report: what was deployed/changed (names + namespace), the public URL if any, verification evidence (ready state, HTTP code), and credentials location (secret names, never values). On failure: the failing resource, the decisive log/event lines, and the next action you are taking.

© hashgraph-online, Apache-2.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 9 other files (scripts, references) in plugins/labring/sealos-skills/plugins/sealos/skills/use-sealos of hashgraph-online/awesome-codex-plugins.

  • SKILL.md
  • references/build.md
  • references/databases.md
  • references/deploy.md
  • references/operate.md
  • references/platform.md
  • references/recipes.md
  • scripts/sealos-api.py
  • scripts/test_sealos_api_adopt.py
  • scripts/wait-app.sh

Open the folder on GitHubat commit 3e1456a

Compare with similar skills

Use Sealos next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Use Sealos compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Use Sealos this skillhashgraph-online/awesome-codex-plugins1.3k—~2.2kAutomated safety check: PassApache-2.0
Create Environmentgodatadriven/whirl205—~1.9kAutomated safety check: PassApache-2.0
Monstermq Broker Configvogler75/monster-mq143—~2.2kAutomated safety check: PassGPL-3.0
Spring Boot Project Creatorgiuseppe-trisciuoglio/developer-kit357—~3.4kAutomated safety check: NotesMIT
Cloudrun DevelopmentTencentCloudBase/CloudBase-AI-Toolkit1.1k1 repos~7.2kAutomated safety check: PassMIT
CloudbaseTencentCloudBase/CloudBase-AI-Toolkit1.1k1 repos~4.8kAutomated safety check: PassMIT

Similar skills

  • Create Environment

    godatadriven/whirl

    Create a new Whirl environment in the envs/ directory. An agent skill from godatadriven/whirl.

    205 GitHub stars~1.9k tokensUpdated 8 days ago
    Backend & APIsAuto-check passed
  • Monstermq Broker Config

    vogler75/monster-mq

    Guide for configuring, deploying, and operating the MonsterMQ broker.

    143 GitHub stars~2.2k tokensUpdated today
    DevOps & CloudAuto-check passed
  • Spring Boot Project Creator

    giuseppe-trisciuoglio/developer-kit

    Creates and scaffolds a new Spring Boot project (3.x or 4.x) by downloading from Spring Initializr, generating package structure (DDD or Layered architecture), configuring JPA, SpringDoc OpenAPI…

    357 GitHub stars~3.4k tokensUpdated 1 mo ago
    Backend & APIsAuto-check: notes
  • Cloudrun Development

    TencentCloudBase/CloudBase-AI-Toolkit

    CloudBase Run backend development rules (Function mode/Container mode).

    1.1k GitHub starsUsed in 1 repo~7.2k tokens
    DatabasesAuto-check passed
  • Cloudbase

    TencentCloudBase/CloudBase-AI-Toolkit

    A skill your agent uses when you develop, design, build, deploy, debug, migrate, or troubleshoot CloudBase (腾讯云开发, 云开发, TCB, 微信云开发) projects — Web, 微信小程序, 小程序, uni-app, mobile (iOS, Android…

    1.1k GitHub starsUsed in 1 repo~4.8k tokens
    Backend & APIsAuto-check passed
  • Official

    Manages MongoDB Atlas Stream Processing (ASP) workflows. An agent skill from mongodb/agent-skills.

    189 GitHub starsUsed in 1 repo~4.9k tokens
    Backend & APIsAuto-check passed

More from hashgraph-online/awesome-codex-plugins

All 716 skills in this repo
  • Anime Reaction Gif

    hashgraph-online/awesome-codex-plugins

    Create original anime-style reaction stickers as looping GIFs and MP4 previews, using generated character pose sheets and timed key poses.

    1.3k GitHub stars~922 tokensUpdated today
    Auto-check passed
  • Calibredb

    hashgraph-online/awesome-codex-plugins

    Manage and query Calibre libraries with the calibredb CLI (local paths or Calibre Content server URLs).

    1.3k GitHub stars~1k tokensUpdated today
    Auto-check passed
  • Rust API Test Harness

    hashgraph-online/awesome-codex-plugins

    A skill your agent uses when adding, changing, testing, or debugging Rust HTTP APIs and services, especially when Codex needs black-box integration tests, random-port app startup, real database test…

    1.3k GitHub stars~1.7k tokensUpdated today
    Auto-check passed
  • Art

    hashgraph-online/awesome-codex-plugins

    Make a studio's game look like something at build time — a cover from a real frame of the game (free), painted covers, backdrops, textures and character plates from image models through the…

    1.3k GitHub stars~2.4k tokensUpdated today
    Auto-check passed
  • Calle

    hashgraph-online/awesome-codex-plugins

    Use CALL-E from Codex through the calle CLI. An agent skill from hashgraph-online/awesome-codex-plugins.

    1.3k GitHub stars~2.9k tokensUpdated today
    Auto-check passed
  • Game Balance Economy

    hashgraph-online/awesome-codex-plugins

    Balance game difficulty, resources, rewards, probability, progression, economies, and dominant strategies.

    1.3k GitHub stars~618 tokensUpdated today
    Auto-check passed

Questions about Use Sealos

What does Use Sealos do?

Deploy and operate apps on Sealos Cloud: sign in to a Sealos account, deploy any project or self-hosted app (from the template store, an official Docker image, or project source code), provision…. Use Sealos is an agent skill from hashgraph-online/awesome-codex-plugins. Deploy and operate apps on Sealos Cloud: sign in to a Sealos account, deploy any project or self-hosted app (from the template store, an official Docker image, or project source code), provision managed databases (PostgreSQL, MySQL, MongoDB, Redis, Kafka), create S3-compatible object storage, expose public HTTPS domains, check status and logs, and troubleshoot failures.

When should I use Use Sealos?

Use Sealos fits situations like: the user mentions Sealos (in any language; tasks that involve File uploads and storage; tasks that involve NoSQL databases.

How do I install Use Sealos in Claude Code?

Run `npx skills add hashgraph-online/awesome-codex-plugins --skill use-sealos -a claude-code`. Or copy the skill folder (plugins/labring/sealos-skills/plugins/sealos/skills/use-sealos in hashgraph-online/awesome-codex-plugins) into .claude/skills/use-sealos in your project. Claude Code loads it when a task matches its description.

How do I install Use Sealos in Codex?

Run `npx skills add hashgraph-online/awesome-codex-plugins --skill use-sealos -a codex`. Or copy the skill folder (plugins/labring/sealos-skills/plugins/sealos/skills/use-sealos in hashgraph-online/awesome-codex-plugins) into .agents/skills/use-sealos in your project. Codex loads it when a task matches its description.

Can I use Use Sealos in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add hashgraph-online/awesome-codex-plugins --skill use-sealos -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/use-sealos, .gemini/skills/use-sealos, .github/skills/use-sealos and .opencode/skills/use-sealos in your project.

What does Use Sealos need to run?

Going by SKILL.md and its folder, Use Sealos needs Python and a shell for the scripts in its folder and the command-line tools its instructions call (kubectl, python3, bash and docker). Our summary lists: Python 3; A Bash shell; Docker. Its frontmatter pre-approves these tools: Bash(kubectl:*), Bash(python3:*), Bash(docker:*), Bash(curl:*), Bash(bash:*), Bash(git:*), Bash(gh:*), Bash(command:*).

Does Use Sealos access the network?

SKILL.md contains no URLs. Its commands use docker, which can reach the network depending on how they are called. This is read from the text; nothing was executed.

Is Use Sealos safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. The check reads SKILL.md only: the scripts in the folder are not scanned, so read them before running anything.

What licence does Use Sealos use?

Use Sealos is published under the Apache-2.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Use Sealos use?

About 2.2k tokens (SKILL.md is roughly 8.8k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 9.5k tokens, read only when the agent opens those files.

What are the alternatives to Use Sealos?

Skills that share tags, products or a category with Use Sealos: Create Environment (godatadriven/whirl, 205 stars), Monstermq Broker Config (vogler75/monster-mq, 143 stars), Spring Boot Project Creator (giuseppe-trisciuoglio/developer-kit, 357 stars) and Cloudrun Development (TencentCloudBase/CloudBase-AI-Toolkit, 1.1k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Use Sealos?

hashgraph-online (a GitHub organization) maintains it in hashgraph-online/awesome-codex-plugins, which has 1,267 GitHub stars. The repository holds 716 skills in this directory. The repository was last updated on October 10, 2026.

Source: hashgraph-online/awesome-codex-plugins on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.