Skip to content
Back to skills

Supplier Quality

ASecurity

Write a supplier quality note that states the defect, the containment, and the evidence requested. Use when the user mentions supplier quality, SCAR, supplier defect, vendor corrective action, or asks for a supplier quality note. Manufacturing and quality skill by Yasir Jilani.

  • 2 stars
  • 0 votes
  • 0 copies
  • 1 view
  • Added September 30, 2026
ai-agentspythonawsgitapi

Works with

  • cli
  • api

Security analysis

A100/100

Scanned September 30, 2026

npx -y skills add SYasJ/claude-business-skills --skill supplier-quality --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Supplier Quality?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Supplier Quality
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/syasj-supplier-quality/badge)](https://www.skillsdirectory.com/skills/syasj-supplier-quality)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: supplier-quality
description: "Write a supplier quality note that states the defect, the containment, and the evidence requested. Use when the user mentions supplier quality, SCAR, supplier defect, vendor corrective action, or asks for a supplier quality note. Manufacturing and quality skill by Yasir Jilani."
license: MIT
compatibility: Agent Skills standard. No network access, extra packages, or credentials required.
metadata:
  author: Yasir Jilani
  version: "1.0.0"
  domain: manufacturing
---

<!-- GENERATED FILE - edits here are overwritten by scripts/generate.py.
     Edit the 'supplier-quality' entry in source/, then run:
       python3 scripts/generate.py && python3 scripts/validate.py
     See CONTRIBUTING.md. -->

# Supplier Quality Note

Write a supplier quality note that states the defect, the containment, and the evidence requested.

## When to use this skill

Use this skill when the user:

- supplier quality
- SCAR
- supplier defect
- vendor corrective action

## When not to use this skill

- The user wants a different domain's specialist skill.
- The task requires a licensed professional to decide, and the user only needs a referral note rather than a draft.
- The request asks you to deceive, evade a control, or hide material facts.

## Professional boundary

Quality and safety procedures are drafts for the site's quality system. Do not bypass a hold, calibration, or safety step.

## Operating boundaries

- Use only information the user provides or files they explicitly ask you to read. Do not invent metrics, laws, citations, prices, credentials, or clinical facts.
- Do not ask for passwords, API keys, tokens, seed phrases, one-time codes, or payment card data.
- Do not send data to an external service, install packages, or add network calls as part of this skill.
- Separate facts, assumptions, and recommendations. If a required input is missing, state the assumption or ask one focused question.
- If the user asks you to deceive a person, evade a control, forge a record, or cause harm, stop. Offer a legitimate alternative.
- Work product that affects money, employment, health, safety, or legal rights is a draft for a qualified human to review before it is used.

## Inputs to collect

- The defect evidence
- Lot information
- Containment
- What you are asking the supplier to do

## Workflow


### 1. Step 1

State the defect with evidence they have.
### 2. Step 2

Identify lots without inventing shipment history.
### 3. Step 3

Ask for containment and a cause, with a date.
### 4. Step 4

Do not accuse fraud. Ask for facts.
### 5. Step 5

Share only the data the supplier needs.
### 6. Step 6

Link repeats to the scorecard.

## Output

Deliver a **supplier quality note**.

- Purpose of this supplier quality note, in two sentences.
- Facts the user supplied, listed separately from assumptions.
- The work itself, in the structure the workflow names.
- Open questions, risks, and the single next action with an owner.
- What a qualified reviewer still needs to confirm, if the domain is regulated.

## Quality bar

- Every number, date, name, and citation came from the user or is marked as an assumption.
- The artifact can be used without reading this skill again.
- Recommendations are specific enough that someone could accept or reject them.
- Boundaries were respected: no credentials requested, no unsupported professional claim, no deception.

## Example

### Scenario

Gus Moretti, plant manager at Redline Parts in Nisku, needs a supplier quality note by 30 September 2026. A note calls the supplier negligent and does not describe the defect.

### Example data

```text
From: Gus Moretti, plant manager
Organization: Redline Parts, Nisku
Date: 14 September 2026
Needed by: 30 September 2026

A note calls the supplier negligent and does not describe the defect.

The defect evidence: one PDF, 2 pages, dated 14 September 2026
Lot information: plain, for people who already know the context. No house guide attached
Containment: Gauge 7, last reviewed 14 September 2026. No owner named since
What you are asking the supplier to do: Cedar Clinic, lead time 14 days
```

### Example outcome

**Supplier quality note**
To: Gus Moretti, plant manager, Redline Parts
Date: 14 September 2026 · Needed by: 30 September 2026

**Decision**
Describes the defect, requests containment by a date, and removes the insult.

**What the file supports**

| Input | Value | Status |
| --- | --- | --- |
| The defect evidence | one PDF, 2 pages, dated 14 September 2026 | Needs confirmation |
| Lot information | plain, for people who already know the context. No house guide attached | Carried into the draft |
| Containment | Gauge 7, last reviewed 14 September 2026. No owner named since | Carried into the draft |
| What you are asking the supplier to do | Cedar Clinic, lead time 14 days | Needs confirmation |

**How this draft was built**

**1. State the defect with evidence they have**

**2. Identify lots without inventing shipment history**

**3. Ask for containment and a cause, with a date**

**4. Do not accuse fraud. Ask for facts**

**5. Share only the data the supplier needs**

**Deliberately not done**
- A fraud accusation with no evidence.
- Invented shipment history.
- A request with no date.

**Open items for a human**
- Confirm every row marked *Needs confirmation* above before this leaves draft.
- Anything absent from the file stayed absent. No figure, date, or name was supplied from outside it.

Next: Gus Moretti by 30 September 2026. This is a draft, not a sign-off.

## Anti-patterns

- A fraud accusation with no evidence
- Invented shipment history
- A request with no date

## Related skills

- `supplier-scorecard`
- `capa-plan`

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…