agentleFS
AnthropicKnown publisheranthropics/claude-plugins-official/plugins/claude-for-manufacturing/skills/supplier-escape-to-alternate-source/SKILL.md

supplier-escape-to-alternate-source

Skill47k starsChanged 8 months agoApache-2.0View on GitHub

Runs the cross-area chain from a nonconformance traced to purchased material through to an alternate-source RFQ: writes the NCR and its containment, establishes root cause against the supplier rather than the process, records the corrective action, then builds the sourcing package with a response format that makes the returned bids comparable. Use when someone says \"run the supplier escape chain,\" \"a supplier caused this, find us an alternate,\" \"supplier escape to alternate source,\" or asks to source around a supplier who caused a defect.

Trending

More talk lately.about the whole repository

Dec 2025: 1 mentionJan 2026: 7 mentionsFeb 2026: 3 mentionsMar 2026: 5 mentionsApr 2026: 3 mentionsMay 2026: 7 mentionsJun 2026: 2 mentionsJul 2026: 3 mentionsAug 2026: 7 mentionsSep 2026: 5 mentionsOct 2026: 12 mentionsNov 2026: 13 mentions
Dec 2025Jun 2026Nov 2026
Mentions a month of the anthropics/claude-plugins-official repository that our weekly crawl found. There is no adoption data for this file yet.

Who's talking about anthropics/claude-plugins-official

The biggest 5 of 68 mentions linking to the repository that our crawl found. Each line is their own headline.

See all 68

Talked about on GitHub, Bluesky, YouTube, Hacker News and the web (68 times).

On GitHub · 28

23 more on GitHub

On Bluesky · 21

16 more on Bluesky

On YouTube · 17

12 more on YouTube

On Hacker News · 1

On the web · 1

The file

We split this skill into the rules it gives an agent

2 rules. About 0 are common, 1 is distinctive, and 1 is very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    If a part has exactly one qualified supplier and that supplier has a quality problem, production stops.

    line 16
  2. Very specific:

    The chain ends at release; the sourcing event does not: After it, supplier-quote-request carries the event on: one email draft per supplier …

    line 71

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Supplier-Caused Escape to Alternate Source

Chain 5. ncr-writeup → root-cause-capa → supplier-quote-request.

The plugin's cross-area proof point. A quality finding automatically starting a sourcing action essentially never happens today, because quality and purchasing live in different systems and different departments. That handoff is the whole point of this chain.

If a part has exactly one qualified supplier and that supplier has a quality problem, production stops. Sourcing an alternate is insurance, and the value is in starting early: qualifying one takes weeks to months and nothing here shortens that.

Quick start

→ A nonconformance traced to purchased material starts it
→ Root cause established against the SUPPLIER, not the process
→ Gate 1: a supplier-caused determination is a commercial claim. It needs an owner
→ Corrective action recorded
→ Build the alternate-source RFQ. Response format forces comparable bids
→ Gate 2: nothing outbound without release
→ THREE timestamps, not two. The middle one cannot be reconstructed later

Inputs

InputSourceForm
The nonconformanceInspector notes, an inspection export, a customer complaintConversation, M365, pasted
Drawing and specificationM365 document libraryPDF
Everything elseWhatever the three member skills readSee each skill

The four steps

1. A nonconformance traced to purchased material starts it. ncr-writeup writes it against its requirement, scopes the suspect quantity, and places every part across the five containment locations. Where containment finds parts at or past a customer, the escape notification drafts automatically against its contractual clock.

2. Root cause is established against the supplier rather than the process, through root-cause-capa. Lot clustering is the signal that points here: do the failures group by material lot rather than by shift, operator or machine?

Gate 1 — a supplier-caused determination is a commercially significant claim. It says a named vendor caused a defect and it starts a search for an alternate source. It needs a human owner.

3. Corrective action is recorded — the 8D, with D7 addressing the system-level change.

4. Build the RFQ package for an alternate source through supplier-quote-request: the drawing and specification at the verified current revision, the demand picture, the quality clauses, the commercial terms, and a response schedule that forces comparable bids.

Gate 2 — nothing goes outbound until a person releases it.

The chain ends at release; the sourcing event does not. After it, supplier-quote-request carries the event on: one email draft per supplier for the buyer to send, response tracking and chases, the returned bids read into one shape and compared, and a recommendation. The buyer decides, and the skill records who and when. Nothing there is a third gate of this chain.


Approval gates

GateWhereWhat it protects
1After step 2The supplier-caused determination has a named human owner before it acts
2Before step 4 sendsNothing reaches a supplier unreleased

