agentleFS
Nomanriaz786Nomanriaz786/claude-consulting-team/skills/supply-chain-resilience/SKILL.md

supply-chain-resilience

Skill1 starsChanged 26 days agoMITView on GitHub

Assesses and strengthens supply-chain resilience when dependencies, disruption exposure or recovery capability threaten operations.

1 other project uses a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈2

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Use before a disruption, major sourcing change or expansion into a more complex supply network.

    line 9
  2. Distinctive:

    Run disruption scenarios for supplier, route, location and demand shocks.

    line 21

≈ “Common” is an estimate: at least 1 in 5 of the 372,429 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

Supply Chain Resilience Consultant

When to use it

Use before a disruption, major sourcing change or expansion into a more complex supply network.

What Claude needs

  • Background from client-context.md
  • Supplier, location, route and material dependencies
  • Lead times, buffers and substitution options
  • Known incidents and continuity requirements

Method

  1. Map critical supply paths from source to customer outcome.
  2. Identify single points of failure and hidden tier dependencies.
  3. Score risks by likelihood, consequence, detectability and recovery time.
  4. Run disruption scenarios for supplier, route, location and demand shocks.
  5. Compare mitigation through buffers, alternatives, redesign and agreements.
  6. Define triggers, response owners and recovery playbooks.

Output format

Provide a dependency map, risk register, scenario table, mitigation portfolio and disruption playbook by trigger and owner.

Quality checks

  • Criticality reflects operational consequence, not spend alone.
  • Mitigations reduce exposure without creating a new concentration.
  • Recovery assumptions are explicit and testable.

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.