procurement-optimizer
by alirezarezvaniprocurement-optimizer helps Procurement Operations run SaaS audits, UNSPSC-aligned spend categorization, Pareto and YoY review, purchasing-cycle bottleneck analysis, and risk-aware supplier consolidation with tier-1 break-glass safeguards.
This skill scores 86/100, making it a solid listing candidate for directory users who need an agent-assisted procurement spend review or SaaS audit workflow. The repository provides enough trigger clarity, executable scripts, intake template, and reference material for an agent to do more than a generic prompt, though users should note the missing local install instructions and the tech-company bias in the built-in taxonomy.
- Highly triggerable frontmatter names concrete use cases and trigger phrases such as spend audit, SaaS audit, supplier consolidation, category strategy, duplicate SaaS, and renewal cluster.
- Operational content is substantive: SKILL.md is large, includes workflow/constraints, and is backed by three deterministic stdlib scripts for spend categorization, purchasing-cycle analysis, and supplier consolidation.
- Good procurement guardrails are embedded, including Pareto analysis, YoY growth handling, Goldratt-style bottleneck flagging, renewal clustering, and refusal to single-source tier-1 categories without a break-glass plan.
- No install command or README is present in the skill path, so users must infer installation from the broader repository or skill-file convention.
- The categorizer is explicitly a tech-company-oriented, ~30-category UNSPSC-aligned map rather than a full UNSPSC database, which may limit fit for non-tech or highly specialized procurement contexts.
Overview of procurement-optimizer skill
What procurement-optimizer is for
procurement-optimizer is a business-operations skill for spend audits, SaaS rationalization, category review, and supplier consolidation planning. It helps a procurement, BizOps, finance, or operations lead move from messy AP/card/SaaS exports to a structured view of what is being bought, which categories drive spend, where purchasing cycles are slow, and which suppliers can be consolidated without creating unacceptable operational risk.
Best-fit users and decisions
This skill is strongest for Procurement Operations teams running an annual SaaS audit, indirect-spend review, renewal planning cycle, or supplier-base rationalization. It is built around practical decisions: which categories deserve attention first, which duplicate tools or suppliers are worth challenging, where approval or PO cycle time is creating bottlenecks, and when consolidation should be rejected because the category is too critical to single-source.
What makes the procurement-optimizer skill different
Unlike a generic “analyze my spend” prompt, the repository includes deterministic Python scripts and procurement-specific reference material. The scripts cover UNSPSC-aligned spend categorization, Pareto analysis, YoY spend growth, purchasing-cycle bottlenecks, and risk-flagged supplier consolidation. The strongest differentiator is its explicit refusal to recommend single-source consolidation for tier-1 categories unless a break-glass plan is documented.
Where it may not fit
Do not use procurement-optimizer as a vendor-performance scorecard, contract legal review, sourcing-event manager, or full ERP/procurement-suite replacement. It works best on structured exports and planning questions, not on live supplier negotiations or subjective relationship health. If your input is only a list of vendor names with no spend, category, renewal, or criticality data, results will be directionally useful but not decision-grade.
How to Use procurement-optimizer skill
procurement-optimizer install and files to inspect first
Install with npx skills add alirezarezvani/claude-skills --skill procurement-optimizer. The source is under business-operations/skills/procurement-optimizer in alirezarezvani/claude-skills.
Read SKILL.md first to understand triggering phrases and boundaries. Then inspect assets/spend_intake_template.md before preparing data. For deeper judgment, read references/procurement_anti_patterns.md, references/spend_management_canon.md, and references/saas_management_canon.md. If you plan to run deterministic analysis, review scripts/spend_categorizer.py, scripts/purchasing_cycle_analyzer.py, and scripts/supplier_consolidation.py.
Input data the skill needs
For spend categorization, prepare line items with supplier, description, category hint, annual spend, frequency, currency, and optionally prior-year spend. The intake template is designed for the top 100–200 line items because the Pareto usually reveals the categories that matter most without cleaning every transaction.
For supplier consolidation, add category, criticality tier, contract term, integration count, switching-cost estimate, renewal date, and whether a break-glass option exists. For cycle-time analysis, provide PO records with request, approval, PO issue, goods receipt, payment dates, category, and approver hops.
Turning a rough goal into a strong prompt
A weak prompt is: “Find savings in our SaaS spend.” A stronger procurement-optimizer usage prompt is:
“Use procurement-optimizer for Procurement Operations. I’m running an annual SaaS audit for a 350-person scaleup. Categorize this spend export, identify the Pareto categories, flag duplicate-function clusters, and produce a supplier-consolidation plan. Do not recommend single-source consolidation for tier-1 categories unless a break-glass plan is present. Pay special attention to renewals in Q3 and YoY increases over 30%.”
This improves output because it gives the skill company profile, decision objective, risk constraint, time horizon, and prioritization rules.
Practical workflow for better results
Start with categorization, not consolidation. First run or ask for UNSPSC-aligned grouping and Pareto breakdown, then review categories manually for obvious misclassification. Next, analyze YoY growth and renewal clusters. Only then ask for a consolidation plan, because supplier recommendations are much better when category, criticality, switching cost, and renewal timing are known.
Use the reference files before accepting recommendations. procurement_anti_patterns.md is especially important because theoretical savings often disappear when migration cost, operational dependency, or supplier concentration risk is ignored.
procurement-optimizer skill FAQ
Is procurement-optimizer only for SaaS audits?
No. SaaS audit is a major use case, but procurement-optimizer also supports broader indirect spend review, category strategy, purchasing-cycle analysis, and supplier rationalization. The included category map is tuned for tech-company spend, so it is especially strong for SaaS-heavy businesses, scaleups, and digital operations teams.
How is this better than an ordinary procurement prompt?
An ordinary prompt may produce plausible but generic recommendations. The procurement-optimizer skill adds a defined workflow, procurement anti-patterns, category-management references, and deterministic scripts. That makes it easier to trigger the right analysis, avoid reckless consolidation, and separate “large spend” from “safe savings opportunity.”
Do beginners need procurement expertise to use it?
A beginner can use the templates and scripts, but the best results still require business judgment. You should know which systems are critical, which vendors have operational lock-in, and which renewals are negotiable. The skill helps structure the analysis; it does not replace stakeholder interviews or finance/procurement governance.
When should I not install procurement-optimizer?
Skip it if you only need vendor health monitoring, legal contract clause extraction, accounts-payable automation, or a one-off negotiation email. Also avoid using it as the sole basis for terminating critical vendors. It is a planning and analysis skill, not an approval authority.
How to Improve procurement-optimizer skill
Improve procurement-optimizer inputs before asking for recommendations
The most common failure mode is under-specified data. Add descriptions, category hints, annualized spend, renewal dates, prior-year spend, and business owner where possible. For SaaS, include seat count, active usage if available, department owner, and whether the tool is system-of-record, workflow-critical, or easily replaceable.
Add risk context, not just savings targets
Procurement teams care about savings, continuity, leverage, compliance, and adoption. A prompt that says “maximize savings” can lead to unsafe consolidation. Better: “Find savings while preserving redundancy for tier-1 systems, avoiding renewal-month overload, and flagging any migration that requires engineering, finance close, security review, or customer-facing downtime.”
Iterate after the first output
Treat the first procurement-optimizer output as a triage view. Correct bad categories, mark false duplicates, add missing switching costs, and clarify tier-1 systems. Then ask for a revised plan with three buckets: quick wins, negotiation candidates, and high-risk opportunities requiring executive review.
Extend the skill for your operating model
If your company has a custom taxonomy, modify the category assumptions in scripts/spend_categorizer.py. If certain categories are always critical in your industry, update profile-driven tier-1 assumptions in scripts/supplier_consolidation.py. For mature Procurement Operations teams, add internal policy thresholds such as approval limits, preferred suppliers, security-review requirements, and renewal notice periods.