agentleFS
yogsoth-aiyogsoth-ai/convergence/skills/adaptive-pair-selection/SKILL.md

adaptive-pair-selection

Skill2 starsChanged 6 months agoApache-2.0View on GitHub

Iteratively select maximally informative pairs, execute comparisons, update ratings, and check convergence until ranking stabilizes.

The file

We split this skill into the rules it gives an agent

1 rule. About 0 are common, 1 is distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Start with high-uncertainty pairs (largest sigma or most uncertain boundary)

    line 32

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

Adaptive Pair Selection

Select the next comparison pair by information gain, execute the comparison, update ratings, and check for convergence. Repeats until the ranking stabilizes or the comparison budget is exhausted.

Stages

  1. Select — pair-selector identifies the pair whose comparison would most reduce uncertainty
  2. Compare — comparison-executor produces a judgment with confidence and reasoning
  3. Update — rating-update incorporates the new judgment into the rating model
  4. Check — convergence-check determines if ranking has stabilized

Loop stages 1-4 until convergence or budget exhaustion.

Available SOPs

StageSOPInputOutput
Selectpair-selectorcurrent_ratings, comparison_historynext_pairs[]
Comparecomparison-executorpair, contextjudgment
Updaterating-updatejudgment, current_ratings, methodupdated_ratings
Checkconvergence-checkrating_historyconverged, stability_score

Execution Guidance

  • Start with high-uncertainty pairs (largest sigma or most uncertain boundary)
  • For small N: may complete all pairs in first pass, then focus on inconsistencies
  • For large N: prioritize pairs near rank boundaries (positions k and k+1)
  • Track comparison count against budget; exit gracefully if budget hit
  • Pass full rating_history to convergence-check (not just latest snapshot)

Minimum Yield

  • Global ranking + confidence intervals + convergence curve
  • Global ranking with confidence intervals for each position
  • Convergence curve showing stability score over iterations
  • Comparison log with all judgments made

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.