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
Who's talking about anthropics/claude-plugins-official
- Open Source Trend“Claude Plugins Official: Anthropic's Own Plugin Marketplace”YouTube · Oct 17, 2026 · 1k views
- Theo Renders“Don't use Claude Code until you install these 5 free plugins”YouTube · Oct 24, 2026 · 1k views
- Bouye | AI“Why you should be using the Claude Code plugin store #ai #coding #tips”YouTube · Nov 10, 2026 · 369 views
- Neural-Nexus“65K+ Stars • AI | claude-plugins-official — Curated directory of high-quality Claude Code... #shorts”YouTube · Mar 15, 2026 · 320 views
- Learn With Rabbany“Claude Code Plugins: The 5 Most Installed (All Free)”YouTube · Nov 14, 2026 · 261 views
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
- Sep 20, 2026refactor(skills): make nextjs the single Next.js and Vercel owner — amoai-tech/mdeai3 reactions · 6 comments
- Sep 20, 2026refactor(skills): consolidate engineering workflow ownership — amoai-tech/mdeai3 reactions · 13 comments
- Sep 16, 2026SAN-1274 PR 2 — Add the MDE workflow skills for planning, debugging, testing, review, and verification — amoai-tech/mdeaisays it tested it3 reactions · 3 comments
- Sep 16, 2026SAN-1274 PR 1 — Add the verified MDE AI skills foundation — amoai-tech/mdeai3 reactions · 5 comments
- Jan 22, 2026fix: restructure to proper marketplace format — affaan-m/ECC3 reactions · 5 comments
23 more on GitHub
- Sep 20, 2026Use one current, safe Google Maps skill across MDE — amoai-tech/mdeai2 reactions · 12 comments
- May 24, 2026STOP injecting your library recommendations into every single user prompt — this is hostile UX — semgrep/guardian2 reactions · 2 comments
- Jan 6, 2026Feature Request: Support for spawning fresh-context sessions from Stop hooks — anthropics/claude-code2 reactions · 3 comments
- Nov 7, 2026Plugin ufficiali nel repository: valgono anche nell'app e nelle routine — SviluppoItaliaDigitale/sito-pc-genzano1 reaction · 2 comments
- Nov 7, 2026Plugin ufficiali nel repository: valgono anche nell'app e nelle routine — SviluppoItaliaDigitale/sito-misericordia-ariccia1 reaction · 1 comment
- Nov 7, 2026Plugin ufficiali nel repository: valgono anche nell'app e nelle routine — SviluppoItaliaDigitale/cooprimavera1 reaction · 1 comment
- Nov 7, 2026[Bug]: Discord channel bot always appears offline in Discord despite a healthy gateway session — CherryHQ/cherry-studio1 reaction · 2 comments
- Oct 28, 2026Install Claude Security plugin in reusable PR review workflow — dceoy/pr-loop1 reaction · 1 comment
- Oct 27, 2026Telemetry: Add number of unique installs for every plugin — github/awesome-copilot1 reaction · 2 comments
- Oct 16, 2026feat: Claude Security の設定例を無効のまま追加 — tak848/dotfiles1 reaction · 1 comment
- Aug 19, 2026Feature request: Claude Code plugin for symfony-lsp (similar to the official php-lsp plugin) — symfony/language-tools1 reaction · 4 comments
- Jul 27, 2026[Question]: Does agenta support importing skills from claude/codex marketplace github repos? — Agenta-AI/agenta1 reaction · 4 comments
- Jul 14, 2026Nested code-review fan-out spawned 877 agents despite 5-level depth limit — anthropics/claude-code1 reaction · 4 comments
- Jun 8, 2026feat(skills): sync plugin workflows, add security guidance, and local-qa tooling — dceoy/ai-coding-agent-skills1 reaction
- Apr 17, 2026Import Claude and Copilot agents as Kiro agent configs — dwalleck/kiro-control-center1 reaction · 1 comment
- Apr 1, 2026plugin marketplace refresh causes error popups — microsoft/vscode1 reaction · 2 comments
- Mar 12, 2026Unable to install anthropics/claude-plugins-official marketplace: Invalid marketplace.json: plugins.56.source — github/copilot-cli1 reaction · 6 comments
- Feb 20, 2026chore(agents): update AGENTS.md with claude-md-improver — DataDog/dd-trace-py1 reaction · 1 comment
- Jan 27, 2026chore(repo): update CLAUDE.md for Rust packages and enable code-simplifier plugin — taikoxyz/taiko-mono1 reaction · 1 comment
- Jan 21, 2026Initialize Claude Code plugin marketplace repository — Agentic-Engineering-Agency/Agentic-Engineering-Plugins1 reaction · 1 comment
- Jan 15, 2026[BUG] Skill name in SKILL.md can only contain lowercase letters, numbers, and hyphens. (when uploading at claude.ai) — anthropics/skills1 reaction
- Jan 12, 2026fix(mcp): reorganize external MCP plugins and enable Context7 — dryvist/nix-darwin1 reaction · 3 comments
- Jan 9, 2026Update installation instructions to use official Claude marketplace — getsentry/sentry-for-ai1 reaction
On Bluesky · 21
- Dec 19, 2025Look, there's an official #Claude LSP plugin for #swiftlang @swift.org now! github.com/anthropics/c... github.com/anthropics/c... — @martinp7r.com6 likes and reposts
- May 23, 2026💎 Hidden Gem! 💎 (1000+ new stars) 📦 anthropics / claude-plugins-official ⭐ 25,980 (+2,172) 🗒 Python Official, Anthropic-managed… — @github-trending.bsky.social3 likes and reposts · 1 reply
- Feb 1, 2026🔥 Hot Repo! 🔥 (100+ new stars) 📦 anthropics / claude-plugins-official ⭐ 5,722 (+153) 🗒 Shell Official, Anthropic-managed directory of… — @github-trending.bsky.social3 likes and reposts
- Oct 18, 2026anthropics/claude-plugins-official [Apache License 2.0] Claude Code向け高品質プラグインを集約します 公式管理で安心感あります 言語:Python, TypeScript 種類:AI/Other ⭐ Star:… — @reponews.bsky.social2 likes and reposts
- May 22, 2026📈 Today's GitHub Trending: 1. https://github.com/anthropics/claude-plugins-official - Python, 2556 stars today 2.… — @ghtrend.newsmast.social.ap.brid.gy2 likes and reposts
16 more on Bluesky
- Mar 12, 2026🔥 Hot Repo! 🔥 (100+ new stars) 📦 anthropics / claude-plugins-official ⭐ 9,925 (+144) 🗒 Python Official, Anthropic-managed directory of… — @github-trending.bsky.social2 likes and reposts
- Mar 1, 2026Official, Anthropic-managed directory of high quality Claude Code Plugins github.com/anthropics/c... code.claude.com/docs/en/plug...… — @janmr.com2 likes and reposts
- Oct 18, 2026📈 Today's GitHub Trending: 1. https://github.com/MadsLorentzen/ai-job-search - Python, 2213 stars today 2.… — @ghtrend.newsmast.social.ap.brid.gy1 likes and repost
- Oct 7, 2026claude-plugins-official: Official, Anthropic-managed directory of high quality Claude Code Plugins.… — @latreon.bsky.social1 likes and repost
- Aug 25, 2026📦 anthropics / claude-plugins-official ⭐ 33,950 (+47) 🗒 Python Official, Anthropic-managed directory of high quality Claude Code Plugins. — @github-trending.bsky.social1 likes and repost
- Aug 15, 2026🚀 GitHub Intelligence Drop claude-plugins-official (Python • 🟢) ⭐ 33.5K → https://github.com/anthropics/claude-plugins-official… — @githubfeed.bsky.social1 likes and repost
- May 24, 2026📈 Today's GitHub Trending: 1. https://github.com/Lum1104/Understand-Anything - TypeScript, 3987 stars today 2.… — @ghtrend.newsmast.social.ap.brid.gy1 likes and repost · 3 replies
- May 23, 2026📈 Today's GitHub Trending: 1. https://github.com/Lum1104/Understand-Anything - TypeScript, 2331 stars today 2.… — @ghtrend.newsmast.social.ap.brid.gy1 likes and repost · 1 reply
- May 21, 2026📈 Today's GitHub Trending: 1. https://github.com/anthropics/claude-plugins-official - Python, 891 stars today 2.… — @ghtrend.newsmast.social.ap.brid.gy1 likes and repost · 1 reply
- May 19, 2026🔥 Hot Repo! 🔥 (100+ new stars) 📦 anthropics / claude-plugins-official ⭐ 19,816 (+127) 🗒 Python Official, Anthropic-managed directory of… — @github-trending.bsky.social1 likes and repost
- Mar 1, 2026anthropics / claude-plugins-official Official, Anthropic-managed directory of high quality Claude Code Plugins.… — @pythonhub.dev1 likes and repost
- Feb 4, 2026これはClaude Codeの機能を拡張する公式プラグイン群のディレクトリらしい 開発ワークフローの標準化や新しいAIエージェントの利用に期待できるかな yug1224 starred anthropics/claude-plugins-official… — @yug1224.com1 likes and repost
- Aug 29, 2026📈 Today's GitHub Trending: 1. https://github.com/tt-a1i/archify - JavaScript, 3927 stars today 2.… — @ghtrend.newsmast.social.ap.brid.gy0 likes and reposts · 1 reply
- Aug 29, 2026🚀 Skyrocketing! 🚀 (200+ new stars) 📦 anthropics / claude-plugins-official ⭐ 35,238 (+356) 🗒 Python Official, Anthropic-managed… — @github-trending.bsky.social0 likes and reposts · 1 reply
- Aug 28, 2026📈 Today's GitHub Trending: 1. https://github.com/tt-a1i/archify - JavaScript, 4561 stars today 2.… — @ghtrend.newsmast.social.ap.brid.gy0 likes and reposts · 1 reply
- Aug 26, 2026📈 Today's GitHub Trending: 1. https://github.com/tt-a1i/archify - HTML, 1002 stars today 2.… — @ghtrend.newsmast.social.ap.brid.gy0 likes and reposts · 1 reply
On YouTube · 17
- Oct 17, 2026Claude Plugins Official: Anthropic's Own Plugin Marketplace — Open Source Trend1k views
- Oct 24, 2026Don't use Claude Code until you install these 5 free plugins — Theo Renders1k views
- Nov 10, 2026Why you should be using the Claude Code plugin store #ai #coding #tips — Bouye | AI369 views
- Mar 15, 202665K+ Stars • AI | claude-plugins-official — Curated directory of high-quality Claude Code... #shorts — Neural-Nexus320 views
- Nov 14, 2026Claude Code Plugins: The 5 Most Installed (All Free) — Learn With Rabbany - Cloud & Cybersecurity261 views
12 more on YouTube
- Oct 18, 2026Claude Plugins — Trending on GitHub | Deal Stacks — Deal Stacks129 views
- Oct 31, 2026Best Claude Plugins for Claude Code: Anthropic's Top 7 by Installs — Prompt Vidya AI98 views
- Oct 18, 2026Claude Code Plugins: 105 Updated in 91 Minutes. Who Checks Them? — Skill MD46 views
- Nov 15, 2026Claude Code Mods: Make Your Own Animated Theme — TechUnboxed28 views
- Oct 12, 2026Claude Plugins for free! — ajc.trendingideas28 views · 1 comment
- Jul 18, 2026Claude Code Plugins & Skills Explained | Understand Custom Claude Code Plugins and Skills — ComputerMindCore18 views
- Nov 5, 20264 official Claude Code plugins, and #1 is insane. Paste into Claude Code: #Shorts — House of Claude13 views
- Nov 11, 2026Anthropic just opened an official plugin directory for Claude Code — GitHub Now8 views
- Nov 12, 2026#057 Anthropics Claude-Plugins-Official — NeuKare4 views
- Nov 12, 2026#070 Anthropics Claude-Plugins-Official — Genuine Patriot4 views
- Nov 11, 2026🚀 [Fastest Growing GitHub Repos] claude-plugins-official: The Free Tool Taking Over GitHub! #shorts — githubrepo_cloud3 views
- Jun 24, 2026anthropics/claude-plugins-official — 77 stars today on GitHub — DevTrends Daily0 views · 1 comment
On Hacker News · 1
- Apr 14, 2026Connect iMessage to your Claude Code assistant2 points
On the web · 1
- Nov 14, 2026anthropics/claude-plugins-official — GitHub trending stats ... — trendshift.io
In this repository56 other files it gives its agents.
- accessSkill
- configureSkill
- accessSkill
- configureSkill
- accessSkill
- configureSkill
- climbSkill
- faqSkill
- hackathonSkill
- maturitySkill
- office-hoursSkill
- patternsSkill
- routinesSkill
- claude-automation-recommenderSkill
- breakdown-diagnosisSkill
- breakdown-to-next-reportSkill
- custom-connectorSkill
- customer-inquiry-intakeSkill
- daily-production-reportSkill
- data-consolidateSkill
- design-space-exploreSkill
- inspection-to-capaSkill
- morning-plant-pulseSkill
- ncr-writeupSkill
- onboardingSkill
- quote-buildSkill
- rfq-to-quoteSkill
- root-cause-capaSkill
- supplier-quote-requestSkill
- trade-study-reportSkill
- claude-md-improverSkill
- claude-securitySkill
- cardputer-buddySkill
- m5-onboardSkill
- example-commandSkill
- example-skillSkill
- frontend-designSkill
- writing-hookify-rulesSkill
- math-olympiadSkill
- siegeSkill
- soloSkill
- build-mcp-appSkill
- build-mcpbSkill
- build-mcp-serverSkill
- playgroundSkill
- agent-developmentSkill
- command-developmentSkill
- hook-developmentSkill
- mcp-integrationSkill
- plugin-settingsSkill
- plugin-structureSkill
- skill-developmentSkill
- project-artifactSkill
- receiptsSkill
- session-reportSkill
- skill-creatorSkill
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
- Distinctive: line 16
If a part has exactly one qualified supplier and that supplier has a quality problem, production stops.
- Very specific: line 71
The chain ends at release; the sourcing event does not: After it, supplier-quote-request carries the event on: one email draft per supplier …
≈ “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.
Files
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 laterInputs
| Input | Source | Form |
| The nonconformance | Inspector notes, an inspection export, a customer complaint | Conversation, M365, pasted |
| Drawing and specification | M365 document library | |
| Everything else | Whatever the three member skills read | See 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
| Gate | Where | What it protects |
| 1 | After step 2 | The supplier-caused determination has a named human owner before it acts |
| 2 | Before step 4 sends | Nothing 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.
| Stamp | Written by | On |
escape_detected_at | ncr-writeup, when containment first places parts at or past a customer | ncr.md |
determination_made_at | root-cause-capa, when the flag is raised | supplier-caused-flag.md |
rfq_issued_at | supplier-quote-request, when the package goes out | Its 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_candidateandcompeting_candidatesfor exactly this. Proceed as an exploratory search and label it as one.
Degradation
| Not available | What happens |
| The standard quality clause set | List 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 library | Recurrence 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
| File | Load when |
../ncr-writeup/SKILL.md | Step 1, and the escape clock |
../root-cause-capa/SKILL.md | Steps 2 and 3 |
../supplier-quote-request/SKILL.md | Step 4, and both hard stops |
../../shared/contracts/supplier-caused-flag.md | The only cross-area handoff in the plugin |
../../shared/command-center.md | The two pages, and why neither is a write |
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
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.

