agentleFS
yogsoth-aiyogsoth-ai/convergence/skills/consistency-audit-loop/SKILL.md

consistency-audit-loop

Skill2 starsChanged 6 months agoApache-2.0View on GitHub

Detect preference cycles, localize inconsistent judgments, request corrections, and recompute ratings until consistency threshold is met.

The file

We split this skill into the rules it gives an agent

4 rules. About 0 are common, 4 are distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈4

    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:

    Run detection first — if no cycles and CR < 0.1, exit immediately (no repair needed)

    line 30
  2. Distinctive:

    When re-comparing, provide the judge with context: "A>B and B>C but you said C>A — please reconsider"

    line 32
  3. Distinctive:

    After repair, recompute full ratings before next detection pass

    line 34
  4. Distinctive:

    Document all changes in repair log for transparency

    line 36

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

Consistency Audit Loop

Audit a comparison matrix for transitivity violations, pinpoint the most problematic judgments, request re-evaluation of those pairs, and recompute until the consistency threshold is satisfied.

Stages

  1. Detect — cycle-detection scans the comparison matrix for cycles and computes transitivity score
  2. Localize — inconsistency-localization identifies which pairs participate in the most cycles
  3. Repair — comparison-executor re-evaluates the problematic pairs with explicit context about the inconsistency

Loop stages 1-3 until consistency threshold met or repair budget exhausted.

Available SOPs

StageSOPInputOutput
Detectcycle-detectioncomparison_matrixcycles[], transitivity_score
Localizeinconsistency-localizationcomparison_matrix, cycles[]problematic_pairs[]
Repaircomparison-executorpair, contextjudgment

Execution Guidance

  • Run detection first — if no cycles and CR < 0.1, exit immediately (no repair needed)
  • Localization should rank pairs by cycle participation count
  • When re-comparing, provide the judge with context: "A>B and B>C but you said C>A — please reconsider"
  • Limit repairs to top 20% most problematic pairs per iteration
  • After repair, recompute full ratings before next detection pass
  • Maximum 3 audit iterations to prevent infinite loops
  • Document all changes in repair log for transparency

Minimum Yield

  • Consistency report + correction recommendations
  • Consistency report: CR value, transitivity score, cycle count
  • List of all cycles found (before and after repair)
  • Repair log: which pairs were re-evaluated, old vs new judgment
  • Final consistency status: pass/fail with metrics

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.