How to use sealos-skills
Package 8 Sealos Cloud skills for DeepSeek Harness, covering deployment, cloud databases, object storage, and local read-only topology views.
This article is auto-derived from indexed fields (wiki / faq / compatibility_json), not freshly AI-generated.
This article is derived from the plugin's already-indexed fields (wiki / faq / compatibility_json / readme), not freshly generated by AI. Source field is noted at the end of each section.
Quick start
sealos-skills
— source: plugin_wiki.wiki_content
Install & verify
dsh plugin --profile web add github:labring/sealos-skills
Run the command above in your DSH Web Profile. Then enable the plugin in the plugin list.
— source: plugins.install
Key points
- Codex CLI: type
$sealos - Codex App: click the + button in the lower-left corner of the chat input, choose Plugins, then choose Sealos
- 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
— source: plugin_wiki.readme_en (fallback readme_raw)
FAQ
How to invoke in DSH after installation?
DSH does not provide a /sealos slash command for this bundle. Simply let the agent "deploy to Sealos Cloud" or require using cloud database/S3, and it will load and execute skills like sealos-deploy through the skill tool.
Must it be installed to the web profile?
Yes. Line 103 of the README clearly states this is a web profile dsh bundle, and installing it to other profiles will not take effect.
What external tools need to be prepared before use?
The deployment process requires docker, buildx, kubectl, gh CLI (on-demand), and sealos-cli; the pure Dockerfile generation or Compose to Sealos template phase only needs Node.js and Python 3.8+. The metadata.compatibility of sealos-deploy lists all dependencies.
Is a Sealos Cloud account required to use it?
Not necessarily. Cloud databases, object storage, and actual deployments all require a Sealos account and workspace; local packaging only (Dockerfile generation, Compose to Sealos template, read-only canvas) does not require a cloud account.
Is the default bash sandbox in DSH sufficient?
Not enough. Logging into Sealos writes to ~/.sealos/kubeconfig, which is prohibited by the default sandbox. You need to enable sandbox_permissions: danger-full-access in the DSH configuration.
How to upgrade or uninstall?
Upgrade: Run dsh plugin --profile web add github:labring/sealos-skills again to perform an in-place update of skills/. Uninstall: Remove this bundle from the profile or delete the skills/ directory; DSH does not provide a dedicated uninstall command.
— source: plugin_wiki.faq_json
Compatibility
- DSH: 未声明
- Node: 未声明
— source: plugin_wiki.compatibility_json
Pitfalls
Review the upstream repo before installing. This guide is auto-derived from indexed fields and may lag the latest release. If anything contradicts the official docs, treat the upstream source as authoritative.
— source: general rule