Agent skill

Procurement

by ericrisco in ericrisco/rsc-harness

A skill your agent uses when a small operator must choose what to buy and from whom: pick a supplier, write an RFI/RFQ/RFP that returns comparable bids, score quotes on total cost of ownership…

MITAuto-check passedBusiness, Finance & HR

Install Procurement

skills CLI
$ npx skills add ericrisco/rsc-harness --skill procurement -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install ericrisco/rsc-harness procurement --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/ericrisco/rsc-harness.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/procurement .claude/skills/procurement && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
procurement
GitHub stars
156
Token cost
~3.2k tokens
SKILL.md length
1,592 words
Files
6 (incl. scripts, references)
Skills in repo
229
Repo updated
First seen
Licence
MIT

At a glance

A skill your agent uses when a small operator must choose what to buy and from whom: pick a supplier, write an RFI/RFQ/RFP that returns comparable bids, score quotes on total cost of ownership…

  • Works in 4 steps: Requirement brief — what you are buying,… → Sourcing request — the RFI, RFQ, or RFP… → Weighted supplier scorecard — criteria… → …
  • A small operator must choose what to buy and from whom: pick a supplier
  • SKILL.md covers What you produce, First move: segment the buy…, Pick the right request: RFI vs… and The weighted scorecard, plus 6 more sections
  • Runs Shell scripts from its folder

What it does

Procurement is an agent skill from ericrisco/rsc-harness. Use when a small operator must choose what to buy and from whom: pick a supplier, write an RFI/RFQ/RFP that returns comparable bids, score quotes on total cost of ownership, negotiate price and payment terms, or judge single-source risk. NOT redlining the purchase agreement (that is contracts), NOT the price you charge customers (that is pricing), NOT stock once it lands (that is inventory).

Its SKILL.md is about 3.2k tokens, which your agent loads only when the skill is triggered. The skill folder holds 8 other files, including scripts and reference files (for example `evals/README.md`, `evals/cases.yaml` and `references/scorecard-and-tco.md`).

It sits in Business, Finance & HR, covering Vendor and procurement management, Proposals and quotes and Contract review. The repository describes itself as: Your agent invents things because it has no memory, and can't touch your database because it has no arms. rsc is the meta-harness that gives it both, plus the trade to know the… The licence is MIT.

When your agent uses it

  • A small operator must choose what to buy and from whom: pick a supplier
  • Write an RFI/RFQ/RFP that returns comparable bids
  • Score quotes on total cost of ownership
  • Negotiate price and payment terms

Example prompts

  • “/procurement”

Requirements

  • A Bash shell

Workflow steps

4 steps, taken from the first numbered list in SKILL.md.

  1. Requirement brief — what you are buying, in numbers (spec, quantity, quality bar, delivery window, must-haves vs nice-to-haves). Without…
  2. Sourcing request — the RFI, RFQ, or RFP you send. Its job is to force comparable responses, so it discloses the evaluation criteria and a…
  3. Weighted supplier scorecard — criteria with weights summing to 100, a score per supplier per criterion, a weighted total. This is what…
  4. Negotiation / term sheet — the price, the payment terms, the concession you traded for them, and your walk-away (BATNA).

What it can do on your machine

Read from SKILL.md and the folder at commit 92fde8f. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Ships 1 file in scripts/ (Shell), which the agent can run.

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Procurement loads about 3.2k tokens when it runs, and up to ~5.4k if it reads all its reference files. Until then it costs about 103 tokens; SKILL.md has 1,592 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~103
When it runs · the whole SKILL.md, loaded when a task matches
~3.2k
With references · SKILL.md plus every file in references/, read only if the agent opens them
~5.4k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); the scripts in this folder are not scanned.

SKILL.md

The full file from ericrisco/rsc-harness at commit 92fde8f, republished under its MIT licence (© ericrisco). 1,592 words, ~3,181 tokens.

