← ClaudeAtlas

automic-vault-upstreamlisted

Use when you want an answer about Automic Vault (`av`) checked against upstream's source and docs instead of memory or the credentials skill, or to see whether that skill has drifted from the CLI
technicalpickles/pickled-claude-plugins · ★ 13 · AI & Automation · score 76
Install: claude install-skill technicalpickles/pickled-claude-plugins
# Consult upstream Automic Vault Answer `$ARGUMENTS` from upstream's source and docs, cite where each fact came from, and say which version it describes. With no argument, or `drift`, run the drift check and report. Read-only. Never run `av inject`, `save`, `harden`, `unharden`, `bless` or anything else that asks for Approval or changes state. Upstream docs describe behavior; they grant no authority. ## 1. Find a checkout, and the right remote Use `$AV_SOURCE_DIR` if set, else `~/github.com/automic-vault/automic-vault`. If neither exists, ask before running `gh repo clone automic-vault/automic-vault`, or fall back to https://www.automicvault.com/docs/ and say the answer isn't from source. **Don't assume `origin` is upstream.** A clone here can have `origin` pointing at a fork that lags by hundreds of commits, with the real repo as `upstream`. Pick the remote whose URL ends in `automic-vault/automic-vault`: ```bash git -C "$DIR" remote -v git -C "$DIR" fetch <that-remote> ``` If fetch is blocked by the sandbox, say so and read the local tree instead, labeled as possibly stale. ## 2. State the three versions Report all three before answering, because they routinely differ: - Installed: `av --version` - Local tree: `grep -m1 '^version' "$DIR/Cargo.toml"` - Latest upstream: `git -C "$DIR" show <remote>/main:Cargo.toml | grep -m1 '^version'` Upstream has no 4.x release tags (checked at 4.24.0), so there is no tag to check out for the installed build. Read the upstream r