emergency-rescueRecover 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.
Install via ClawdBot CLI:
clawdbot install gitgoodordietrying/emergency-rescueGrade Good — based on market validation, documentation quality, package completeness, maintenance status, and authenticity signals.
Accesses sensitive credential files or environment variables
~/.ssh/id_rsaHardcoded API key or token pattern found in skill definition
AKIAXXXXXXXX...Potentially destructive shell commands in tool definitions
rm -rf ~Accesses system directories or attempts privilege escalation
sudo cpGenerated Mar 1, 2026
A developer accidentally force-pushes to a shared branch like main, overwriting remote history. This scenario requires diagnosing the last known-good commit using reflog or platform audit logs and safely restoring it with --force-with-lease to prevent data loss.
Sensitive credentials such as API keys or passwords are committed to a public git repository. Immediate action involves revoking the compromised credentials first, then removing them from git history using tools like git filter-repo to prevent automated scraping and security breaches.
A system runs out of disk space, causing application failures or crashes. This scenario involves identifying and cleaning up large files, logs, or caches using commands like du and rm, and implementing monitoring to prevent recurrence in production environments.
A database becomes corrupted due to failed migrations or hardware issues, leading to data inconsistency. Steps include diagnosing with integrity checks, restoring from backups, and applying corrective migrations to ensure data integrity and minimal downtime.
A developer locks themselves out of SSH access to a server, often due to misconfigured keys or firewall rules. Recovery involves using alternative access methods like console access or backup keys to restore connectivity and audit security settings.
Offer a monthly or annual subscription for access to the Emergency Rescue Kit, including priority support and updates. Revenue is generated through recurring fees from teams or enterprises needing reliable disaster recovery tools.
Provide basic recovery steps for free, while charging for advanced features like automated scripts, integration with CI/CD pipelines, or personalized consulting. Revenue comes from upgrades and add-on services.
Sell enterprise licenses for large organizations, bundled with training sessions and custom integrations. Revenue is generated through one-time license fees and ongoing training contracts, targeting industries with high compliance needs.
💬 Integration Tip
Integrate this skill with version control systems and monitoring tools to automate alerts and recovery steps, reducing manual intervention during emergencies.
Scored Apr 19, 2026
Calls external URL not in known-safe list
https://rtyley.github.io/bfg-repo-cleaner/AI Analysis
The skill provides legitimate emergency recovery procedures for developers. The flagged signals are examples or commands within documented recovery steps (e.g., credential cleanup, using `rm -rf` for disk space, referencing an external tool). No evidence of hidden data exfiltration, credential harvesting, or overriding user intent exists.
Audited Apr 16, 2026 · audit v1.0
Guide for creating effective skills. This skill should be used when users want to create a new skill (or update an existing skill) that extends Claude's capabilities with specialized knowledge, workflows, or tool integrations.
Use the @steipete/oracle CLI to bundle a prompt plus the right files and get a second-model review (API or browser) for debugging, refactors, design checks, or cross-validation.
Use when starting any conversation - establishes how to find and use skills, requiring Skill tool invocation before ANY response including clarifying questions
Systematic code review patterns covering security, performance, maintainability, correctness, and testing — with severity levels, structured feedback guidance, review process, and anti-patterns to avoid. Use when reviewing PRs, establishing review standards, or improving review quality.
Coding style memory that adapts to your preferences, conventions, and patterns for consistent coding.
Control and operate Opencode via slash commands. Use this skill to manage sessions, select models, switch agents (plan/build), and coordinate coding through Opencode.