Download SKILL.mdSave it as .claude/skills/procurement/SKILL.md (or your agent's skills folder). This skill also uses 5 other files; get the full folder from GitHub.
name
procurement
description
Use when a small operator must choose what to buy and from whom: pick a supplier, write an RFI/RFQ/RFP that returns comparable bids, score quotes on total cost of ownership, negotiate price and payment terms, or judge single-source risk. NOT redlining the purchase agreement (that is `contracts`), NOT the price you charge customers (that is `pricing`), NOT stock once it lands (that is `inventory`).
tags
procurement, sourcing, suppliers, rfq, negotiation, vendor-management
recommends
contracts, pricing, inventory, logistics-ops, invoicing, cost-tracking
origin
risco

Procurement — buy well, and leave a decision someone could audit

You are a disciplined buyer's analyst. Your job is to choose the right supplier and the right terms on total cost — and to leave behind a scored, weighted decision a colleague could re-run and reach the same conclusion. You do not sign the contract, you do not set the price you charge customers, and you do not count the stock once it lands. You decide what to buy and from whom, and you make the deal.

The one rule, stated up front: never compare suppliers on sticker price — always total cost of ownership. And never single-source a critical input silently — name the risk and write down the backup. Every other section serves these two.

What you produce

Four artifacts. Each exists because a later question demands it.

  1. Requirement brief — what you are buying, in numbers (spec, quantity, quality bar, delivery window, must-haves vs nice-to-haves). Without it, bids come back incomparable.
  2. Sourcing request — the RFI, RFQ, or RFP you send. Its job is to force comparable responses, so it discloses the evaluation criteria and a deadline.
  3. Weighted supplier scorecard — criteria with weights summing to 100, a score per supplier per criterion, a weighted total. This is what makes the choice defensible and what scripts/verify.sh checks.
  4. Negotiation / term sheet — the price, the payment terms, the concession you traded for them, and your walk-away (BATNA).

First move: segment the buy (Kraljic 2×2)

Before you pick a tactic, place the buy on two axes — business impact (profit/criticality if it fails) and supply risk (how hard to replace the supplier). Tactic must match the quadrant, or you over-invest effort on a stapler order and under-invest on the part that halts production (Kraljic, HBR 1983).

Impact \ RiskLow supply riskHigh supply risk
Low impactRoutine — automate, consolidate orders, buy from an approved-supplier list. Don't run a tender for paperclips.Bottleneck — secure continuity. Develop a backup supplier, hold buffer stock, lock a delivery SLA.
High impactLeverage — run a competitive bid, exploit your buying power, churn suppliers for price.Strategic — partner. Fewest suppliers, joint planning, multi-year deal, deepest relationship.

Re-score quadrants at least annually — a routine item becomes a bottleneck the day its only maker exits the market. SRM cadence scales with quadrant (see references): quarterly reviews for Strategic, semiannual for Bottleneck.

Pick the right request: RFI vs RFQ vs RFP

Match the request to what you don't yet know. Sending the wrong one wastes a bidding cycle.

You need to…Send a…Use when
Learn the market, scope the fieldRFI (request for information)Requirements are still fuzzy; non-binding; you're narrowing a shortlist.
Get a price on a fully-specified, identical needRFQ (request for quotation)Specs are locked, suppliers are comparable, and price is the decider.
Solicit a full solution where the how is openRFP (request for proposal)You must evaluate approach and price — the supplier designs part of the answer.

The mature phased flow is RFI → RFP → RFQ, but a well-defined commodity buy skips straight to an RFQ. Don't run an RFP for a screw you can fully spec — that's an RFQ wearing a costume.

Whatever you send, it MUST contain these or the bids come back incomparable:

  • exact spec + quantity (and minimum order quantity tolerance);
  • delivery terms and required date (Incoterm if cross-border);
  • the evaluation criteria and their weights, disclosed — bidders optimize for what you'll score, and disclosure cuts disputes;
  • a hard response deadline;
  • a required response format (a filled table beats free-form prose you can't compare).

Copy-ready RFI/RFQ/RFP skeletons and the invite + award/regret email templates: see references/sourcing-requests.md.

The weighted scorecard

Assign each criterion a weight; weights sum to 100. Score every supplier on every criterion (a 1–5 scale is enough). Weighted total = Σ(weight × score). Predefined weights set before you see bids kill the bias where you reverse-engineer the criteria to pick the supplier you already liked.

A common starting split — tune per category:

  • technical / capability fit ~40
  • price / commercial ~30
  • vendor viability / risk ~30

Worked mini-example (scores 1–5):

text
Criterion        Weight  SupplierA  SupplierB   A weighted   B weighted
Capability         40       4          3           160          120
Commercial         30       3          5            90          150
Viability/risk     30       4          3           120           90
                  ----                              ----         ----
Total              100                               370         360

A edges B (370 vs 360) even though B is cheaper on the commercial line — because capability and risk outweigh a lower price. Disclose these weights to bidders. Full template: references/scorecard-and-tco.md.

Total cost of ownership, never sticker price

The cheapest unit price routinely loses once you add the costs nobody quoted. A workable model:

text
TCO = Acquisition
    + (Annual Operating   × Years)
    + (Annual Maintenance × Years)
    + Training
    + Downtime / lost productivity
    − Residual / resale value

The lines people forget: delivery & freight, installation, integration effort, training, support, downtime, license true-ups, exit/disposal. Quote all of them or you're comparing fiction.

Bad → Good. You are buying 5,000 units a year.

  • Bad — compare on unit price: Supplier A at $9.00 beats Supplier B at $11.00. Pick A.
  • Good — compare on TCO:
text
Line              Supplier A         Supplier B
Unit × 5,000      $9.00 → $45,000    $11.00 → $55,000
Freight           $6,000 (overseas)  $500 (local)
Support contract  $5,000/yr          included
Downtime (8% defect, lost prod.)  $4,000   $0
                  --------           --------
Year-1 TCO        $60,000            $55,500

Supplier B — the "expensive" one — is $4,500 cheaper once freight, support, and defect downtime land. Always recompute on TCO before you award.

Negotiation

Rules, each with its why:

  • Separate price from terms; settle price first. Resistance is lowest on price when terms aren't yet on the table; opening with both lets the supplier trade one against the other.
  • Trade something for every concession — never ask free. Want Net 60 or a volume discount? Offer what the supplier values: an annual/volume commitment, a phased ramp (Net 45 for 6 months → Net 60 after), or a reliable-payer track record. A free ask gets a free no.
  • Know your BATNA (walk-away). Your leverage is the credible alternative supplier. If you have none, that's a single-source problem to fix first (next section), not a negotiation to win.
  • Anchor on TCO, not line items. Negotiate the total cost you computed, so the supplier can't claw back a unit-price cut through freight or support.

The early-payment discount is math, not a vibe. A "2/10 net 30" offer (2% off if paid within 10 days, else full at 30) is a return on paying 20 days early:

text
Annualized return = (Discount% ÷ (1 − Discount%)) × (365 ÷ DaysSaved)
                  = (0.02 ÷ 0.98)        × (365 ÷ 20)
                  ≈ 0.0204               × 18.25
                  ≈ 37.2% annualized

Take the discount whenever your cost of capital is below ~37.2%. "We're tight on cash" is rarely a reason to skip a 37.2% return — borrow against it before you pass. Negotiation playbook and BATNA worksheet: references/scorecard-and-tco.md.

Show full SKILL.md (589 more words)Show less

Supply risk + the maverick-spend leak

Name which case any critical input falls in — they are different risks:

  • Single source — you chose one supplier though alternatives exist. A concentration risk you accepted; document why and a switch plan.
  • Sole source — only one supplier exists. A risk you must mitigate, not choose away: buffer stock, a qualification project for an alternative, a contractual continuity clause.
  • Dual sourcing — two qualified suppliers for the same item, splitting volume. Cuts single-point-of-failure risk at higher unit cost; right for Bottleneck/Strategic items.

Require a written backup plan for any critical or strategic single/sole source. A critical input with no named backup is an outage waiting for a date.

Maverick (off-process) spend is the silent leak — purchases made outside the approved process and supplier list. APQC measured it around 1.8% of annual purchase value; organizations can lose up to ~16% of negotiated savings to it, and the practical target is under 10% of spend going off-contract. The fix isn't a procurement suite — it's a one-page intake gate (anything over $X routes through this skill's flow) plus an approved-supplier list.

Ongoing: scorecard, cadence, re-source triggers

A supplier you picked once is not a supplier you can ignore. Track four dimensions on a recurring performance scorecard: quality (defect/return rate), delivery (on-time-in-full), price drift (vs the awarded price), responsiveness (issue resolution time). Review on the SRM cadence set by Kraljic quadrant.

Re-source — re-open the comparison — when a trigger fires: OTIF drops below your threshold for two periods, price drifts up beyond the contracted escalator, a single/sole source loses its only backup, or the category re-segments into a higher-risk quadrant. Performance scorecard template, SRM-cadence-by-quadrant table, and re-source thresholds: references/scorecard-and-tco.md.

Anti-patterns

Anti-patternWhy it bitesDo instead
Compare suppliers on unit price onlyThe cheapest unit routinely loses once freight, support, and downtime landRecompute every shortlist on TCO before awarding
One vague RFP for a commodity you can fully specWastes a bidding cycle; bids come back incomparableSend an RFQ with fixed specs when price is the decider
Evaluation weights kept secret (or invented after bids arrive)Invites bias and post-award disputesSet weights before bids, disclose them, score predefined criteria
Ask for Net 60 / a discount with nothing offeredA free ask earns a free noTrade a volume commit, phased ramp, or reliable-payer record
Skip the early-payment discount because "we're tight"You pass on a ~37.2% annualized returnCompute it; take it whenever cost of capital is lower
Single-source a critical part and say nothingAn outage with no named owner or backupLabel single/sole/dual, write the backup plan
Negotiate price and terms in one breathThe supplier trades one against the otherSettle price first, then negotiate terms separately
Let small buys skip the processMaverick spend quietly burns negotiated savingsA one-page intake gate + approved-supplier list

Hand-offs

You own the decision and the deal. The moment it becomes something else, route:

  • Drafting/redlining the binding purchase agreement, MSA, liability/IP clauses, signature → ../contracts/SKILL.md.
  • The price you charge your customers, your margins, packaging → ../pricing/SKILL.md.
  • Stock levels, reorder points, safety stock, SKU counts once goods are on hand → ../inventory/SKILL.md.
  • Freight, carrier choice, warehousing, customs once you've decided to buy → ../logistics-ops/SKILL.md.
  • Generating and paying the supplier bill, dunning, payment runs → ../invoicing/SKILL.md.
  • Tracking ongoing SaaS/subscription spend after a renewal decision → ../cost-tracking/SKILL.md.

Note on AI: generative tools can compress supplier discovery by up to ~90% — finding candidates fast. They do not replace the weighting, TCO model, risk segmentation, or negotiation. Use AI to widen the shortlist; keep the judgment human and on paper.

© ericrisco, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 5 other files (scripts, references) in skills/procurement of ericrisco/rsc-harness.

  • SKILL.md
  • evals/README.md
  • evals/cases.yaml
  • references/scorecard-and-tco.md
  • references/sourcing-requests.md
  • scripts/verify.sh

Open the folder on GitHubat commit 92fde8f

Compare with similar skills

Procurement next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Procurement compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Procurement this skillericrisco/rsc-harness156—~3.2kAutomated safety check: PassMIT
Energy Procurementaffaan-m/ECC274k4 repos~7.4kAutomated safety check: PassApache-2.0
Rfp Response Compliance Reviewpnp/sharepoint-skills131—~2.8kAutomated safety check: PassMIT
Influence And Negotiationsamber/cc-skills228—~7.1kAutomated safety check: PassMIT
Stakeholder SummaryZekaiSuni/claude-for-legal-turkish107—~670Automated safety check: PassApache-2.0
Rfp Responsemohitagw15856/pm-claude-skills1.4k—~882Automated safety check: PassMIT

Similar skills

  • Energy Procurement

    affaan-m/ECC

    Procure electricity and natural gas for commercial and industrial facilities: tariff and rate-schedule optimization, demand-charge mitigation, supplier RFPs, fixed/index/block-and-index hedging…

    274k GitHub starsUsed in 4 repos~7.4k tokens
    Business, Finance & HRAuto-check passed
  • Rfp Response Compliance Review

    pnp/sharepoint-skills

    Reviews a draft proposal against the firm's configurable compliance rules — prohibited language, required disclosures, role and positioning boundaries, and procurement-submission requirements.

    131 GitHub stars~2.8k tokensUpdated yesterday
    Business, Finance & HRAuto-check passed
  • Influence and negotiation toolkit for any interaction needing another person's agreement, even when the user never says 'negotiation'.

    228 GitHub stars~7.1k tokensUpdated 6 days ago
    Business, Finance & HRAuto-check passed
  • Stakeholder Summary

    ZekaiSuni/claude-for-legal-turkish

    Convert a legal review into a short, sanitized, business-readable summary for Turkish commercial practice.

    107 GitHub stars~670 tokensUpdated 4 mo ago
    Business, Finance & HRAuto-check passed
  • Rfp Response

    mohitagw15856/pm-claude-skills

    Write a compliant, competitive response to an RFP/RFQ/ITT (government or enterprise procurement).

    1.4k GitHub stars~882 tokensUpdated yesterday
    Sales & SupportAuto-check passed
  • Rfp Scoring Matrix

    mohitagw15856/pm-claude-skills

    Build a weighted RFP evaluation matrix and defensible award recommendation.

    1.4k GitHub stars~1.4k tokensUpdated yesterday
    Sales & SupportAuto-check passed

More from ericrisco/rsc-harness

All 229 skills in this repo
  • Ab Testing

    ericrisco/rsc-harness

    A skill your agent uses when designing or analyzing a controlled experiment — falsifiable hypothesis, sample size from an MDE, reading significance/CI/power, CUPED, or rescuing tests that won't go…

    156 GitHub stars~2.4k tokensUpdated yesterday
    Auto-check passed
  • Accessibility

    ericrisco/rsc-harness

    A skill your agent uses when making a web UI conform to WCAG 2.2 Level AA — axe-core or Lighthouse a11y violations, keyboard operability, focus management, ARIA roles/names/live regions, contrast…

    156 GitHub stars~3.4k tokensUpdated yesterday
    Auto-check passed
  • Ads

    ericrisco/rsc-harness

    A skill your agent uses when running or fixing paid acquisition on Google or Meta — campaign structure (Performance Max, Demand Gen, Search, Advantage+), platform-fit creative, budget/scaling rules…

    156 GitHub stars~2.2k tokensUpdated yesterday
    Auto-check passed
  • Agent Eval

    ericrisco/rsc-harness

    A skill your agent uses when measuring whether an LLM or agent system actually got better and gating merges on it: golden sets, fixing an inflated LLM-as-judge, scoring RAG (faithfulness, contextual…

    156 GitHub stars~3.2k tokensUpdated yesterday
    Auto-check passed
  • AI Media

    ericrisco/rsc-harness

    A skill your agent uses when a creative goal must become a finished media file: pick and order generative-media models per modality — AI voiceover, image-to-video clips, score — then glue them with…

    156 GitHub stars~3.3k tokensUpdated yesterday
    Auto-check passed
  • Analytics

    ericrisco/rsc-harness

    A skill your agent uses when instrumenting product or web analytics — GA4/PostHog SDK wiring, event taxonomy, funnels, double-counted events, consent gating, PII scrubbing.

    156 GitHub stars~2.8k tokensUpdated yesterday
    Auto-check passed

Questions about Procurement

What does Procurement do?

A skill your agent uses when a small operator must choose what to buy and from whom: pick a supplier, write an RFI/RFQ/RFP that returns comparable bids, score quotes on total cost of ownership…. Procurement is an agent skill from ericrisco/rsc-harness. Use when a small operator must choose what to buy and from whom: pick a supplier, write an RFI/RFQ/RFP that returns comparable bids, score quotes on total cost of ownership, negotiate price and payment terms, or judge single-source risk.

When should I use Procurement?

Procurement fits situations like: A small operator must choose what to buy and from whom: pick a supplier; write an RFI/RFQ/RFP that returns comparable bids; score quotes on total cost of ownership; negotiate price and payment terms.

How do I install Procurement in Claude Code?

Run `npx skills add ericrisco/rsc-harness --skill procurement -a claude-code`. Or copy the skill folder (skills/procurement in ericrisco/rsc-harness) into .claude/skills/procurement in your project. Claude Code loads it when a task matches its description.

How do I install Procurement in Codex?

Run `npx skills add ericrisco/rsc-harness --skill procurement -a codex`. Or copy the skill folder (skills/procurement in ericrisco/rsc-harness) into .agents/skills/procurement in your project. Codex loads it when a task matches its description.

Can I use Procurement in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add ericrisco/rsc-harness --skill procurement -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/procurement, .gemini/skills/procurement, .github/skills/procurement and .opencode/skills/procurement in your project.

What does Procurement need to run?

Going by SKILL.md and its folder, Procurement needs a shell for the scripts in its folder. Our summary lists: A Bash shell.

Does Procurement access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Procurement safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. The check reads SKILL.md only: the scripts in the folder are not scanned, so read them before running anything.

What licence does Procurement use?

Procurement is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Procurement use?

About 3.2k tokens (SKILL.md is roughly 13k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 2.2k tokens, read only when the agent opens those files.

What are the alternatives to Procurement?

Skills that share tags, products or a category with Procurement: Energy Procurement (affaan-m/ECC, 274k stars), Rfp Response Compliance Review (pnp/sharepoint-skills, 131 stars), Influence And Negotiation (samber/cc-skills, 228 stars) and Stakeholder Summary (ZekaiSuni/claude-for-legal-turkish, 107 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Procurement?

ericrisco (a GitHub user) maintains it in ericrisco/rsc-harness, which has 156 GitHub stars. The repository holds 229 skills in this directory. The repository was last updated on October 6, 2026.

Source: ericrisco/rsc-harness on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.