RecoveryAudit
Rehearse Beads recovery and drift handling. USE WHEN backup, restore, pull or push, lock cleanup, or mode-transition safety should be audited before trusting Beads operationally.From its SKILL.md
npx -y skills add mj-deving/pai-skills --skill RecoveryAuditAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
2 things to look at
- no licenseNo license file was found in the repository. Code published without one is not open source by default, so using it at work is a question for whoever answers licensing questions where you are.
- 0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
SKILL.md
1.1 KB, 207 tokens by cl100k_base, as published. Nobody here has run it
Beads Recovery Audit
Use this skill when the repo already works well enough on the happy path, but you do not yet trust failure handling.
Outcome rule:
- prefer rehearsal on disposable clones or test repos
- make pass or fail explicit
- leave a short runbook, not hand-wavy reassurance
Quick start
- Run:
${PAI_EXTENSIONS_DIR}/skills/Beads/RecoveryAudit/scripts/recovery_probe.sh
- Read references/recovery-drill.md.
- Turn the findings into a pass/fail report plus next actions.
Audit areas
- current repo state capture
- Dolt remote visibility
- backup and restore path
- pull/push behavior
- lock or lingering-process symptoms
- hook posture where relevant
- embedded-versus-server assumptions
Rule
Do not claim recovery is good because bd ready works once. Recovery readiness means the drill is understood and repeatable.
What ships with it: 3 files
1.9 KB alongside SKILL.md, 1 of them executable
agents/
- openai.yaml296 B
references/
- recovery-drill.md1.1 KB
scripts/
- recovery_probe.shruns584 B