Database Manager
v1.0.0Plan, operate, and recover relational databases with schema governance, safe migrations, backup drills, and incident response playbooks.
⭐ 0· 989·13 current·13 all-time
byIván@ivangdavila
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
OpenClaw
Benign
high confidencePurpose & Capability
The name/description (database operations, migrations, backups, incident playbooks) aligns with the files and runtime instructions. The only requested resource is a local config/memory path (~/database-manager/), which is appropriate for durable runbooks and checklists.
Instruction Scope
All runtime instructions are documentation-centric and scoped to local files: templates, checklists, and a setup flow that (with user consent) creates ~/database-manager/ and initializes files with restrictive permissions. One ambiguous clause: the skill may 'proceed with labeled assumptions' if context is missing — this grants the agent discretion to act on inferred context unless the agent explicitly asks the user, so the user should ensure the agent asks for confirmation before making environment-specific changes.
Install Mechanism
Instruction-only skill with no install spec and no code files. No packages, downloads, or executable installs are performed by the skill itself.
Credentials
The skill requests no environment variables, no credentials, and only a config path under the user's home. Files are expected to be plain text and the documentation explicitly says not to store secrets in memory files.
Persistence & Privilege
The skill persists durable state only under ~/database-manager/, a path declared in metadata and the setup docs. It is not always-enabled and does not request system-wide or other skills' config changes. The skill allows autonomous invocation by default (platform default) but that is not combined with elevated privileges or broad credential access.
Assessment
This skill appears coherent and limited to local runbooks. Before enabling: confirm you are comfortable with the agent creating ~/database-manager/ (it will create files and set restrictive permissions if you approve); do not store DB connection strings, passwords, or private keys in these files; ensure the agent asks for explicit confirmation before executing any steps that would connect to or modify production databases (the docs require user confirmation for destructive operations); and be cautious if you install the related runtime skills (sql, mysql, prisma) — those may request credentials or binaries to actually connect to databases. If you want higher assurance, validate the skill's homepage/owner or run it in a sandboxed account/home directory first.Like a lobster shell, security has layers — review code before you run it.
latestvk977qy4qb6vbwbfbg5est5axax8253cx
License
MIT-0
Free to use, modify, and redistribute. No attribution required.
Runtime requirements
🗄️ Clawdis
OSLinux · macOS · Windows
Config~/database-manager/