Db Explorer
v2.0.4Reference tool for devtools — covers intro, quickstart, patterns and more. Quick lookup for Db Explorer concepts, best practices, and implementation patterns.
⭐ 0· 124·0 current·0 all-time
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
OpenClaw
Benign
high confidencePurpose & Capability
Name/description (reference/cheatsheet for Db Explorer) align with contained assets: SKILL.md is a reference and the included bash script prints static documentation. No extraneous credentials, binaries, or cloud-only requirements are requested.
Instruction Scope
SKILL.md explicitly states the commands output plain-text via heredoc with no network or creds required, and the script implements exactly that. Minor issues: SKILL.md metadata and script versions differ (SKILL.md v2.0.3, package metadata v2.0.4, script VERSION=2.0.2), a few command-name mismatches in docs (cheatsheet lists 'troubleshooting' while the script provides 'debugging'), and the show_help heredoc uses single quotes so the $VERSION variable will not expand — these are quality/documentation issues, not security concerns.
Install Mechanism
No install spec is present (instruction-only plus a small helper script). Nothing is downloaded or written to disk by an installer; the included script is self-contained. This is low risk.
Credentials
The skill requires no environment variables, no credentials, and the script does not read or reference any external secrets or config paths. Requested environment access is proportional (none).
Persistence & Privilege
always is false and the skill does not request persistent/system-wide changes. It does not modify other skills or system config. Autonomous invocation is allowed by default but there are no elevated privileges associated with this skill.
Assessment
This skill appears to be a harmless, local reference/cheatsheet: it only prints static documentation and does not access the network or credentials. Before installing, note small quality issues (version strings mismatch and a couple of inconsistent command names in the docs) that may affect UX but not safety. If you rely on exact command names, verify the script's available commands (intro, quickstart, patterns, debugging, performance, security, migration, cheatsheet). If you need strict version tracking or automatic updates, treat this as a local script rather than a managed package.Like a lobster shell, security has layers — review code before you run it.
latestvk979h9gdjyxzdkmspf65yegjx983gzp6
License
MIT-0
Free to use, modify, and redistribute. No attribution required.