From version-guard
Verify and enforce use of the latest stable library/package versions using live documentation lookups instead of training-data knowledge. Use PROACTIVELY whenever: (1) Recommending or selecting a library, framework, or package version, (2) Adding dependencies to any project (package.json, pyproject.toml, requirements.txt, Cargo.toml, go.mod, Gemfile, pom.xml, build.gradle, composer.json, etc.), (3) A user asks "what version of X should I use?" or similar version questions, (4) Writing code examples that import or configure version-sensitive libraries, (5) Suggesting install commands (npm install, pip install, cargo add, go get, etc.), (6) Upgrading or auditing existing dependencies.
How this skill is triggered — by the user, by Claude, or both
Slash command
/version-guard:version-guardThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
You are a version-aware assistant. Before recommending any library version, you MUST verify
You are a version-aware assistant. Before recommending any library version, you MUST verify the current stable release against live documentation. Never trust training-data version knowledge.
Trigger automatically when you detect any of these contexts:
npm install, pip install, cargo add, go get, etc.)The context7 MCP tools are deferred. Load them first:
ToolSearch query: "+context7"
This loads mcp__context7__resolve-library-id and mcp__context7__query-docs.
mcp__context7__resolve-library-id
libraryName: "<package-name>"
query: "latest version installation"
Select the result with the highest relevance and documentation coverage.
mcp__context7__query-docs
libraryId: "<resolved-id>"
query: "latest version installation getting started"
Extract:
"Using <library> v<latest> (verified current — training data may reference v<old>)"When upgrading from an older version:
If context7 cannot resolve the library:
"<library> latest version <current-year>""Per <source>, latest stable is v<X>"For dependency file formats and context7 naming conventions across all major ecosystems, see ../../references/ecosystem-patterns.md.
npx claudepluginhub zircote-plugins/version-guardVerifies version-sensitive facts (APIs, versions, pricing, model IDs, CLI flags, config) against current sources instead of training data. Activates on any question about dates, versions, deprecations, or latest recommendations.
Fetches current official docs before writing framework-specific code to prevent deprecated API usage. Activates on dependency changes or framework work.
Verifies version-sensitive and time-changing facts (APIs, configs, CLI flags, pricing, model IDs) against installed environment and current docs before relying on training memory.