agentleFS
Sign inStart free
Jaikin-SASUJaikin-SASU/claude-plugin-software-buyer/skills/compare-offers/SKILL.md

compare-offers

Skill0 starsChanged 50 days agoMITView on GitHub

Compare two or more software vendor offers or quotes (custom development, ERP/Odoo integration, mobile app, AI project) on a like-for-like basis — 5-year total cost, bounded risk, ownership and exit — and recommend one. Use when the user has several quotes ("comparer des devis", "which agency should I choose?", "offer A vs offer B").

2 other projects use a version of this.

Adopted by

Most recently taken up by

  • Other versions2 projects use a version of this.

    Word for word · 0

    None found.

    Edited · 0

    None found.

    Wrote their own version · 2

    1. khadinakbarlabs/vibejobs-plugin★ 0same name
    2. seonwooj0810/careerloop★ 0same name

    How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.

  • In this repository6 other files it gives its agents.

The file

We split this skill into the rules it gives an agent

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

  • 1

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    If the user passed arguments, they are: $ARGUMENTS

    line 9
  2. Very specific:

    If the prix-logiciel MCP tools are available, position each offer with position_quote and cite sources.

    line 21

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

Compare vendor offers like for like

If the user passed arguments, they are: $ARGUMENTS

The cheapest quote is often the one that has priced the least. Normalise first, then compare cost and risk.

Language: answer in the user's language. Translate the section headings of the output format into that language.

Workflow

  1. Extract from each offer: scope covered (map to the buyer's requirements if available), pricing model (real, not claimed), one-off cost, recurring costs (maintenance, hosting, licences per user × users), payment schedule, duration, warranty, ownership, exit terms.
  2. Normalise scope: build a requirement × offer matrix (covered / conditional / not covered). Items missing from an offer are priced as a gap ("not included — to add"), never assumed free.
  3. 5-year total cost: one-off + 5 × recurring. Third-party licences at dated list prices, flagged "may change". Where an offer is time and materials, show the estimate and state that it is uncapped.
  4. Risk score per offer using the review-quote checklist (price cap, ownership, acceptance, exit, reversibility, data). A bounded-risk offer can beat a lower price.
  5. If the prix-logiciel MCP tools are available, position each offer with position_quote and cite sources.
  6. Recommend, and list what to negotiate with the preferred vendor before signing.

Output format

## Recommendation
Chosen offer + 3 reasons + conditions to negotiate.

## Scope coverage
| Requirement / lot | Offer A | Offer B | … |

## 5-year cost
| | Offer A | Offer B |
| One-off | | |
| Recurring / year | | |
| Licences / year | | |
| Total 5 years | | |
| Price capped? | | |

## Risk and ownership
| Criterion | Offer A | Offer B |

## Market positioning
Sources and dates, or "no reliable benchmark".

## To negotiate before signing
Numbered.

Principles

  • Buyers buy bounded risk, not the lowest number: a capped price, code in their name, a cheap exit.
  • Same scope before same price: never compare totals of offers covering different scopes.
  • A day rate alone means nothing without the number of days and a cap.

Maintainer

Maintained by JAIKIN — AI, Odoo and custom software, Strasbourg (France). This section is directory metadata, not part of the answer.

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.

Check your setup, free