Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →hashgraph-online/sealos-database
Provision, connect, and operate Sealos Cloud databases through sealos-cli for local development, Devbox development, and app setup.
Passed 8 of 16 test cases with the skill, and 7 of 16 without it.
and 2 more in the full report
5 fixed6 passed either way7 still failing4 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 5 test cases the skill fixed. Same model, same prompt, with and without the skill.
I want to query my active Sealos database instances for our staging project using `sealos-cli`. Please run the command to list databases, ensuring the output is easy to parse programmatically without scraping ASCII table borders.
| Checked | Without skill | With skill |
|---|---|---|
| Includes the `-o json` flag in the `sealos-cli database list` command. | Missed | Passed |
The instructions your model reads when the skill loads.
sealos-database (/sealos-database and database create, connect, backup, logs, or access requests).cloud-local-mutation through sealos-cli, with an optional redacted handoff to deployment.DB-REUSE-ENV, DB-CONFIRM-PUBLIC, and DB-REDACT-CONNECT.Accept a project path and database intent. Analyze first, list existing databases, create or reuse the selected type, and wire only the existing application env key. Preserve prior env values and local Compose rollback; private access is the default. Database deletion, public access, backup deletion, restore collisions, and disabling active access remain gated operations.
Never print passwords, full connection strings, kubeconfig, auth files, or copied env values. Ask before public access or destructive operations and state the private alternative. Parse JSON CLI output and keep the selected workspace, namespace, database, and env mutation scoped to the request.
For each request, resolve the project, analyze its database need, confirm CLI/auth/region/workspace, list before create/reuse, fetch connection details, wire the existing env key, and verify connectivity or migrations. Emit request-scoped success, stopped, or error; the existing analyzer-first workflow remains the domain extension below. Workspace ambiguity, an unavailable credential response, or a tracked env target stops the request before mutation.
input:
project: local path or repository source
intent: database type, purpose, and create-or-reuse preference
access: private by default; public only after confirmation
preconditions:
- analyzer evidence names the database signal and env key
- sealos-cli/auth/region/workspace are resolved
- the selected env file is ignored and the key is known
The ordered action is analyze -> resolve account/workspace -> list -> create or reuse -> wait -> fetch -> wire -> verify. The selected workspace, namespace, database identity, and env mutation remain request-scoped.
Load the analyzer, CLI, env-wiring, and connectivity procedures one level deep when their phase is reached. Keep credential-handling and public/destructive confirmation visible here even when detailed commands live in owned scripts or references.
test cases passed, vs 7 / 16 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.