Agent skill

Backup Recovery Policy

by Hack23 in Hack23/cia

Business continuity and disaster recovery: 30-day retention, quarterly restore tests, RTO/RPO targets per ISO 27001 A.17

Apache-2.0Auto-check passedDevOps & Cloud

Install Backup Recovery Policy

skills CLI
$ npx skills add Hack23/cia --skill backup-recovery-policy -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install Hack23/cia backup-recovery-policy --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/Hack23/cia.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.github/skills/backup-recovery-policy .claude/skills/backup-recovery-policy && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
backup-recovery-policy
GitHub stars
239
Token cost
~4.7k tokens
SKILL.md length
1,019 words
Files
1
Skills in repo
78
Repo updated
First seen
Licence
Apache-2.0

At a glance

Business continuity and disaster recovery: 30-day retention, quarterly restore tests, RTO/RPO targets per ISO 27001 A.17

  • Works in 4 steps: Immediate Actions (0-15 minutes) → Point-in-Time Recovery (15-60 minutes) → Application Cutover (60-90 minutes) → …
  • Tasks that involve Backup and disaster recovery
  • SKILL.md covers Purpose, When to Use This Skill, Business Impact-Driven Backup… and Backup Strategies, plus 10 more sections
  • Calls aws and psql

What it does

Backup Recovery Policy is an agent skill from Hack23/cia. Business continuity and disaster recovery: 30-day retention, quarterly restore tests, RTO/RPO targets per ISO 27001 A.17

Its SKILL.md is about 4.7k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in DevOps & Cloud, covering Backup and disaster recovery. The repository describes itself as: Citizen Intelligence Agency. Open-source intelligence platform analyzing Swedish political activities using AI and data visualization. Tracks politicians, government… The licence is Apache-2.0.

When your agent uses it

  • Tasks that involve Backup and disaster recovery

Example prompts

  • “/backup-recovery-policy”

Workflow steps

4 steps, taken from the first numbered list in SKILL.md.

  1. Immediate Actions (0-15 minutes)
  2. Point-in-Time Recovery (15-60 minutes)
  3. Application Cutover (60-90 minutes)
  4. Post-Recovery (90+ minutes)

What it can do on your machine

Read from SKILL.md and the folder at commit 495fd7d. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Shell commands in SKILL.md call:

    • aws
    • psql

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    Links to these hosts (documentation or services it may open):

    • github.com

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Backup Recovery Policy loads about 4.7k tokens when it runs. Until then it costs about 36 tokens; SKILL.md has 1,019 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~36
When it runs · the whole SKILL.md, loaded when a task matches
~4.7k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from Hack23/cia at commit 495fd7d, republished under its Apache-2.0 licence (© Hack23). 1,019 words, ~4,651 tokens.

