agentleFS
yogsoth-aiyogsoth-ai/convergence/skills/best-option-selection/SKILL.md

best-option-selection

Skill2 starsChanged 6 months agoApache-2.0View on GitHub

Select the single best candidate from a set using WSM, TOPSIS, AHP, MAUT, or VIKOR methods.

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:

    If user questions the result, switch methods, recompute, and compare

    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

Best-Option Selection

Purpose: Select the single best-performing alternative from a candidate set, supporting WSM, TOPSIS, AHP, MAUT, VIKOR, and other methods.

When to use:

  • User needs to select "the best one" from multiple candidates
  • Decision scenario allows compensatory trade-offs (high scores offset low scores)
  • Moderate number of candidates (3-15)

Budget

Base SOPTarget±10% Range
criterion-definition5-8 criteria4-9
weight-elicitation-sop1 weight vector1
alternative-scoring1 score matrix1
normalization1 normalized matrix1
scoring-synthesis1 recommendation1

State Ledger

strategy: best-option-selection
status: pending
criteria_defined: false
weights_computed: false
scores_computed: false
normalized: false
synthesized: false
selected_method: null
result: null

Available Tactics

  • scoring-matrix-construction — Standard workflow: define criteria → assign weights → score → aggregate → sensitivity

Available SOPs

Import (from scoring-matrix-construction)

  • criterion-definition
  • weight-elicitation-sop
  • alternative-scoring
  • normalization

Subagent

  • scoring-synthesis

Execution Guidance

  1. Invoke scoring-matrix-construction tactic to build the score matrix
  2. Select aggregation method based on problem characteristics (WSM for simple scenarios, TOPSIS when ideal solution reference is needed, VIKOR when compromise solution is needed)
  3. Invoke scoring-synthesis to produce final recommendation
  4. If user questions the result, switch methods, recompute, and compare

Output Format

## Best Option Recommendation

**Recommended:** [Alternative name]
**Overall Score:** [Score value]
**Method Used:** [WSM/TOPSIS/AHP/MAUT/VIKOR]

### Score Ranking
| Rank | Alternative | Overall Score | Key Strengths |
|------|-------------|---------------|---------------|

### Sensitivity Notes
[Impact of weight changes on the result]

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.