Emergency Rescue Kit
v1.0.0Recover from developer disasters. Use when someone force-pushed to main, leaked credentials in git, ran out of disk space, killed the wrong process, corrupted a database, broke a deploy, locked themselves out of SSH, lost commits after a bad rebase, or hit any other "oh no" moment that needs immediate, calm, step-by-step recovery.
⭐ 1· 2.7k·14 current·15 all-time
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
OpenClaw
Suspicious
medium confidencePurpose & Capability
The skill's name and description (developer emergency recovery) align with the steps in SKILL.md (git, credential revocation, DB fixes, rollbacks). However, SKILL.md invokes additional tooling and services (GitHub/GitLab API calls via gh, AWS CLI commands, database admin commands, etc.) that are not declared in the skill's required binaries or metadata. That omission is an inconsistency: a rescue guide legitimately needs those CLIs, so they should be listed explicitly.
Instruction Scope
The instructions provide many direct, high‑privilege, possibly destructive commands (git reset --hard, push --force, revoke API keys, ALTER USER in DBs). These are expected for a rescue playbook but grant broad discretion. The SKILL.md generally flags destructive steps and follows 'diagnose → fix → verify', which is appropriate. It does, however, assume access to provider consoles/APIs and local admin privileges without stating any constraints or requiring explicit human approval steps.
Install Mechanism
Instruction-only skill with no install spec and no code files: low file‑write risk. Nothing is downloaded or installed by the registry metadata itself.
Credentials
The skill declares no required environment variables or primary credentials, yet the instructions expect the operator to have credentials/configured CLIs for GitHub, GitLab, AWS, and databases. The guidance calls for immediate credential revocation and cloud/DB admin actions — reasonable for the purpose, but the skill metadata doesn't surface these needs, which is an incoherence. Also the SKILL.md references tools (gh, aws CLI, possibly psql/mysql) that may rely on sensitive local credentials/config files; the skill doesn't document or restrict that access.
Persistence & Privilege
always is false and the skill is user‑invocable; it does not request forced or persistent presence. Autonomous invocation is allowed by default but not combined with other privilege/escalation flags.
What to consider before installing
This is a plausible emergency playbook, but it contains many high‑privilege and destructive commands and calls that expect configured admin CLIs (GitHub/GitLab CLI, AWS CLI, DB tools) and valid credentials. Before installing or running it: (1) verify you want an agent that can execute or suggest destructive recovery steps — require manual approval for any destructive action; (2) ensure the agent environment does not unintentionally hold cloud or DB credentials you don't want exposed to an automated assistant; (3) if you plan to rely on it, ask the publisher to update metadata to list the additional required CLIs (gh, aws, psql/mysql, etc.) and to add explicit safety/human‑in‑the‑loop checks; (4) prefer to run the commands yourself or review them line‑by‑line in a secure environment rather than allowing autonomous execution. If you need higher assurance, only use vetted, source‑attributed runbooks from trusted teams or vendors.Like a lobster shell, security has layers — review code before you run it.
latestvk97avv95s5xznywrq6ammpppzx80f5qd
License
MIT-0
Free to use, modify, and redistribute. No attribution required.
Runtime requirements
🚨 Clawdis
OSLinux · macOS · Windows
Any bingit, bash