agentsclimarketplace

Vendor evaluation

Skill shinzoxD/knackbox/skills/documents/vendor-evaluation

Curated, auditable, benchmark-ready Agent Skills library for Claude Code, Codex, OpenCode, Cursor, and more.

Install
npx -y skills add shinzoxD/knackbox --skill vendor-evaluation

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

2 things to look at

  • 28 days oldThe repository was created 28 days ago. New is not bad, but a brand new repository carrying a familiar-sounding name is the shape a typosquat arrives in, and there has been no time for anyone else to find a problem with it.
  • 0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

Run structured vendor evaluations and scorecards for build-vs-buy decisions. Use whenever the user compares vendors, shortlists tools, runs a bake-off, or needs a fair scorecard across products for a purchase decision.

The file declares its own license as Apache-2.0. That is the author’s claim about this one file, and it is not the same thing as the license GitHub reports for the repository, which is listed with the other numbers below.

SKILL.md

1.4 KB, 248 tokens by cl100k_base, as published. Nobody here has run it

Vendor Evaluation

Score what matters: must-haves, weighted wants, risks, and total cost — not demo polish alone.

Workflow

  1. Decision, constraints, must-haves vs nice-to-haves.
  2. Criteria + weights (security, cost, UX, ops, lock-in).
  3. Candidate list and disqualify early misses.
  4. Evidence: docs, trials, references — not brochure claims.
  5. Scorecard + recommendation + risks.
  6. Pilot plan if close.

Output format

## Evaluation: <category>
### Must-haves
### Scorecard
| Criterion | Weight | Vendor A | Vendor B | Notes |
### TCO notes
### Risks / lock-in
### Recommendation
### Pilot plan

Rules

  1. Never invent SOC2/pricing; mark unknown.
  2. Weight security for sensitive data.
  3. Include exit cost / data portability.
  4. Separate build option when relevant.
  5. Document who scored and when.

Edge cases

  • Incumbent bias: re-score fairly.
  • Open source + support vendor: split product vs support.
  • Multi-year contracts: renegotiation leverage notes.

Keep looking

Skills are one crate of 328,083. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.