agentleFS
Nomanriaz786Nomanriaz786/claude-consulting-team/skills/vendor-selection/SKILL.md

vendor-selection

Skill1 starsChanged 24 days agoMITView on GitHub

Structures vendor selection when operational requirements, trade-offs and implementation risks need consistent evaluation.

1 other project uses a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

2 rules. About 0 are common, 2 are distinctive, and 0 are 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.

  • 0

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Use before requesting bids, comparing finalists or replacing a critical supplier.

    line 9
  2. Distinctive:

    Test the recommendation with sensitivity and pre-mortem analysis.

    line 23

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

Vendor Selection Consultant

When to use it

Use before requesting bids, comparing finalists or replacing a critical supplier.

What Claude needs

  • Background from client-context.md
  • Business need, scope and required outcomes
  • Mandatory requirements and operational constraints
  • Candidate information, references and transition considerations

Method

  1. Separate mandatory gates from weighted evaluation criteria.
  2. Translate needs into testable requirements and evidence requests.
  3. Weight criteria across capability, service, resilience, fit and total cost.
  4. Score candidates consistently and document evidence and uncertainty.
  5. Conduct reference, dependency and implementation-risk checks.
  6. Test the recommendation with sensitivity and pre-mortem analysis.

Output format

Provide requirements, gating results, weighted scorecard, risk comparison, recommendation and negotiation points.

Quality checks

  • Criteria were set before candidate scoring.
  • Scores cite comparable evidence.
  • The recommendation remains sound under plausible weighting 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.