agentsclimarketplace
Sign in

Vendor evaluation

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

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.From its SKILL.md

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.

One thing to look at

  • 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 file declares

Copied from the file, not written here

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.

What ships with it: 1 file

1.1 KB alongside SKILL.md

benchmarks/

Gives 0 of the 12 instructions most operations skills give in 248 tokens

Counted across 483 of the 484 authors here whose files we hold, read 2026-08-07

  • Collect monitoring data throughout the simulationin 14 of 483, across 6 files
  • Set the random seed for reproducibilityin 14 of 483, across 6 files
  • Validate simulations against analytical solutionsin 12 of 483, across 4 files
  • Clarify goals, constraints, and inputsin 11 of 483, across 2 files
  • Implement contract tests for integration pointsin 11 of 483, across 2 files
  • Implement strangler fig infrastructure with API gatewayin 11 of 483, across 2 files
  • Audit modernized components for security vulnerabilitiesin 11 of 483, across 2 files
  • Avoid Python blocking calls in processesin 10 of 483, across 3 files
  • Use resource context managers for automatic cleanupin 9 of 483, across 2 files
  • Maintain consistent time unitsin 9 of 483, across 2 files
  • Validate outcomes against success criteriain 8 of 483, across 1 file
  • Analyze the legacy codebase for technical debtin 8 of 483, across 1 file

Said here and by no other author read

  • disqualify candidates missing must-haves early
  • gather evidence from docs trials and references
  • weight security for sensitive data
  • include exit cost and data portability
  • evaluate build option separately when relevant
  • document who scored and when

Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once. Length counted with cl100k_base; the agent that loads this file may tokenize it differently.

Keep looking

Skills are one crate of 325,949. 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.