菜单
Evaluates whether PostgreSQL backup posture is actually recoverable in practice. Use when: the user asks if recovery is realistic, RPO/RTO readiness needs review, restore evidence is unclear, or backup status alone is not enough for confidence.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Produces a weekly CISO management briefing as a Marp-compatible Markdown presentation. Use when: weekly cybersecurity notes, KPI/KRI data, incidents, vulnerabilities, threat intelligence, regulatory updates, or management decision needs must become an executive-ready cyber risk and security management brief.
Operating protocol for a Crux project. Use when: an agent or IDE needs to understand Crux layout, locate framework-home definitions, locate project `.crux` state, route work to the right agent, run onboarding, manage task continuity, or decide which files are read-only versus writable.
Enforces a disciplined implementation posture before coding or broad refactors: surface assumptions, narrow scope, prefer the simplest complete fix, define verification targets, and avoid speculative cleanup. Use when: a developer agent is about to implement, refactor, review, or change non-trivial code and there is meaningful ambiguity, risk, or temptation to over-engineer.
Analyses a live Kubernetes cluster and produces .crux/docs/kubernetes.md and .crux/summaries/kubernetes.md. Read-only — does not modify any cluster resources. Use when: (1) .crux/docs/kubernetes.md is missing during onboarding, (2) user requests an architecture review, (3) cluster configuration has significantly changed.
Audits all cluster namespaces against tenant naming conventions defined in decisions/tenant-naming-conventions.md. Checks label compliance, missing resource quotas, and naming pattern violations. Use when: naming convention question, pre-release namespace review, SOC Type 2 audit, or periodic drift check.
Applies or updates Kubernetes NetworkPolicy resources for a target namespace. Supports standard policy templates (deny-all-ingress, allow-same-namespace, allow-ingress-controller, allow-monitoring) and custom policies from user input. Requires explicit user approval before applying any change. Use when: hardening a namespace, onboarding a new tenant, policy drift repair.
| name | postgresql-recovery-readiness-review |
| description | Evaluates whether PostgreSQL backup posture is actually recoverable in practice. Use when: the user asks if recovery is realistic, RPO/RTO readiness needs review, restore evidence is unclear, or backup status alone is not enough for confidence. |
| license | MIT |
| compatibility | opencode |
| metadata | {"owner":"postgresql-admin","type":"read-only","approval":"No"} |
Owner: postgresql-admin
Type: read-only
Approval: No
Turns backup and restore evidence into a practical PostgreSQL recovery-readiness judgment.
Requires already loaded:
.crux/workspace/postgresql-admin/MEMORY.md
Loads during execution (lazy):
.crux/docs/postgresql-backup-recovery-baseline.md
(generate from agent assets first if missing)
| Input | Source | Required |
|---|---|---|
target-host | user / MEMORY.md | Yes |
backup-context | MEMORY.md / user | No |
1. Review available backup and WAL evidence
2. Review restore path and test evidence if any
3. Assess recovery confidence against known expectations
4. Return practical readiness summary and gaps
5. Skill complete — unload
Inline markdown summary.
| Condition | Action |
|---|---|
| Restore evidence absent | mark readiness as unproven |
| Inputs are partial | state confidence accordingly |
| Unexpected failure | Stop. Write error to bus. Notify user. |