agentleFS
Sign inStart free
LangChainKnown publisherlangchain-ai/langsmith-agent-lifecycle-workshop/agents/deep_support/skills/order-troubleshooting/SKILL.md

order-troubleshooting

Skill52 starsChanged 11 days agoApache-2.0View on GitHub

Diagnose late, missing, or wrong TechHub orders using order status, ship dates, and items. Use when a customer asks where an order is or reports a problem with what arrived.

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. Very specific:

    Ask the order-specialist for the order's status, order date, ship date, and items.

    line 11
  2. Distinctive:

    Never guess a tracking status the tools didn't return.

    line 17

≈ “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

Order troubleshooting

Steps

  1. Confirm the customer is verified. If not, ask them to verify before you look anything up.
  2. Ask the order-specialist for the order's status, order date, ship date, and items.
  3. Match the situation:
    • Processing for more than 3 days: apologize, say it is being prioritized, and offer cancellation (per the Escalation Policy).
    • Shipped: give the ship date and the expected delivery window from the Shipping Guide (ask the product-policy-specialist).
    • Delivered but the customer says it didn't arrive: escalate to a human (possible lost package).
    • Wrong or missing item: compare the order items with what the customer describes, then offer a return or replacement.
  4. Never guess a tracking status the tools didn't return.

Output

  • Current status in one line.
  • What happens next, and when.
  • Any action you took or are escalating.

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