agentleFS
yogsoth-aiyogsoth-ai/convergence/skills/criteria-interrogation/SKILL.md

criteria-interrogation

Skill2 starsChanged 6 months agoApache-2.0View on GitHub

Challenge the evaluation criteria themselves using Assumption-based Planning, Critical Systems Heuristics, and Boundary Critique to ensure the framework is sound.

The file

We split this skill into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈6

    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:

    When criteria were inherited rather than deliberately designed

    line 12
  2. Distinctive:

    When different criteria would produce different winners

    line 13
  3. Distinctive:

    When stakeholders disagree about what matters

    line 14
  4. Distinctive:

    When the evaluation framework has not been challenged

    line 15
  5. Distinctive:

    Test conclusion sensitivity: would different weights change the winner?

    line 55
  6. Distinctive:

    If winner changes under reasonable alternative weighting, verdict is REWEIGHT

    line 56

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

Criteria Interrogation

Purpose: Question whether the evaluation framework used during convergence was itself valid — exposing hidden biases in criteria selection, weighting, and boundary definitions that may have predetermined the outcome.

When to use:

  • When criteria were inherited rather than deliberately designed
  • When different criteria would produce different winners
  • When stakeholders disagree about what matters
  • When the evaluation framework has not been challenged

Budget

MetricMinimum
Criteria challengedAll criteria used in convergence
Alternative framings>= 2 alternative criteria sets
Boundary questions>= 5 (who benefits, who is excluded)

State Ledger

criteria_under_review: []
challenges_raised: {}
alternative_framings: []
sensitivity_to_criteria_change: {}
verdict: null  # CRITERIA_SOUND | CRITERIA_BIASED | REWEIGHT

Available Tactics

TacticWhen to Deploy
assumption-excavationDefault — treat criteria as assumptions to challenge
multi-perspective-attackWhen criteria privilege certain stakeholders

Available SOPs

  • assumption-extraction — surface assumptions embedded in criteria
  • assumption-challenge — challenge each criterion's validity
  • conclusion-sensitivity — test if outcome changes with different criteria
  • perspective-assignment — assign stakeholder perspectives to criteria
  • perspective-attack — attack criteria from each perspective

Execution Guidance

  1. List all criteria used in convergence with their weights
  2. For each criterion, apply assumption-extraction (why this criterion?)
  3. Challenge each criterion's inclusion, exclusion, and weight
  4. Test conclusion sensitivity: would different weights change the winner?
  5. If winner changes under reasonable alternative weighting, verdict is REWEIGHT

Output Format

strategy: criteria-interrogation
criteria_reviewed: <count>
challenges:
  - criterion: <name>
    challenge: <argument>
    severity: HIGH | MEDIUM | LOW
    alternative: <proposed change>
sensitivity_result: ROBUST | FRAGILE
verdict: CRITERIA_SOUND | CRITERIA_BIASED | REWEIGHT
recommended_changes: []

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.