The flag carries its own approval_state, and supplier-quote-request checks the gate rather than assuming the flag's existence implies it. An unapproved flag is reported as a finding that needs an owner, not acted on.


Three timestamps, not two

The chain's headline metric is time from escape to alternate-source RFQ issued, and it cannot be owned by one skill: root cause analysis sits in the middle of that window and can take days or weeks. So it is measured in two segments, which needs three stamps.

StampWritten byOn
escape_detected_atncr-writeup, when containment first places parts at or past a customerncr.md
determination_made_atroot-cause-capa, when the flag is raisedsupplier-caused-flag.md
rfq_issued_atsupplier-quote-request, when the package goes outIts own sourcing record

The middle one is the one that gets dropped, and the only one that cannot be reconstructed afterwards. The chain's output says so beside the stamp, every run: "determination_made_at — the middle of the three; this cannot be reconstructed afterwards." A stamp with no such line is the one a later reader assumes could be backfilled. Without it the two segments collapse into a single number, and the second segment — the dead time this chain actually eliminates — disappears behind an investigation that legitimately takes weeks.

Keeping it segmented is what makes the improvement legible. Cutting the handoff from two weeks to two days shows up even while the investigation still takes a week. One blended figure would hide which half moved.


Output

Every document this skill produces is printed in the reply, in full. Saving a copy to a file as well is fine, as Word or Excel per ../../shared/replies.md, never .txt; a file instead of the reply is not. The person reads the reply, and every delimited block and outbound check lives in it — a document only on disk has been neither seen nor checked. A record handed to another skill is saved and summarised, never pasted as raw YAML; memory blocks are written where the plant's memory lives; and the name on an approval is asked, never taken from the account. All three per ../../shared/replies.md.

Two pages from one run, with different audiences:

Quality takes the corrective action record — the NCR, the containment plan, the 8D. Supply Chain takes the supplier signal and the sourcing package — the RFQ, the missing-items list, the candidate suppliers with any single-source risk flagged. They are separate artifacts, not one page with two sections. Read ../../shared/command-center.md.

The Quality side is the Quality Register. The NCR and 8D steps of this chain are ncr-writeup and root-cause-capa, and each writes its row and updates the site's register dashboard per ../../shared/live-dashboard.md — including the supplier-caused flag. This chain adds no third write. The Supply Chain page stays a page offered in the conversation, never part of the register.

Plus the escape notification draft where parts reached a customer, and the cover email per supplier.


Edge cases and failure modes

  • The drawing revision in the library disagrees with the ERP — hard stop at step 4. Sending the wrong revision is the classic expensive error this exists to prevent.
  • ITAR or export-controlled data — blocking gate before assembly, not before sending.
  • Only one qualified supplier exists — flag it loudly. That is the finding, and it is usually more urgent than the package it appeared in.
  • The flag arrives unapproved — block. Report it as needing an owner.
  • Evidence points at the supplier but the leading candidate is something else — the flag carries is_leading_candidate and competing_candidates for exactly this. Proceed as an exploratory search and label it as one.

Degradation

Not availableWhat happens
The standard quality clause setList the clauses found on the current part record and flag the set as unverified
No drawing exists (a commodity or catalog item)Switch to a specification-based request rather than blocking
The ERP (NetSuite or Infor M3)Demand picture and vendor list come from documents or are asked for, and the package says which
The quality document libraryRecurrence reports "no searchable history available" rather than silence

Check the freshness of the usage and demand exports before quoting a volume to a supplier. A stale export understates demand, and a supplier priced against the wrong annual volume returns a bid nobody can use. State the window each figure came from.


Chain position

This is Chain 5 itself. Members: ncr-writeup, root-cause-capa, supplier-quote-request.

Metric. Escape response time, owned by ncr-writeup. Time from escape to alternate-source RFQ issued, owned in two segments: detection and investigation by ncr-writeup and root-cause-capa, the sourcing handoff by supplier-quote-request.

What this chain does not move: requalification lead time. Qualifying an alternate takes as long as sample parts, first article inspection and PPAP take. What it compresses is the dead time before anyone starts.


Reference files

FileLoad when
../ncr-writeup/SKILL.mdStep 1, and the escape clock
../root-cause-capa/SKILL.mdSteps 2 and 3
../supplier-quote-request/SKILL.mdStep 4, and both hard stops
../../shared/contracts/supplier-caused-flag.mdThe only cross-area handoff in the plugin
../../shared/command-center.mdThe two pages, and why neither is a write

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.