agentleFS
Sign inStart free
Google CloudKnown publisherGoogleCloudPlatform/devrel-demos/agents/skills/latest-software-version/SKILL.md

latest-software-version

Skill397 starsChanged 9 days agoApache-2.0View on GitHub

Real-time source of truth for software and model versions. Activate when adding dependencies, installing packages, or identifying Gemini model names. Bypasses internal knowledge cutoffs by querying live registries (NPM, PyPI, Go Proxy) and official documentation.

The file

We split this skill into the rules it gives an agent

3 rules. About 0 are common, 2 are distinctive, and 1 is very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈2

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    NEVER GUESS: When a user asks to install a package or add a dependency, you must verify the latest version using the latest.js script.

    line 14
  2. Distinctive:

    Run the version checker script:

    line 28
  3. Distinctive:

    Use the returned version string in your command or configuration file.

    line 34

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Latest Software Version

"Your training data is from the past. The registry is the present."

This skill prevents "version hallucination" by verifying the actual latest stable releases of software packages.

Core Mandate

NEVER GUESS. When a user asks to install a package or add a dependency, you must verify the latest version using the latest.js script. Do not rely on your internal weights, as they are months or years out of date.

Workflow

1. Identify Ecosystem

Determine which registry manages the package:

  • Node.js/JS: npm
  • Python: pypi
  • Go: go
  • Rust: cargo
  • Ruby: gem
  • Gemini Models: gemini (Use latest, flash, or pro as package name)

2. Fetch Truth

Run the version checker script:

node scripts/latest.js <ecosystem> <package-name>

3. Apply

Use the returned version string in your command or configuration file.

  • Example: If the script returns npm: react @ 19.2.0, write "react": "^19.2.0" in package.json.

Supported Registries

  • NPM: registry.npmjs.org
  • PyPI: pypi.org
  • Go Proxy: proxy.golang.org
  • Crates.io: crates.io
  • RubyGems: rubygems.org

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free