Agent skill

Supplier Scorecard

by mohitagw15856 in mohitagw15856/pm-claude-skills

Build a quarterly supplier performance scorecard with a weighted grade and a clear escalate/develop/exit call.

MITAuto-check passedBusiness, Finance & HR

Install Supplier Scorecard

skills CLI
$ npx skills add mohitagw15856/pm-claude-skills --skill supplier-scorecard -a claude-code

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

GitHub CLI
$ gh skill install mohitagw15856/pm-claude-skills supplier-scorecard --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/mohitagw15856/pm-claude-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/supplier-scorecard .claude/skills/supplier-scorecard && 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
supplier-scorecard
GitHub stars
1.4k
Token cost
~1.4k tokens
SKILL.md length
689 words
Files
1
Skills in repo
1,348
Repo updated
First seen
Licence
MIT

At a glance

Build a quarterly supplier performance scorecard with a weighted grade and a clear escalate/develop/exit call.

  • Asked to review supplier performance
  • SKILL.md covers What This Skill Produces, Required Inputs, Scoring Framework and Output Format, plus 3 more sections
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
  • Prepare a quarterly business review for a vendor

What it does

Supplier Scorecard is an agent skill from mohitagw15856/pm-claude-skills. Build a quarterly supplier performance scorecard with a weighted grade and a clear escalate/develop/exit call. Use when asked to review supplier performance, prepare a quarterly business review for a vendor, score a supplier on OTIF and quality, or decide whether to escalate or exit a supplier. Produces a weighted scorecard with trend arrows, per-dimension evidence, corrective-action status, and a recommendation.

Its SKILL.md is about 1.4k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Business, Finance & HR, covering OKRs and executive reporting and Customer success. The repository describes itself as: 1255 professional Agent Skills for Claude, ChatGPT, Gemini, Cursor & Codex — PRDs, postmortems, leases, medical bills, layoffs, go-bags, new countries. Plain markdown, MIT, in… The licence is MIT.

When your agent uses it

  • Asked to review supplier performance
  • Prepare a quarterly business review for a vendor
  • Score a supplier on OTIF and quality
  • Decide whether to escalate

Example prompts

  • “/supplier-scorecard”

What it can do on your machine

Read from SKILL.md and the folder at commit 1cbf1f0. 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

    No scripts in the folder and no shell commands in SKILL.md.

    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

Supplier Scorecard loads about 1.4k tokens when it runs. Until then it costs about 109 tokens; SKILL.md has 689 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~109
When it runs · the whole SKILL.md, loaded when a task matches
~1.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); files beside SKILL.md are not scanned.

SKILL.md

The full file from mohitagw15856/pm-claude-skills at commit 1cbf1f0, republished under its MIT licence (© mohitagw15856). 689 words, ~1,431 tokens.

