agentsclimarketplace
Sign in

Research software versions

Skill ImYourBoyRoy/agent-continuity-stack/skills/research-software-versions

Research the appropriate stable version of one software component before installation or migration. Use for compatibility, deprecation, and migration evidence; remain read-only and project-constrained.From its SKILL.md

Install
npx -y skills add ImYourBoyRoy/agent-continuity-stack --skill research-software-versions

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

  • 17 days oldThe repository was created 17 days ago. New is not bad, but a brand new repository carrying a familiar-sounding name is the shape a typosquat arrives in, and there has been no time for anyone else to find a problem with it.
  • 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

2.3 KB, 382 tokens by cl100k_base, as published. Nobody here has run it

Research Software Versions

Recommend the latest appropriate stable version, not simply the highest number.

Establish the compatibility envelope

Inspect:

  • manifests and lockfiles
  • runtime and toolchain files
  • engine and platform constraints
  • CI and deployment matrices
  • transitive requirements and native dependencies
  • existing compatibility decisions
  • repository-specific validation restrictions

Identify the currently declared, resolved, installed, and deployed states. Treat them as distinct.

Research authoritatively

Use current sources in this order where available:

  1. security and support policy
  2. first-party registry or release index
  3. official documentation and migration guide
  4. official changelog and release notes
  5. upstream repository release or tag

Read references/source-policy.md for projects without conventional releases. Do not infer stability from a default branch or download badge.

Evaluate:

  • runtime and operating-system requirements
  • removed or renamed APIs and flags
  • feature and default changes
  • transitive and lockfile impact
  • deployment-platform compatibility
  • maintenance status and release age
  • known regressions or security advisories

Do not introduce prereleases unless explicitly requested and justified.

Recommend

State:

  • current declared and resolved version
  • latest stable available
  • latest compatible under current constraints
  • recommended version
  • why newer or older candidates were rejected
  • required migration
  • verification path and rollback
  • authoritative sources and date checked

Required upgrades, security response, routine maintenance, and optional enhancements must remain separate. Do not apply unrelated upgrades without approval.

Define verification

Define the project's approved build, test, or deployment evidence for the later implementation. Preserve lockfile reproducibility in the recommendation. Do not claim proven project compatibility from documentation alone. Stop before editing files or running mutating update commands; hand an authorized selection to apply-project-updates.

What ships with it: 3 files

1.6 KB alongside SKILL.md

agents/

references/

Keep looking

Skills are one crate of 326,629. 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.