Download SKILL.mdSave it as .claude/skills/backup-recovery-policy/SKILL.md (or your agent's skills folder).
name
backup-recovery-policy
description
Business continuity and disaster recovery: 30-day retention, quarterly restore tests, RTO/RPO targets per ISO 27001 A.17
license
Apache-2.0

Backup and Recovery Policy Skill

Purpose

This skill provides systematic guidance for implementing business continuity and disaster recovery within the CIA platform, ensuring data protection aligns with business impact analysis, RTO/RPO targets, and ISO 27001 Annex A.17 requirements.

When to Use This Skill

Apply this skill when:

  • ✅ Designing backup strategies for new systems or data stores
  • ✅ Configuring AWS backup services (RDS snapshots, S3 versioning, EBS backups)
  • ✅ Implementing disaster recovery procedures
  • ✅ Conducting quarterly backup restore tests
  • ✅ Defining RTO (Recovery Time Objective) and RPO (Recovery Point Objective) targets
  • ✅ Planning for data retention and archival
  • ✅ Responding to data loss incidents
  • ✅ Conducting business continuity planning

Do NOT skip for:

  • ❌ Development/test environments (may contain production data copies)
  • ❌ Temporary data stores (may become permanent)
  • ❌ "Easily reproducible" data (validate recovery procedures)
  • ❌ Third-party managed services (verify backup capabilities)

Business Impact-Driven Backup Framework

RTO/RPO Targets by Classification
ClassificationBusiness ImpactRPO TargetRTO TargetBackup FrequencyRetention
RESTRICTEDExtreme<15 minutes<1 hourContinuous replication30 days minimum
CONFIDENTIALVery High<4 hours<4 hoursHourly7 years (financial data)
INTERNALModerate<24 hours<24 hoursDaily3 years
PUBLICLow>24 hours>72 hoursWeeklyIndefinite
Backup Strategy Decision Tree
mermaid
graph TD
    START["💾 Backup Need"] --> CLASSIFY{"🏷️ Data Classification?"}
    
    CLASSIFY -->|RESTRICTED| CRITICAL["🔴 Critical Backup<br/>Continuous Replication"]
    CLASSIFY -->|CONFIDENTIAL| HIGH["🟠 High Priority<br/>Hourly Backups"]
    CLASSIFY -->|INTERNAL| MEDIUM["🟡 Medium Priority<br/>Daily Backups"]
    CLASSIFY -->|PUBLIC| STANDARD["🟢 Standard<br/>Weekly Backups"]
    
    CRITICAL --> IMPACT{"📊 Business Impact?"}
    HIGH --> IMPACT
    MEDIUM --> IMPACT
    STANDARD --> IMPACT
    
    IMPACT -->|Financial System| FINANCE["💰 Financial Data<br/>7-year retention"]
    IMPACT -->|Core Operations| CORE["🏗️ Core Systems<br/>1-year retention"]
    IMPACT -->|Support Functions| SUPPORT["🛠️ Support Systems<br/>3-month retention"]
    
    FINANCE --> METHOD{"🔧 Backup Method?"}
    CORE --> METHOD
    SUPPORT --> METHOD
    
    METHOD -->|Database| RDS["📊 AWS RDS<br/>Automated Snapshots"]
    METHOD -->|Files| S3["📁 AWS S3<br/>Versioning + Lifecycle"]
    METHOD -->|Infrastructure| IaC["🏗️ Infrastructure as Code<br/>Git + CloudFormation"]
    
    RDS --> TEST["🧪 Quarterly Restore Test"]
    S3 --> TEST
    IaC --> TEST
    
    TEST --> MONITOR["📈 Monitoring & Alerts"]
    
    style CRITICAL fill:#D32F2F
    style HIGH fill:#FF9800
    style MEDIUM fill:#FDD835
    style STANDARD fill:#4CAF50

Backup Strategies

Full Backup Strategy

Definition: Complete copy of all data at a point in time.

Use Cases:

  • Initial backup establishment
  • Monthly comprehensive backups
  • Before major system changes
  • Regulatory compliance requirements

AWS Implementation:

yaml
# CloudFormation template for full database backup
Resources:
  DatabaseFullBackupFunction:
    Type: AWS::Lambda::Function
    Properties:
      FunctionName: cia-database-full-backup
      Runtime: python3.12
      Handler: index.lambda_handler
      Role: !GetAtt BackupFunctionRole.Arn
      Timeout: 900 # 15 minutes
      Environment:
        Variables:
          RDS_INSTANCE_ID: !Ref CIADatabase
          BACKUP_BUCKET: !Ref BackupBucket
      Code:
        ZipFile: |
          import boto3
          import datetime
          import os
          
          rds = boto3.client('rds')
          
          def lambda_handler(event, context):
              """
              Create full RDS snapshot
              """
              
              instance_id = os.environ['RDS_INSTANCE_ID']
              timestamp = datetime.datetime.now().strftime('%Y%m%d-%H%M%S')
              snapshot_id = f"{instance_id}-full-{timestamp}"
              
              # Create snapshot
              response = rds.create_db_snapshot(
                  DBSnapshotIdentifier=snapshot_id,
                  DBInstanceIdentifier=instance_id,
                  Tags=[
                      {'Key': 'BackupType', 'Value': 'Full'},
                      {'Key': 'CreatedBy', 'Value': 'Automated'},
                      {'Key': 'Retention', 'Value': '30days'}
                  ]
              )
              
              print(f"Full backup initiated: {snapshot_id}")
              
              return {
                  'statusCode': 200,
                  'body': snapshot_id
              }
  
  # Schedule monthly full backups
  FullBackupSchedule:
    Type: AWS::Events::Rule
    Properties:
      Name: cia-monthly-full-backup
      Description: Monthly full database backup
      ScheduleExpression: cron(0 2 1 * ? *) # 1st of month at 2 AM UTC
      State: ENABLED
      Targets:
        - Arn: !GetAtt DatabaseFullBackupFunction.Arn
          Id: FullBackupTarget

RTO and RPO Implementation

Recovery Time Objective (RTO)

Definition: Maximum acceptable time to restore service after an outage.

RTO Tiers:

RTO LevelTime WindowBusiness Function ExampleImplementation
Instant<5 minutesFinancial transactionsMulti-AZ failover
Critical5-60 minutesCore databaseAutomated failover
High1-4 hoursApplication servicesBlue-green deployment
Medium4-24 hoursAnalytics systemsManual restore from backup
Standard>24 hoursHistorical archivesRestore on demand

RTO Configuration Example:

yaml
  # Multi-AZ RDS for instant failover (RTO <5 minutes)
  CIADatabase:
    Type: AWS::RDS::DBInstance
    Properties:
      DBInstanceIdentifier: cia-production-db
      Engine: postgres
      EngineVersion: "18.3"
      DBInstanceClass: db.t3.medium
      AllocatedStorage: 100
      StorageType: gp3
      StorageEncrypted: true
      KmsKeyId: !Ref DatabaseEncryptionKey
      
      # Multi-AZ for high availability (automatic failover)
      MultiAZ: true
      
      # Automated backups for point-in-time recovery
      BackupRetentionPeriod: 35
      PreferredBackupWindow: "03:00-04:00"
      
      # Deletion protection
      DeletionProtection: true
      
      Tags:
        - Key: RTO
          Value: Critical-5to60min
        - Key: RPO
          Value: NearRealtime-1to15min
        - Key: BusinessImpact
          Value: VeryHigh
Recovery Point Objective (RPO)

Definition: Maximum acceptable data loss measured in time.

RPO Tiers:

RPO LevelData Loss WindowBusiness Function ExampleBackup Frequency
Zero Loss<1 minuteFinancial recordsSynchronous replication
Near Real-time1-15 minutesCore databaseContinuous backup
Minimal15-60 minutesApplication data15-minute snapshots
Hourly1-4 hoursUser activity logsHourly backups
Daily4-24 hoursAnalytics dataDaily backups
Extended>24 hoursArchived dataWeekly backups

Quarterly Restore Testing

Restore Test Procedure

Objective: Verify backup integrity and validate RTO/RPO targets.

Frequency: Quarterly minimum (ISO 27001 A.17.1.3)

Test Checklist:

  • Select representative backup (full + incrementals)
  • Restore to isolated test environment
  • Verify data integrity (checksums, row counts)
  • Test application functionality against restored data
  • Measure actual recovery time vs RTO target
  • Measure data loss vs RPO target
  • Document results and lessons learned
  • Update recovery procedures if needed

Automated Restore Test Script:

bash
#!/bin/bash
# Quarterly backup restore test
# Tests RTO/RPO compliance and backup integrity

set -euo pipefail

TEST_DATE=$(date +%Y%m%d-%H%M%S)
TEST_REPORT="backup-restore-test-${TEST_DATE}.md"
TEST_INSTANCE="cia-restore-test-${TEST_DATE}"

log() {
  echo "[$(date -u +"%Y-%m-%d %H:%M:%S UTC")] $*" | tee -a "${TEST_REPORT}"
}

# Start restore test
log "# Quarterly Backup Restore Test"
log ""
log "**Test Date**: $(date -u +"%Y-%m-%d %H:%M:%S UTC")"
log "**Tester**: CEO"
log "**Test Instance**: ${TEST_INSTANCE}"
log ""

# Step 1: Identify latest backup
log "## Step 1: Identify Latest Backup"
SNAPSHOT_ID=$(aws rds describe-db-snapshots \
  --db-instance-identifier cia-production-db \
  --query 'DBSnapshots | sort_by(@, &SnapshotCreateTime) | [-1].DBSnapshotIdentifier' \
  --output text)

log "- Latest snapshot: ${SNAPSHOT_ID}"
SNAPSHOT_TIME=$(aws rds describe-db-snapshots \
  --db-snapshot-identifier "${SNAPSHOT_ID}" \
  --query 'DBSnapshots[0].SnapshotCreateTime' \
  --output text)
log "- Snapshot time: ${SNAPSHOT_TIME}"
log ""

# Step 2: Restore snapshot to test instance
log "## Step 2: Restore Database"
START_TIME=$(date +%s)

log "- Initiating restore..."
aws rds restore-db-instance-from-db-snapshot \
  --db-instance-identifier "${TEST_INSTANCE}" \
  --db-snapshot-identifier "${SNAPSHOT_ID}" \
  --db-instance-class db.t3.small \
  --publicly-accessible false \
  --no-multi-az \
  --tags Key=Purpose,Value=RestoreTest Key=TestDate,Value="${TEST_DATE}"

# Wait for instance to be available
log "- Waiting for instance to become available..."
aws rds wait db-instance-available --db-instance-identifier "${TEST_INSTANCE}"

END_TIME=$(date +%s)
RESTORE_DURATION=$((END_TIME - START_TIME))
log "- ✅ Restore completed in ${RESTORE_DURATION} seconds"
log ""

# Step 3: Verify data integrity
log "## Step 3: Data Integrity Verification"

# Get endpoint
DB_ENDPOINT=$(aws rds describe-db-instances \
  --db-instance-identifier "${TEST_INSTANCE}" \
  --query 'DBInstances[0].Endpoint.Address' \
  --output text)

log "- Database endpoint: ${DB_ENDPOINT}"

# Verify row counts
log "- Verifying table row counts..."
psql -h "${DB_ENDPOINT}" -U cia_user -d cia_database -c "\
  SELECT schemaname, tablename, n_live_tup as row_count \
  FROM pg_stat_user_tables \
  ORDER BY n_live_tup DESC \
  LIMIT 10;" | tee -a "${TEST_REPORT}"

# Step 4: Cleanup
log "## Step 4: Cleanup"
log "- Deleting test instance..."
aws rds delete-db-instance \
  --db-instance-identifier "${TEST_INSTANCE}" \
  --skip-final-snapshot \
  --delete-automated-backups

log "- ✅ Test instance cleanup initiated"
log ""

# Summary
log "## Test Summary"
log ""
log "| Metric | Target | Actual | Status |"
log "|--------|--------|--------|--------|"
log "| RTO | <4 hours | $(($RESTORE_DURATION / 60)) minutes | ✅ Pass |"
log "| Data Integrity | 100% | Verified | ✅ Pass |"
log ""

echo "✅ Restore test completed. Report: ${TEST_REPORT}"

Retention Policies

Retention by Classification
ClassificationRetention PeriodRationaleDisposal Method
RESTRICTEDMinimum requiredCompliance, immediate disposal after expirySecure deletion (multi-pass overwrite)
CONFIDENTIAL7 yearsFinancial/legal requirements (Swedish law)Secure deletion with audit trail
INTERNAL3 yearsOperational historyStandard deletion
PUBLICIndefiniteHistorical value, public interestStandard deletion (if needed)
S3 Lifecycle Policy
yaml
  BackupBucket:
    Type: AWS::S3::Bucket
    Properties:
      BucketName: cia-backups
      BucketEncryption:
        ServerSideEncryptionConfiguration:
          - ServerSideEncryptionByDefault:
              SSEAlgorithm: aws:kms
              KMSMasterKeyID: !Ref BackupEncryptionKey
      VersioningConfiguration:
        Status: Enabled
      LifecycleConfiguration:
        Rules:
          # CONFIDENTIAL financial data: 7-year retention
          - Id: ConfidentialFinancialRetention
            Status: Enabled
            Prefix: confidential/financial/
            ExpirationInDays: 2555 # 7 years
            NoncurrentVersionExpirationInDays: 90
            Transitions:
              - TransitionInDays: 90
                StorageClass: STANDARD_IA
              - TransitionInDays: 365
                StorageClass: GLACIER
          
          # INTERNAL data: 3-year retention
          - Id: InternalDataRetention
            Status: Enabled
            Prefix: internal/
            ExpirationInDays: 1095 # 3 years
            NoncurrentVersionExpirationInDays: 30
            Transitions:
              - TransitionInDays: 30
                StorageClass: STANDARD_IA
              - TransitionInDays: 180
                StorageClass: GLACIER
      PublicAccessBlockConfiguration:
        BlockPublicAcls: true
        BlockPublicPolicy: true
        IgnorePublicAcls: true
        RestrictPublicBuckets: true
      Tags:
        - Key: Purpose
          Value: BackupStorage
        - Key: DataClassification
          Value: Mixed

Disaster Recovery Scenarios

Scenario 1: Database Corruption

Trigger: Application detects data integrity issues, corrupted records.

Recovery Procedure:

  1. Immediate Actions (0-15 minutes)

    • Stop application to prevent further corruption
    • Identify corruption scope (affected tables, time range)
    • Notify CEO and initiate incident response
  2. Point-in-Time Recovery (15-60 minutes)

    • Identify last known good state (before corruption)
    • Restore RDS instance to point-in-time
    • Validate data integrity in restored instance
  3. Application Cutover (60-90 minutes)

    • Update application configuration to new database endpoint
    • Restart application services
    • Verify application functionality
  4. Post-Recovery (90+ minutes)

    • Conduct root cause analysis
    • Update monitoring to detect similar issues
    • Document lessons learned

Expected RTO: 2 hours
Expected RPO: <15 minutes (point-in-time recovery)

Show full SKILL.md (421 more words)Show less
Scenario 2: Complete AWS Region Failure

Trigger: AWS region unavailable, all services unreachable.

Recovery Procedure:

  1. Immediate Actions (0-30 minutes)

    • Declare disaster, activate business continuity plan
    • Notify stakeholders (users, CEO, partners)
    • Initiate cross-region recovery
  2. Database Recovery (30-120 minutes)

    • Restore latest cross-region snapshot in alternate region
    • Configure network security groups and access
    • Validate data integrity
  3. Application Deployment (120-180 minutes)

    • Deploy application to alternate region (CloudFormation)
    • Configure DNS cutover to new region
    • Update monitoring and alerting
  4. Validation (180-240 minutes)

    • End-to-end application testing
    • Performance validation
    • User communication and documentation

Expected RTO: 4 hours
Expected RPO: <4 hours (cross-region snapshot lag)

ISO 27001 Control Mapping

A.17.1.2 - Implementing Information Security Continuity

Control Objective: Organization shall establish, document, implement and maintain processes, procedures and controls to ensure the required level of continuity for information security during an adverse situation.

Implementation:

  • ✅ Backup strategies documented by classification
  • ✅ RTO/RPO targets defined and tested
  • ✅ Disaster recovery procedures established
  • ✅ Quarterly restore testing
A.17.1.3 - Verify, Review and Evaluate Information Security Continuity

Control Objective: Organization shall verify established and implemented information security continuity controls at regular intervals.

Implementation:

  • ✅ Quarterly backup restore tests
  • ✅ Automated backup validation
  • ✅ Annual disaster recovery exercise
  • ✅ Continuous monitoring of backup status

NIST Cybersecurity Framework Mapping

PR.IP-4: Backups of information conducted, maintained, tested

  • ✅ Automated backups per classification
  • ✅ Immutable backups (S3 versioning, RDS snapshots)
  • ✅ Quarterly restore testing

RC.RP-1: Recovery plan executed during or after incident

  • ✅ Disaster recovery procedures documented
  • ✅ RTO/RPO targets defined
  • ✅ Recovery scenarios tested

CIS Controls Mapping

CIS Control 11: Data Recovery

  • 11.1: Establish and Maintain Data Recovery Process - ✅ Documented procedures
  • 11.2: Perform Automated Backups - ✅ AWS automated snapshots
  • 11.3: Protect Recovery Data - ✅ Encryption, immutability
  • 11.4: Establish and Maintain Isolated Instance of Recovery Data - ✅ Cross-region backups
  • 11.5: Test Data Recovery - ✅ Quarterly restore tests

Practical Implementation Checklist

For New Systems
  • Classify data per classification framework
  • Define RTO/RPO targets based on business impact
  • Configure automated backups (RDS, S3, EBS)
  • Enable cross-region replication for critical data
  • Set up backup monitoring and alerting
  • Document recovery procedures
  • Schedule first restore test (within 30 days)
For Existing Systems
  • Audit current backup coverage
  • Verify RTO/RPO alignment with business needs
  • Test actual recovery time vs targets
  • Implement missing backups
  • Enable backup encryption
  • Configure lifecycle policies for retention
  • Conduct quarterly restore testing

References

  • ISO 27001:2022 - Annex A.17 Information Security Aspects of Business Continuity Management
  • NIST SP 800-34 - Contingency Planning Guide
  • CIS Controls v8 - Control 11: Data Recovery
  • AWS Well-Architected Framework - Reliability Pillar

© Hack23, Apache-2.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in .github/skills/backup-recovery-policy of Hack23/cia.

Open the folder on GitHubat commit 495fd7d

Compare with similar skills

Backup Recovery Policy next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Backup Recovery Policy compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Backup Recovery Policy this skillHack23/cia239—~4.7kAutomated safety check: PassApache-2.0
OmniRoute Backup and Sync CLIdiegosouzapw/OmniRoute74k—~948Automated safety check: PassMIT
Pymobiledevice3 Device Operatordoronz88/pymobiledevice32.9k—~1.8kAutomated safety check: NotesGPL-3.0
Myclaw BackupLeoYeAI/openclaw-backup659—~1.8kAutomated safety check: PassMIT
OmniRoute Database Backupsdiegosouzapw/OmniRoute74k—~395Automated safety check: PassMIT
Tempsgotempsh/temps828—~2kAutomated safety check: PassApache-2.0

Similar skills

  • OmniRoute Backup and Sync CLI

    diegosouzapw/OmniRoute

    Backup and restore OmniRoute data from the CLI. Trigger incremental snapshots, sync to cloud storage, manage backup schedules, and restore from archive files.

    74k GitHub stars~948 tokensUpdated today
    DevOps & CloudAuto-check passed
  • Pymobiledevice3 Device Operator

    doronz88/pymobiledevice3

    Operate iOS and iPadOS devices with pymobiledevice3, from a local checkout or straight from PyPI via uvx on a fresh workstation.

    2.9k GitHub stars~1.8k tokensUpdated yesterday
    DevOps & CloudAuto-check: notes
  • Myclaw Backup

    LeoYeAI/openclaw-backup

    Backup and restore all OpenClaw configuration, agent memory, skills, and workspace data.

    659 GitHub stars~1.8k tokensUpdated 7 mo ago
    DevOps & CloudAuto-check passed
  • OmniRoute Database Backups

    diegosouzapw/OmniRoute

    Trigger system backups, restore from backup files, and manage the SQLite database lifecycle. Supports export, import, and incremental snapshot strategies.

    74k GitHub stars~395 tokensUpdated today
    DevOps & CloudAuto-check passed
  • Temps

    gotempsh/temps

    Manage, deploy, operate, and instrument applications with Temps.

    828 GitHub stars~2k tokensUpdated today
    DevOps & CloudAuto-check passed
  • Hermes Offsite Backup

    OnlyTerp/hermes-optimization-guide

    Set up encrypted off-machine Hermes backups. An agent skill from OnlyTerp/hermes-optimization-guide.

    687 GitHub stars~772 tokensUpdated 15 days ago
    DevOps & CloudAuto-check passed

More from Hack23/cia

All 78 skills in this repo
  • WCAG 2.1 AA compliance, ARIA attributes, keyboard navigation, screen reader optimization for accessible political data platforms

    239 GitHub stars~2.7k tokensUpdated today
    Auto-check passed
  • Advanced chart types, D3.js/Vaadin Charts patterns, political data visualization, time series analysis

    239 GitHub stars~1.5k tokensUpdated today
    Auto-check passed
  • AI Governance

    Hack23/cia

    AI governance, EU AI Act compliance, OWASP LLM security, responsible AI practices for GitHub Copilot agents

    239 GitHub stars~1.4k tokensUpdated today
    Auto-check passed
  • API Integration

    Hack23/cia

    External API integration patterns, retry logic, circuit breakers, caching, rate limiting for government data APIs

    239 GitHub stars~1.9k tokensUpdated today
    Auto-check passed
  • AWS CloudWatch metrics, alarms, dashboards, log insights, and application monitoring for the CIA platform

    239 GitHub stars~1.9k tokensUpdated today
    Auto-check passed
  • AWS security best practices, VPC security, IAM, KMS, CloudTrail, GuardDuty for CIA platform deployment

    239 GitHub stars~2.3k tokensUpdated today
    Auto-check passed

Categories

Questions about Backup Recovery Policy

What does Backup Recovery Policy do?

Business continuity and disaster recovery: 30-day retention, quarterly restore tests, RTO/RPO targets per ISO 27001 A.17. Backup Recovery Policy is an agent skill from Hack23/cia.

When should I use Backup Recovery Policy?

Backup Recovery Policy fits situations like: tasks that involve Backup and disaster recovery.

How do I install Backup Recovery Policy in Claude Code?

Run `npx skills add Hack23/cia --skill backup-recovery-policy -a claude-code`. Or copy the skill folder (.github/skills/backup-recovery-policy in Hack23/cia) into .claude/skills/backup-recovery-policy in your project. Claude Code loads it when a task matches its description.

How do I install Backup Recovery Policy in Codex?

Run `npx skills add Hack23/cia --skill backup-recovery-policy -a codex`. Or copy the skill folder (.github/skills/backup-recovery-policy in Hack23/cia) into .agents/skills/backup-recovery-policy in your project. Codex loads it when a task matches its description.

Can I use Backup Recovery Policy in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add Hack23/cia --skill backup-recovery-policy -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/backup-recovery-policy, .gemini/skills/backup-recovery-policy, .github/skills/backup-recovery-policy and .opencode/skills/backup-recovery-policy in your project.

What does Backup Recovery Policy need to run?

Going by SKILL.md and its folder, Backup Recovery Policy needs the command-line tools its instructions call (aws and psql).

Does Backup Recovery Policy access the network?

SKILL.md names 1 domain. As links in the text: github.com. This is read from the text; nothing was executed.

Is Backup Recovery Policy safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Backup Recovery Policy use?

Backup Recovery Policy is published under the Apache-2.0 licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Backup Recovery Policy use?

About 4.7k tokens (SKILL.md is roughly 19k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Backup Recovery Policy?

Skills that share tags, products or a category with Backup Recovery Policy: OmniRoute Backup and Sync CLI (diegosouzapw/OmniRoute, 74k stars), Pymobiledevice3 Device Operator (doronz88/pymobiledevice3, 2.9k stars), Myclaw Backup (LeoYeAI/openclaw-backup, 659 stars) and OmniRoute Database Backups (diegosouzapw/OmniRoute, 74k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Backup Recovery Policy?

Hack23 (a GitHub organization) maintains it in Hack23/cia, which has 239 GitHub stars. The repository holds 78 skills in this directory. The repository was last updated on October 9, 2026.

Source: Hack23/cia on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.