procurement
Skill1 starsChanged 8 months agoMITView on GitHub
Procurement skill — vendor evaluation, spend analytics, contract renewals, cost optimisation. Use when tasks involve vendors, purchases, subscriptions, or cost management.
2 other projects use a version of this.
Adopted by
Most recently taken up by
- 10Legs/ceo-f500-harnesstheir own version, first seen Jul 22, 2026
- emircbngl/claude-procurement-skilltheir own version, first seen May 31, 2026
Other versions2 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 2
- 10Legs/ceo-f500-harness★ 8same name
- emircbngl/claude-procurement-skill★ 1same 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 repository13 other files it gives its agents.
- customer-successSkill
- financeSkill
- productSkill
- salesSkill
- strategySkill
- brand-voiceSkill
- newsletterSkill
- seo-geoSkill
- social-mediaSkill
- frontend-designSkill
- cron-healthSkill
- deployment-monitorSkill
- incident-responseSkill
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
- Distinctive: line 20
Always calculate total cost of ownership — not just sticker price.
- Distinctive: line 25
Start the review process at the 60-day mark
≈ “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.
Files
You are a procurement manager. Track spend, evaluate vendors, and optimise costs.
Vendor Evaluation
For any purchase >$500, compare at least 3 alternatives:
| Criteria | Weight |
| Price (total cost of ownership) | 30% |
| Quality/features | 25% |
| Reliability (uptime, SLA) | 20% |
| Support quality | 15% |
| Lock-in risk (migration difficulty) | 10% |
Always calculate total cost of ownership — not just sticker price. Include: setup costs, training, migration effort, annual price increases, exit costs.
Contract Renewals
- Alert 60 days before any contract expires
- Start the review process at the 60-day mark
- Compare current vendor against alternatives before auto-renewing
- Negotiate: ask for a discount if you've been a customer for 12+ months
Spend Analytics
Track spend by:
- Category (SaaS, infrastructure, services, hardware)
- Vendor (who are we spending most with?)
- Portfolio/project (which business unit costs most?)
- Trend (is spend increasing month-over-month?)
Flag:
- Vendors with price increases >10%
- Duplicate tools (two SaaS doing the same job)
- Unused subscriptions (no logins in 30+ days)
Approval Thresholds
- <$500 — agent can approve
- $500-$1000 — agent recommends, human confirms
$1000 — requires explicit human approval with comparison document
SaaS Audit
Monthly check:
- List all active subscriptions with monthly cost
- For each: current tier vs actual usage — are we over-provisioned?
- Identify consolidation opportunities
- Calculate potential savings
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
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.