Download SKILL.mdSave it as .claude/skills/supplier-scorecard/SKILL.md (or your agent's skills folder).
name
supplier-scorecard
description
Build a quarterly supplier performance scorecard with a weighted grade and a clear escalate/develop/exit call. Use when asked to review supplier performance, prepare a quarterly business review for a vendor, score a supplier on OTIF and quality, or decide whether to escalate or exit a supplier. Produces a weighted scorecard with trend arrows, per-dimension evidence, corrective-action status, and a recommendation.

Supplier Scorecard Skill

A supplier review that ends with "keep monitoring" is a meeting, not a decision. This skill turns delivery, quality, responsiveness, and cost data into a weighted quarterly grade with trend direction — and forces one of three outcomes: escalate, develop, or exit. It also audits whether last quarter's corrective actions actually closed, because a supplier who commits and doesn't deliver is telling you something.

What This Skill Produces

  • A weighted performance grade (0–100) across five dimensions with trend arrows vs. prior quarters
  • Per-dimension evidence: OTIF %, PPM/defect rate, response metrics, cost behavior
  • Corrective-action follow-through audit (committed vs. closed)
  • A classification — Preferred / Approved / Conditional / Exit-candidate — and a recommended action path
  • Talking points for the supplier business review

Required Inputs

Ask for these if not provided:

  • Supplier & spend — name, category, annual spend, share of category, single/dual-sourced
  • Delivery data — OTIF % (on-time in-full) for the quarter, plus 2–3 prior quarters for trend
  • Quality data — PPM or defect rate, customer complaints traced to this supplier, any stop-ships
  • Responsiveness — quote turnaround, engineering-change response, escalation behavior
  • Cost behavior — price changes vs. market/index, cost-reduction commitments delivered
  • Open corrective actions — CAPAs/SCARs from prior reviews and their status

If history is missing, score the current quarter and label trends [no baseline — first scored quarter]. Infer reasonable dimension detail from a thin brief and label it [inferred].

Scoring Framework

Default weights (adjust for category — e.g., quality-critical items shift quality to 35%):

DimensionWeight5 (excellent)3 (acceptable)1 (failing)
Delivery (OTIF)30%≥98%93–95%<90%
Quality (PPM / defects)25%≤100 PPM, no escapes≤1,000 PPM>5,000 PPM or a stop-ship
Responsiveness15%Same-day acknowledgment, proactive alertsMeets agreed SLAsChased for answers
Cost behavior15%Beats index, delivers savings commitmentsTracks indexAbove-index increases, missed commitments
Corrective-action follow-through15%All closed on time with verified effectivenessClosed late but closedRepeat findings, open past due

Grade = Σ(score × weight) × 20 → 0–100. Bands: ≥85 Preferred · 70–84 Approved · 55–69 Conditional (development plan required) · <55 Exit-candidate.

Trend arrows: ↑ improved ≥5 points vs. prior quarter, → within ±5, ↓ declined ≥5. A ↓ trend in Conditional triggers escalation even if the band hasn't changed yet.

Recommendation logic: score AND trajectory AND strategic dependence. A 60-score sole-source supplier gets a development plan with executive sponsorship; a 60-score supplier with two qualified alternates gets a requalification/exit timeline. Say which case applies.

Output Format

Show full SKILL.md (306 more words)Show less
Supplier Scorecard: [supplier] — [quarter]

1. Summary — grade, band, trend, and the recommendation in two sentences.

2. Scorecard — table: Dimension | Weight | Metric this quarter | Prior quarter | Score (1–5) | Trend | Evidence.

3. Corrective-action audit — table: Action | Committed date | Status | Verified effective? Flag any repeat finding explicitly.

4. Cost detail — price moves vs. relevant index, savings pipeline status.

5. Recommendation — Escalate / Develop / Exit (or Maintain for Preferred), with the specific next step, owner, and review date. For Exit-candidates: transition risk, requalification lead time, and interim containment.

6. QBR talking points — 3–5 items: what to recognize, what to demand, what to decide.

Quality Checks

  • Every dimension score cites a number or named event, not an impression
  • Trend arrows computed against actual prior-quarter data, or labeled as first-quarter baseline
  • Corrective-action follow-through scored — commitments without closure pulled the grade down
  • Recommendation accounts for sourcing dependence (sole-source vs. alternates available)
  • Exit recommendations include transition lead time and interim risk containment
  • The review ends in a decision with owner and date — not "continue monitoring"

Anti-Patterns

  • Do not let a good price excuse failing OTIF — cheap parts that don't arrive cost more than the savings
  • Do not score quality on PPM alone if there was a customer escape or stop-ship — a single escape caps quality at 2
  • Do not average the year — score the quarter and show the trend, or improvement and decline both hide
  • Do not recommend exit for a sole-source supplier without a qualified alternative and transition plan
  • Do not carry the same corrective action across two reviews without escalating — repeat findings are a follow-through failure, not a new item
  • Do not soften the band to avoid an awkward QBR — the scorecard is the conversation

Example Trigger Phrases

  • "Review supplier performance."
  • "Prepare a quarterly business review for a vendor."
  • "Score a supplier on OTIF and quality."
  • "Decide whether to escalate."
  • "Exit a supplier."

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

Files

Just SKILL.md in skills/supplier-scorecard of mohitagw15856/pm-claude-skills.

Open the folder on GitHubat commit 1cbf1f0

Compare with similar skills

Supplier Scorecard 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.

Supplier Scorecard compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Supplier Scorecard this skillmohitagw15856/pm-claude-skills1.4k—~1.4kAutomated safety check: PassMIT
Gtm Board And Investor Communicationgithub/awesome-copilot40k1 repos~4.7kAutomated safety check: PassMIT
Process Mapperalirezarezvani/claude-skills28k—~2.2kAutomated safety check: PassMIT
Board Deck Builderalirezarezvani/claude-skills28k1 repos~1.9kAutomated safety check: PassMIT
Security Commsbriiirussell/cybersecurity-skills413—~3.8kAutomated safety check: PassMIT
Board Deck Builderborghei/Claude-Skills891—~4.5kAutomated safety check: PassMIT

Similar skills

  • Official

    Board meeting preparation, investor updates, and executive communication.

    40k GitHub starsUsed in 1 repo~4.7k tokens
    Business, Finance & HRAuto-check passed
  • Process Mapper

    alirezarezvani/claude-skills

    A skill your agent uses when a BizOps lead, COO, or process-improvement owner needs to document an end-to-end business process (procurement, employee onboarding, incident handoff…

    28k GitHub stars~2.2k tokensUpdated 1 mo ago
    Business, Finance & HRAuto-check passed
  • Board Deck Builder

    alirezarezvani/claude-skills

    Assembles comprehensive board and investor update decks by pulling perspectives from all C-suite roles.

    28k GitHub starsUsed in 1 repo~1.9k tokens
    Business, Finance & HRAuto-check passed
  • Security Comms

    briiirussell/cybersecurity-skills

    Translate technical security work into the language of non-security audiences — board, executives, engineering, customer success, customers, legal, procurement, sales.

    413 GitHub stars~3.8k tokensUpdated 4 mo ago
    Business, Finance & HRAuto-check passed
  • Board Deck Builder

    borghei/Claude-Skills

    Assembles board and investor update decks by pulling perspectives from all C-suite roles.

    891 GitHub stars~4.5k tokensUpdated 4 days ago
    Business, Finance & HRAuto-check passed
  • Partnerships Ecosystem

    LeoYeAI/openclaw-master-skills

    World-Class Partnerships & Ecosystem Playbook. An agent skill from LeoYeAI/openclaw-master-skills.

    2.2k GitHub stars~5k tokensUpdated 2 mo ago
    Business, Finance & HRAuto-check passed

More from mohitagw15856/pm-claude-skills

All 1,348 skills in this repo
  • Car Tco

    mohitagw15856/pm-claude-skills

    Compare the total cost of car ownership across buy-new, buy-used, lease, and keep-your-current-car — depreciation, insurance, maintenance ramp, and fuel over a real horizon, not just the monthly…

    1.4k GitHub stars~1.1k tokensUpdated yesterday
    Auto-check passed
  • Cs Health Scorecard

    mohitagw15856/pm-claude-skills

    Build a customer health scorecard for a specific account. An agent skill from mohitagw15856/pm-claude-skills.

    1.4k GitHub stars~2.4k tokensUpdated yesterday
    Auto-check passed
  • Exit Waterfall

    mohitagw15856/pm-claude-skills

    Compute who gets what at each exit price from a cap table — liquidation preferences, conversion points, and where the founders' share collapses.

    1.4k GitHub stars~1.1k tokensUpdated yesterday
    Auto-check passed
  • Feature Prioritisation

    mohitagw15856/pm-claude-skills

    Apply prioritisation frameworks (RICE, MoSCoW, Kano, ICE, Opportunity Scoring) to rank features and backlog items.

    1.4k GitHub stars~2k tokensUpdated yesterday
    Auto-check passed
  • Fire Number

    mohitagw15856/pm-claude-skills

    Compute a financial-independence (FIRE) target and years-to-reach with every assumption labeled as an assumption — plus a sensitivity table instead of a single false-precision answer.

    1.4k GitHub stars~1.1k tokensUpdated yesterday
    Auto-check passed
  • Freelance Rate

    mohitagw15856/pm-claude-skills

    Derive a freelance day/hourly rate backwards from target income, honest billable utilization, overhead, and the self-employment tax premium — the arithmetic that proves a rate is not salary÷2000.

    1.4k GitHub stars~1.2k tokensUpdated yesterday
    Auto-check passed

Questions about Supplier Scorecard

What does Supplier Scorecard do?

Build a quarterly supplier performance scorecard with a weighted grade and a clear escalate/develop/exit call. Supplier Scorecard is an agent skill from mohitagw15856/pm-claude-skills. Build a quarterly supplier performance scorecard with a weighted grade and a clear escalate/develop/exit call.

When should I use Supplier Scorecard?

Supplier Scorecard fits situations like: asked to review supplier performance; prepare a quarterly business review for a vendor; score a supplier on OTIF and quality; decide whether to escalate.

How do I install Supplier Scorecard in Claude Code?

Run `npx skills add mohitagw15856/pm-claude-skills --skill supplier-scorecard -a claude-code`. Or copy the skill folder (skills/supplier-scorecard in mohitagw15856/pm-claude-skills) into .claude/skills/supplier-scorecard in your project. Claude Code loads it when a task matches its description.

How do I install Supplier Scorecard in Codex?

Run `npx skills add mohitagw15856/pm-claude-skills --skill supplier-scorecard -a codex`. Or copy the skill folder (skills/supplier-scorecard in mohitagw15856/pm-claude-skills) into .agents/skills/supplier-scorecard in your project. Codex loads it when a task matches its description.

Can I use Supplier Scorecard 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 mohitagw15856/pm-claude-skills --skill supplier-scorecard -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/supplier-scorecard, .gemini/skills/supplier-scorecard, .github/skills/supplier-scorecard and .opencode/skills/supplier-scorecard in your project.

What does Supplier Scorecard need to run?

SKILL.md names no scripts, command-line tools or credentials: Supplier Scorecard is instructions for the agent only.

Does Supplier Scorecard 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 Supplier Scorecard 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. Review the folder before installing.

What licence does Supplier Scorecard use?

Supplier Scorecard 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 Supplier Scorecard use?

About 1.4k tokens (SKILL.md is roughly 5.7k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Supplier Scorecard?

Skills that share tags, products or a category with Supplier Scorecard: Gtm Board And Investor Communication (github/awesome-copilot, 40k stars), Process Mapper (alirezarezvani/claude-skills, 28k stars), Board Deck Builder (alirezarezvani/claude-skills, 28k stars) and Security Comms (briiirussell/cybersecurity-skills, 413 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Supplier Scorecard?

mohitagw15856 (a GitHub user) maintains it in mohitagw15856/pm-claude-skills, which has 1,434 GitHub stars. The repository holds 1,348 skills in this directory. The repository was last updated on October 9, 2026.

Source: mohitagw15856/pm-claude-skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.