# sealos-skills > Package 8 Sealos Cloud skills for DeepSeek Harness, covering deployment, cloud databases, object storage, and local read-only topology views. ## Metadata - Author: [@labring](https://github.com/labring) - Repo: - GitHub: [labring/sealos-skills](https://github.com/labring/sealos-skills) - Stars: 73 - Language: Python - Homepage: - Topics: `agent-skills`, `ai-agent`, `claude-code`, `cloud-native`, `codex`, `deployment`, `docker`, `dsh-plugin`, `gemini-cli`, `kubernetes`, `sealos` - Forks: 18 - Open Issues: 6 - Last push: 2026-08-14T06:36:11.000Z - Added: 2026-08-20T00:00:00.000Z ## Install ```bash dsh plugin --profile web add github:labring/sealos-skills ``` ## Wiki ## One-Sentence Pitch Pack 8 Agent Skills maintained by the Sealos Cloud team into DeepSeek Harness's web profile in one go, enabling AI agents to directly complete operations like project deployment, cloud databases, S3 object storage, and Sealos Desktop app development within conversations. ## Core Capabilities - One-click deploy local or GitHub projects to Sealos Cloud, with automatic validation of actual URLs, login flows, logs, databases, and resource manifests after deployment - Evaluate repository cloud-native readiness (0-12 points), and hand off to Dockerfile generation phase after passing - Generate production-ready Dockerfiles for any project (including multi-stage builds, monorepo, and build-fix iterations) - Convert Docker Compose or installation docs to Sealos templates with role-based resource quotas, official routing semantics, KubeBlocks databases, and Job gates - Create managed databases such as Postgres, MySQL, MongoDB, and Redis on Sealos Cloud via sealos-cli, only writing required local environment variables - Use sealos-cli s3 to create and manage S3-compatible object storage buckets, access credentials, and presigned URLs—private by default, public access requires confirmation - Provide Sealos Desktop app development guidance, including SDK integration, iframe debugging, and beginner tutorials - Start a read-only canvas UI locally at 127.0.0.1 that reads deployed project's .sealos/state.json and kubectl resources, displaying only without modification ## Technical Implementation - **Language**: JavaScript (ESM) - **Key Dependencies**: `@deepseek-ai/cordis` (peer, injected by host), `yaml` ^2.4.2 (for parsing SKILL.md YAML frontmatter) - **Architecture Pattern**: Cordis plugin, uses `inject = ['skills']` to depend on host ctx.skills, calls `ctx.skills.registerProvider()` to register a provider named `sealos` with rank=600 (same level as host built-in provider). cordis.patch.yml appends `sealos-skills` node during bundle phase, depends on skill registry mounted by @deepseek-ai/dsh-base. - **Entry File**: index.js (sync reads skills/*/SKILL.md → registers provider → list/get returns skill list and details) ## Use Cases People using DeepSeek Harness who want AI agents to directly handle Sealos Cloud tasks. If you only want the agent to write Dockerfiles, understand docker-compose.yml, or view local resource topology from already-deployed projects, this bundle can be used standalone—but the most valuable feature is running the full "code→deploy→view results" chain. ## Prerequisites & Compatibility | Dependency | Minimum Version | Notes | |---|---|---| | DeepSeek Harness | Not declared | README example uses `npx @deepseek-ai/dsh web`, requires web profile to be installed and initialized | | Node.js | Not declared | index.js uses node:fs/promises and top-level await; test.js uses node:test, recommends Node 18+ | | pnpm | Not declared | README line 103 notes pnpm must be in PATH during bundle installation | | Platform | Cross-platform | Pure JS implementation, no OS restrictions declared | | Native modules | None | Only depends on `yaml`, no node-gyp / native extensions | | Runtime external tools | As needed | sealos-deploy metadata.compatibility requires: Sealos account/workspace, docker, buildx, gh CLI (as needed), git (as needed), kubectl, Node 18+ (optional acceleration), Python 3.8+ and PyYAML (Phase 5), kompose/crane (for Compose conversion) | ## Installation ```bash dsh plugin --profile web add github:labring/sealos-skills ``` ## Configuration This plugin requires no additional configuration. The bundle automatically scans `skills/*/SKILL.md` in the repository at startup and registers all 8 skills to ctx.skills. ## FAQ **Q: How do I invoke it in DSH after installation?** A: DSH doesn't provide a /sealos slash command for this bundle. Simply tell the agent to "deploy to Sealos Cloud", "create a cloud database", "connect to S3", or ask to view resources from the last deployment—the agent will load the corresponding sealos-* skill via the skill tool and execute it. **Q: Must I install it to the web profile?** A: Yes. README line 103 explicitly states this repository is a web profile dsh bundle, and installing to other profiles won't take effect. **Q: What external tools should I prepare before using it?** A: To actually deploy projects to the cloud, you'll need docker, buildx, kubectl, gh CLI (as needed), and sealos-cli. Generating Dockerfiles or converting docker-compose to Sealos templates only requires Node.js and Python 3.8+. The full list is in sealos-deploy's metadata.compatibility field. **Q: Do I need a Sealos Cloud account to use it?** A: Not necessarily. Cloud databases, object storage, and actual deployments all require a Sealos account and workspace. Generating Dockerfiles, converting Compose templates, and viewing the canvas don't need a cloud account. **Q: Is DSH's default bash sandbox sufficient?** A: No. Logging into Sealos writes to `~/.sealos/kubeconfig`, which the default sandbox blocks. You need to enable `sandbox_permissions: danger-full-access` in DSH configuration, otherwise the login step gets intercepted by the sandbox. **Q: How do I upgrade or uninstall?** A: Upgrade: Running `dsh plugin --profile web add github:labring/sealos-skills` again will overwrite and update skills/. Uninstall: Remove the bundle from the profile or directly delete the skills/ directory—DSH doesn't provide a dedicated uninstall command for it. **Q: How is priority determined for the 8 skills?** A: All use BUNDLED_SKILL_RANK=600 (index.js line 8), placing them at the same level as DSH's built-in skill providers, ordered by skill name in ascending order. ## Learning Curve Beginner — the bundle itself requires no configuration; install it and trigger it with natural language in sessions. However, actually completing cloud deployments requires a Sealos account, container registry, sealos-cli, and kubectl, so there's significant external preparation before running through the full process for the first time. ## Known Issues & Limitations - Installation and login depend on pnpm being in PATH (README:103) - Bash sandbox blocks `~/.sealos/kubeconfig` writes by default, requiring explicit danger-full-access enablement (README:118) - Bundle is designed only for web profile; installing to other profiles won't take effect (README:103) - Actual cloud operations (deployment, database/S3 creation) require Sealos account, workspace, and container registry; local-only generation capabilities are limited - Canvas skill requires validated last_deploy evidence in .sealos/state.json, otherwise stops rather than degrading to read-only view (skills/sealos-canvas/SKILL.md:1-7) - sealos-database/sealos-s3 default to private access; public access and deletion are gated and require explicit user confirmation (skills/sealos-database/SKILL.md, skills/sealos-s3/SKILL.md) --- This document is auto-generated by [deepseek-plugin.org](https://deepseek-plugin.org). HTML page: [sealos-skills](https://deepseek-plugin.org/plugins/labring/sealos-skills) Wiki generated by AI (model: `MiniMax-M2.5`)