provisioning-configuration-and-disaster-recovery-expert

Audit provisioning, CI/CD, Azure configuration, secrets, and disaster recovery readiness.

Updated Dec 20, 2025
One-click install
npx skills add https://github.com/koala-man-64/helpful-scripts --skill provisioning-configuration-and-disaster-recovery-expert-koala-man-64
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: provisioning-configuration-and-disaster-recovery-expert
Source: https://github.com/koala-man-64/helpful-scripts/tree/main/exports/codex-skills/repo-local/provisioning-configuration-and-disaster-recovery-expert
Command: npx skills add https://github.com/koala-man-64/helpful-scripts --skill provisioning-configuration-and-disaster-recovery-expert-koala-man-64

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Projects often depend on undocumented manual setup, hidden cloud state, long-lived credentials, and untested backups, making them impossible to rebuild or recover after a failure. This Skill systematically audits whether a repository can be provisioned, deployed, and recovered from disaster using versioned automation and documented procedures. ## Core Features & Use Cases - Eight-Pass Audit Workflow: Inventories repository provisioning, maps GitHub and Azure configuration, audits secrets and identities, analyzes deployment bootstrap order, detects drift, simulates disaster scenarios, and produces a ranked risk report. - Evidence-Based Findings: Classifies every statement as Confirmed, Inferred, or Unknown, with concrete file paths, resource names, and workflow references, and never prints raw secret values. - Structured Recovery Report: Produces a recovery readiness rating, external configuration inventory, bootstrap-from-scratch runbook, recovery runbook, and prioritized remediation roadmap. - Use Case: Before handing a project to a new team, run this Skill to discover that production deployment depends on a manually created service principal, an undocumented GitHub environment secret, and a database with no tested restore path, then get a step-by-step remediation plan. ## Quick Start Use the provisioning-configuration-and-disaster-recovery-expert skill to audit whether this repository can be provisioned, deployed, and recovered from disaster.

Frequently Asked Questions about provisioning-configuration-and-disaster-recovery-expert

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I audit whether my project can be recovered from a disaster?▼

Run a disaster recovery audit that inventories secrets, cloud resources, and deployment pipelines, then simulates failures like deleted resource groups, corrupted databases, or expired credentials. This Skill produces a recovery readiness rating and a step-by-step recovery runbook.

How to check if GitHub Actions secrets and environments are configured correctly?▼

Map each workflow to the repository secrets, environment variables, protection rules, and OIDC settings it requires, then flag missing, unused, or overbroad entries. The audit also identifies where long-lived secrets should be replaced with GitHub OIDC or federated credentials.

Does this audit make changes to my Azure or GitHub configuration?▼

No, inspection is read-only by default and never rotates, deletes, or reconfigures secrets, cloud resources, DNS, or identities. Live changes only happen after you explicitly approve an incremental, reversible plan with rollback steps.

Can it detect drift between Terraform or Bicep and actual Azure resources?▼

Yes, the drift analysis pass compares IaC definitions against actual or documented Azure state to find resources not represented in code, missing deployments, and manual portal-only settings. Resources that cannot be recreated from version control are flagged as recovery gaps.

What are the limitations when there is no live Azure or GitHub access?▼

Without cloud or repository access, the audit runs repository-only and marks GitHub and Azure state findings with reduced confidence. It lists the exact checks that must be run later and classifies those conclusions as Inferred or Unknown.