Prioritize primeintellect envs and add freshness/CI/version criteria to browse-environments skill

[willccbb]

Motivation

• Improve discovery quality by preferring official primeintellect environments as the first-pass results.
• Emphasize actionable signals (CI/actions, recency, and explicit version) to avoid stale or broken environments.
• Make the shortlist selection more deterministic for downstream evals, installs, and migrations.

Description

• Update skills/browse-environments/SKILL.md to change the primary prime env list example to include --owner primeintellect by default.
• Add explicit shortlist filtering guidance to prefer primeintellect-published environments with passing latest actions/CI, updated within ~2 months, and on version v0.1.8 or newer.
• Move and expand the inspect/pull steps and add a Recency line to the candidate comparison checklist.

Testing

• Ran uv run pre-commit install which completed successfully.
• Ran uv run pre-commit run --all-files which passed all configured checks.
• Ran uv run pytest tests/ -q --maxfail=1 which reported a failure in tests/test_envs.py::test_env[gsm8k] attributable to an environment/API evaluation issue unrelated to this docs-only change.

---

Codex Task

---

Note

Low Risk
Docs-only changes that adjust recommended CLI usage and evaluation criteria; no runtime or security-sensitive code paths are modified.

Overview
Updates skills/browse-environments/SKILL.md to prioritize official primeintellect environments in the primary prime env list example and to make the discovery workflow more deterministic.

Adds explicit shortlisting guidance to filter by passing latest actions/CI, recent updates (~2 months), and minimum version (v0.1.8+), and expands the comparison checklist with an explicit recency signal while renumbering the inspect/pull steps accordingly.

^{Written by Cursor Bugbot for commit 518a766. This will update automatically on new commits. Configure here.}