tool-procurement-eval
Evaluate a new tool before it joins the stack — the problem-first framing (tools answer needs, not demos), the trial designed with success criteria upfront, the stack-fit check (integration, overlap, the tool-sprawl tax), and the security/data review sized to the stakes. Use when asked should we buy this tool, evaluate this software for the team, we have three tools that do this already, or run a proper trial before committing. Produces the need statement, the trial design with pre-set criteria, the stack-fit audit, and the adopt/decline verdict with its reasoning.
npx skills add mohitagw15856/pm-claude-skills --skill tool-procurement-eval --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# Tool Procurement Eval Skill Tools enter stacks backwards: someone sees a demo, gets excited, and the "evaluation" becomes a justification ritual ([vendor-comparison-matrix](../vendor-comparison-matrix/SKILL.md) fights this at the compare stage; this skill fights it at the door). The forward order: the *need* stated first (which problem, whose, costing what — [purchase-justification](../purchase-justification/SKILL.md) arithmetic), the *stack-fit* check before the trial (does something we own already do this? — the overlap audit that kills half of tool requests honestly), the *trial designed* with success criteria written before day one (or the trial's warm feelings decide), and the security/data review sized to what the tool touches — because the fun tool that ingests customer data is a compliance decision wearing a productivity costume. ## What This Skill Produces - **The need statement** — the problem, its owner, its cost, and the requirements it implies (must vs. nice — pre-demo) - **The stack-fit audit** — the overlap check against owned tools, the integration reality, and the sprawl tax named - **The trial design** — duration, participants, the pre-written success criteria,
- What This Skill Produces
- Required Inputs
- Framework: The Eval Rules
- Output Format
- The Need + Requirements
- Stack-Fit Audit
- Trial Design
- The Verdict
- Quality Checks
- Anti-Patterns
What does the tool-procurement-eval skill do?
Evaluate a new tool before it joins the stack — the problem-first framing (tools answer needs, not demos), the trial designed with success criteria upfront, the stack-fit check (integration, overlap, the tool-sprawl tax), and the security/data review sized to the stakes. Use when asked should we buy this tool, evaluate this software for the team, we have three tools that do this already, or run a proper trial before committing. Produces the need statement, the trial design with pre-set criteria, the stack-fit audit, and the adopt/decline verdict with its reasoning.
How do I install it?
Run `npx skills add mohitagw15856/pm-claude-skills --skill tool-procurement-eval --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From mohitagw15856/pm-claude-skills, a repository with 1,255 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.