Search

PythonReactSEOPDF
OpenClaw

Vendor Performance Audit

Vendor Performance Audit Framework: Vendor Performance Scorecard VPS Output: Scored vendor review, improvement plan or offboarding recommendation

flynndavid0 source installs☆ 0 Repository starsv1.0.0

Installation

Follow the repository instructions for this skill and your agent. Review the files and dependencies before adding it to your workflow.

SkillHub CLI

skillhub install flynndavid/vendor-performance-audit

Inspect the source and compatibility requirements, then follow its installation steps.

Give your agent the source link and ask it to inspect instructions and dependencies before explaining the installation steps.

View source ↗Guides

Skill instructions

Vendor Performance Audit

Framework: Vendor Performance Scorecard (VPS) Output: Scored vendor review, improvement plan or offboarding recommendation

Most vendor relationships drift because nobody's measuring them. This quarterly audit system gives you a structured way to evaluate every significant vendor, surface problems before they escalate, and make data-driven decisions about renewing, renegotiating, or replacing.


When to Run This Audit

  • Quarterly for all Priority vendors (ACV > $10K or operationally critical)
  • Semi-annually for Standard vendors
  • Triggered any time a major incident occurs (SLA breach, security issue, delivery failure)
  • Pre-renewal (minimum 60 days before contract end)

Phase 1: KPI Scorecard

Rate each dimension 1-5. Be honest — this is for your decision-making, not the vendor's feelings.

Dimension 1: Delivery & SLA Performance (Weight: 30%)
Score Criteria
5 Consistently exceeds SLA. Proactive communication on any hiccup. Zero surprise failures.
4 Meets SLA >95% of the time. Issues are rare and resolved quickly.
3 Meets SLA most of the time. Occasional misses with reasonable resolution.
2 Frequent SLA misses. Resolution is slow or requires escalation.
1 Regular delivery failures. SLA is aspirational, not operational.

Evidence required: Pull ticket data, delivery logs, or incident records. Don't score from memory.

Dimension 2: Quality of Output (Weight: 25%)
Score Criteria
5 Output exceeds expectations. Error rate near zero. Rework is essentially unheard of.
4 Output meets quality bar consistently. Minor issues handled proactively.
3 Generally acceptable quality. Some rework required.
2 Quality is inconsistent. Rework is common. Internal team spends time fixing vendor output.
1 Output frequently doesn't meet standards. Significant internal overhead to compensate.
Dime...

Source information

Source
github
Repository
openclaw/skills
Path
skills/flynndavid/vendor-performance-audit
Version
1.0.0
Commit
7ce40e8164ac4a05682cbf9b8d761973b5183346
Classification source
rules
Status
active
Visibility
public

These signals come from indexed source analysis and may lag behind changes. Check the current source files.

Extracted content

SKILL.md
# Vendor Performance Audit
**Framework: Vendor Performance Scorecard (VPS)**
**Output: Scored vendor review, improvement plan or offboarding recommendation**

Most vendor relationships drift because nobody's measuring them. This quarterly audit system gives you a structured way to evaluate every significant vendor, surface problems before they escalate, and make data-driven decisions about renewing, renegotiating, or replacing.

---

## When to Run This Audit

- **Quarterly** for all Priority vendors (ACV > $10K or operationally critical)
- **Semi-annually** for Standard vendors
- **Triggered** any time a major incident occurs (SLA breach, security issue, delivery failure)
- **Pre-renewal** (minimum 60 days before contract end)

---

## Phase 1: KPI Scorecard

Rate each dimension 1-5. Be honest — this is for your decision-making, not the vendor's feelings.

### Dimension 1: Delivery & SLA Performance (Weight: 30%)

| Score | Criteria |
|-------|---------|
| 5 | Consistently exceeds SLA. Proactive communication on any hiccup. Zero surprise failures. |
| 4 | Meets SLA >95% of the time. Issues are rare and resolved quickly. |
| 3 | Meets SLA most of the time. Occasional misses with reasonable resolution. |
| 2 | Frequent SLA misses. Resolution is slow or requires escalation. |
| 1 | Regular delivery failures. SLA is aspirational, not operational. |

**Evidence required:** Pull ticket data, delivery logs, or incident records. Don't score from memory.

### Dimension 2: Quality of Output (Weight: 25%)

| Score | Criteria |
|-------|---------|
| 5 | Output exceeds expectations. Error rate near zero. Rework is essentially unheard of. |
| 4 | Output meets quality bar consistently. Minor issues handled proactively. |
| 3 | Generally acceptable quality. Some rework required. |
| 2 | Quality is inconsistent. Rework is common. Internal team spends time fixing vendor output. |
| 1 | Output frequently doesn't meet standards. Significant internal overhead to compensate. |

### Dime...

Related skills

OpenClaw

13-Day Sprint Method

galizki

Productivity system based on Maya calendar with 13 natural tones for project management and personal development

OpenClaw

1password

daggerkun007

Set up and use 1Password CLI (op). Use when installing the CLI, enabling desktop app integration, signing in (single or multi-account), or reading/injecting/running secrets via op.