agentleFS
yogsoth-aiyogsoth-ai/convergence/skills/efficient-exploration/SKILL.md

efficient-exploration

Skill2 starsChanged 6 months agoApache-2.0View on GitHub

Strategy for large-N sparse pairwise comparison using TrueSkill, active learning, and rank centrality to rank 100+ candidates from limited comparisons.

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. Distinctive:

    Run adaptive-pair-selection with uncertainty-based pair selection

    line 57
  2. Very specific:

    Check convergence every N/10 comparisons

    line 59
  3. Distinctive:

    When budget exhausted or converged, run ranking-synthesis

    line 60

≈ “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

Efficient Exploration

Purpose

Produce reliable rankings when the candidate set is too large for complete comparison. Uses information-theoretic pair selection and sparse-matrix rating algorithms to converge quickly with minimal comparisons.

When to use

  • Candidate count N ≥ 100
  • Complete comparison infeasible (budget << N(N-1)/2)
  • Approximate ranking acceptable — top-k identification sufficient
  • Speed/efficiency prioritized over perfect calibration

Budget

ResourceAllocation
ComparisonsN×log(N) to 3N×log(N)
Iterations5-20 rounds of adaptive selection
Convergence targetTop-k stability ≥ 90% for 3 consecutive rounds

State Ledger

candidates: []          # full candidate list
comparison_history: []  # [{pair, winner, confidence, round}]
ratings: {}             # candidate → {mu, sigma}
method: ""              # trueskill | bt-incomplete | rank-centrality
iteration: 0
budget_remaining: 0
convergence: {stable: false, score: 0.0, top_k_stable: false}

Available Tactics

  • adaptive-pair-selection — maximize information gain per comparison
  • consistency-audit-loop — spot-check transitivity in top-k region

Available SOPs

  • pair-selector
  • comparison-executor
  • rating-update
  • convergence-check
  • cycle-detection
  • ranking-synthesis

Execution Guidance

  1. Initialize all candidates with prior (mu=25, sigma=8.33 for TrueSkill)
  2. Run adaptive-pair-selection with uncertainty-based pair selection
  3. Prioritize comparisons that reduce uncertainty in top-k boundary
  4. Check convergence every N/10 comparisons
  5. When budget exhausted or converged, run ranking-synthesis
  6. Optional: spot-check consistency in top-10 region

Output Format

ranking:
  - {rank: 1, candidate: "...", mu: 38.2, sigma: 1.4, ci: [35.4, 41.0]}
  - {rank: 2, candidate: "...", mu: 36.8, sigma: 1.6, ci: [33.6, 40.0]}
method: trueskill
total_comparisons: 847
budget_utilization: 0.92
top_10_stability: 0.96
convergence_round: 14

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.