Planetscale Cli Skills
v1.0.2Comprehensive PlanetScale CLI (pscale) command reference and workflows for database management via terminal. Use when user mentions PlanetScale CLI, pscale c...
⭐ 2· 722·2 current·2 all-time
byVince Lozada@vince-winkintel
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
OpenClaw
Benign
high confidencePurpose & Capability
Name/description match the actual contents: command references, workflows, and three bash automation scripts for pscale operations. The capabilities requested (running pscale CLI commands, optional service token env vars) are appropriate for a PlanetScale CLI helper.
Instruction Scope
SKILL.md only instructs running the pscale CLI and the included scripts. The scripts validate inputs, avoid eval/dynamic execution, and pass arguments as tokens. They reference the pscale config location for context but do not read or transmit unrelated system files or secrets.
Install Mechanism
No install spec (instruction-only) and scripts are included in the bundle. There are no downloaded binaries or remote installers. This is the lowest-risk install model and matches the skill's stated behavior.
Credentials
The skill documents optional environment variables PLANETSCALE_SERVICE_TOKEN_ID and PLANETSCALE_SERVICE_TOKEN for CI use — appropriate and proportionate. It also notes interactive login stores tokens in ~/.config/planetscale/. Minor inconsistency: top-level registry metadata lists no required binaries/env, while SKILL.md declares pscale as a required binary and those two env vars as optional.
Persistence & Privilege
always:false and user-invocable:true (normal). The skill does not request persistent system-wide changes or other skills' config. Scripts are local and run only when invoked.
Assessment
Overall this appears coherent and implements only PlanetScale CLI operations. Before installing or running scripts: 1) confirm you trust the skill source (README references a GitHub repo and ClawHub but source was listed as unknown); 2) ensure the pscale CLI is installed and authenticated (pscale auth login or export service token env vars); 3) note the scripts require PCRE-enabled grep (grep -oP) — this may fail on BSD/macOS grep; adjust to use grep -E/awk/jq or install GNU grep if needed; 4) do not paste service tokens into public places and don't commit them to VCS; 5) the registry metadata vs SKILL.md has a small mismatch about required binaries/env — treat pscale as required even if registry shows none. If you want extra assurance, inspect the included scripts locally (they are small and validate inputs) before running them.Like a lobster shell, security has layers — review code before you run it.
latestvk97ekdvzczcevdz8tx8j971fyd820k1x
License
MIT-0
Free to use, modify, and redistribute. No attribution required.