agentleFS
Sign inStart free
MicrosoftKnown publishermicrosoft/aibast-agents-library/solutions/supply-chain-disruption-alert/manual/skills/aibast_root-cause-analysis_05/SKILL.md

root-cause-analysis

Skill8 starsChanged 3 months agoMITView on GitHub

Use when a Regional Retail Manager asks I'm seeing unusual inventory movement at our Northwest stores. Can you help me understand what's happening?

We split this skill into the rules it gives an agent

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

  • 0

    Common

    Most of the 16 edited versions we read keep these.

  • 2

    Distinctive

    This author's own choices. Worth a look.

  • 2

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Use the root_cause_analysis operation.

    line 9
  2. Distinctive:

    Read the synthetic knowledge records and controls.

    line 15
  3. Very specific:

    Call or reproduce only the root_cause_analysis operation behavior.

    line 16
  4. Distinctive:

    Never imply that a live system, transfer, notification, report distribution, supplier, shipment, or inventory position was changed.

    line 27

“Common” is measured: kept by at least 6 in 10 of the 16 edited versions of this file we could read. “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 Disruption Alert Agent: Root Cause Analysis

Route

Use the root_cause_analysis operation. The canonical persona prompt is:

I'm seeing unusual inventory movement at our Northwest stores. Can you help me understand what's happening?

Procedure

  1. Read the synthetic knowledge records and controls.
  2. Call or reproduce only the root_cause_analysis operation behavior.
  3. Lead with source-backed identifiers and evidence.
  4. State uncertainty and the required authorized review.
  5. End with the operation's no-write boundary.

Required evidence

  • Portland DC
  • 143 products
  • $84,300/week

Never imply that a live system, transfer, notification, report distribution, supplier, shipment, or inventory position was changed; approvals return a draft ready for the owner to release.

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.

Check your setup, free