galyarderlabs/galyarder-framework / integrations/antigravity/recovering-from-ransomware-attack
recovering-from-ransomware-attack
UnverifiedExecutes structured recovery from a ransomware incident following NIST and CISA frameworks, including environment isolation, forensic evidence preservation, clean infrastructure rebuild, prioritized system restoration from verified backups, credential reset, and validation against re-infection. Covers Active Directory recovery, database restoration, and application stack rebuild in dependency order. Activates for requests involving ransomware recovery, post-encryption restoration, or disaster recovery from ransomware.
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 14.7 KB |
| references/api-reference.md | markdown | 1.7 KB |
| references/standards.md | markdown | 1.1 KB |
| references/workflows.md | markdown | 1.4 KB |
| scripts/agent.py | script | 6.6 KB |
| scripts/process.py | script | 10.9 KB |
references/workflows.md
View on GitHub# Workflows - Recovering from Ransomware Attack
## Workflow 1: Recovery Decision and Planning
```
Containment Complete + Forensics Initiated
|
v
[Assess backup availability]
|-- Immutable copies intact? --> Primary recovery path
|-- Air-gapped copies available? --> Secondary recovery path
|-- No clean backups? --> Consider decryption key (paid or NoMoreRansom)
|
v
[Determine recovery scope]
|-- Full rebuild vs. selective restore
|-- Identify minimum viable recovery set
|
v
[Map system dependencies]
|-- AD/DNS -> Database -> Application -> Web
|
v
[Estimate recovery timeline per tier]
|
v
[Brief executive team on recovery plan and timeline]
|
v
[Begin recovery]
```
## Workflow 2: System Recovery Execution
```
[Establish clean recovery VLAN]
|
v
[Phase 1: Identity Recovery]
|-- Restore DCs from verified backup
|-- Reset krbtgt (2x)
|-- Reset all admin passwords
|-- Validate AD health (dcdiag)
|
v
[Phase 2: Critical Systems]
|-- Restore databases
|-- Verify data consistency
|-- Restore core applications
|-- Test application functionality
|
v
[Phase 3: Important Systems]
|-- Restore in groups of 5-10
|-- Validate each before proceeding
|
v
[Phase 4: Remaining Systems]
|
v
[Each system: Scan for persistence -> Patch -> Deploy EDR -> Connect]
|
v
[Post-recovery monitoring (7-14 days elevated alert)]
```
---
2026 Galyarder Labs. Galyarder Framework.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| writing-skillsobra/superpowersUse when creating new skills, editing existing skills, or verifying skills work before deployment | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| xlsxanthropics/skillsUse this skill any time a spreadsheet file is the primary input or output. This means any task where the user wants to: open, read, edit, or fix an existing .xlsx, .xlsm, .xltx, .csv, or .tsv file (e.g., adding columns, computing formulas, formatting, charting, cleaning messy data); create a new spreadsheet from scratch or from other data sources; or convert between tabular file formats. Trigger especially when the user references a spreadsheet file by name or path — even casually (like "the xlsx in my downloads") — and wants something done to it or produced from it. Also trigger for cleaning or restructuring messy tabular data files (malformed rows, misplaced headers, junk data) into proper spreadsheets. The deliverable must be a spreadsheet file. Do NOT trigger when the primary deliverable is a Word document, HTML report, standalone Python script, database pipeline, or Google Sheets API integration, even if tabular data is involved. | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |
| shipping-and-launchaddyosmani/agent-skillsPrepares production launches. Use when preparing to deploy to production, or when asking what needs to be in place before shipping. Use when you need a pre-launch checklist, when setting up monitoring, when planning a staged rollout, or when you need a rollback strategy. | Stars: 119k | Updated | Claude CodeCodex | Verified | Install |
| childhoodthedotmack/claude-memBabysit a shipped release after merge, publication, or deployment. Verify published packages, production behavior, installed plugins, and late CI or user reports until the observation window is clean; use babysit for PR readiness before release. | Stars: 118k | Updated | Claude CodeCodex | Verified | Install |