agentsclimarketplace
Sign in

VersionAudit

Skill mj-deving/pai-skills/skills/Beads/VersionAudit

Audit a repo's live Beads posture before migration or coordination work. USE WHEN verify backend mode, remotes, hooks, legacy drift, or whether a repo is safe to upgrade, share, or recover.From its SKILL.md

Install
npx -y skills add mj-deving/pai-skills --skill VersionAudit

Assembled 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.5 KB, 295 tokens by cl100k_base, as published. Nobody here has run it

Beads Version Audit

Use this skill before bootstrap, migration, server-mode decisions, or recovery planning.

Outcome rule:

  • produce a mechanical audit first
  • then explain the operational meaning
  • point to the smallest justified remediation path

Quick start

Run:

${PAI_EXTENSIONS_DIR}/skills/Beads/VersionAudit/scripts/audit_beads_env.sh
bd version
bd context --json || true
bd bootstrap --dry-run || true
bd config drift --json || true

Then use references/remediation-matrix.md to interpret the result.

What to check

  • bd is installed and responds
  • the repo has .beads/ state
  • current ready output is readable
  • Dolt remotes exist or do not exist by design
  • bd bootstrap --dry-run would adopt existing remote state rather than minting a shadow database
  • Claude hook posture is healthy when relevant
  • legacy JSONL or other historical markers are still present
  • lock/process anomalies are visible

Report shape

Keep the result compact:

  • current posture
  • drift or risk found
  • immediate remediation
  • what not to change yet

Escalation rule

If the audit shows real uncertainty about current architecture, route the user to beads-research and cite the current README/docs before making migration claims.

What ships with it: 3 files

3.7 KB alongside SKILL.md, 1 of them executable

agents/

references/

scripts/

Keep looking

Skills are one crate of 326,790. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.