Ops Supplier Scorecard

Turn PO and receipt data into a supplier scorecard on OTIF, lead time variability, quality, price and dependency risk. Use for vendor reviews, supplier performance or consolidation.

5 stars 1 forksOther

Install

skills CLI (Claude Code, Cursor, Codex and more)
npx skills add eshmith7/claude-skills-library --skill ops-supplier-scorecard
Manual install
git clone --depth 1 https://github.com/eshmith7/claude-skills-library.git /tmp/claude-skills-library
mkdir -p ~/.claude/skills
cp -r /tmp/claude-skills-library/ops-skills/ops-supplier-scorecard ~/.claude/skills/ops-supplier-scorecard

Personal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.

From the SKILL.md

# Supplier Performance Scorecard

Most supplier reviews run on two inputs: the buyer's memory, and the loudest recent failure. So the supplier who quietly delivered late nine times looks better than the one who missed badly once. A scorecard fixes that, but only if it measures against what was originally committed rather than what was later renegotiated.

## When to use this

Trigger on: supplier scorecard, vendor performance, vendor review, OTIF, on time in full, supplier rating, vendor evaluation, supplier QBR, supplier consolidation, "which vendors are letting us down", single source risk.

## Before you start

Required: purchase order and receipt data covering at least one full quarter, with item, supplier, order date, promised date, receipt date, quantity ordered and quantity received.

Ask, briefly:
1. **Whether the promised date in the file is the original commitment or the latest revised one.** This is the most important question in this skill. If a supplier can move the date and the system keeps only the newest, every supplier scores near perfect and the scorecard is worthless. Ask explicitly. If only revised dates exist, say clearly what the number does and does not measure.
2. Quality data, if it exists. Incoming inspection results, rejections, returns, complaints.
3. Their tolerance for early delivery. Early is not free; it consumes cash and space, and many companies treat significantly early as a miss.
Read the full skill on GitHub

Details

Skill name
ops-supplier-scorecard
Path
ops-skills/ops-supplier-scorecard/SKILL.md
Repo updated
9 September 2026

FAQ

What does the Ops Supplier Scorecard skill do?

Turn PO and receipt data into a supplier scorecard on OTIF, lead time variability, quality, price and dependency risk. Use for vendor reviews, supplier performance or consolidation.

How do I install the Ops Supplier Scorecard skill?

skills CLI (Claude Code, Cursor, Codex and more): npx skills add eshmith7/claude-skills-library --skill ops-supplier-scorecard. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.

Is Ops Supplier Scorecard popular?

It lives in eshmith7/claude-skills-library, which has 5 GitHub stars and 1 forks.

Related skills

Browse the most popular Claude skills, all other skills, or write your own with the skills generator.