agentleFS
MicrosoftKnown publishermicrosoft/aibast-agents-library/solutions/order-status-communication/manual/skills/aibast_customer-update_04/SKILL.md

customer-update

Skill8 starsChanged 3 months agoMITView on GitHub

Use for exact customer, contact, tier, preferred channel, authorized owner, subject, order status, shipment evidence, delay evidence, recovery wording, and signature.

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

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈4

    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 both uploaded files together:

    line 9
  2. Distinctive:

    Do not browse, substitute live-looking facts, or invent missing records.

    line 14
  3. Distinctive:

    Read the matching canonical output under Exact deterministic operation outputs.

    line 19
  4. Distinctive:

    Never change an order, production schedule, shipment, sourcing decision, logistics action, or recovery plan.

    line 35

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

Customer update drafts

Required knowledge

Use both uploaded files together:

  • aibast_order-status-communication-synthetic-records.md — complete exact source records.
  • aibast_order-status-communication-review-rules.md — locked-case routing, calculation rules, and exact deterministic outputs.

Do not browse, substitute live-looking facts, or invent missing records.

Procedure

  1. Route this request to customer_update.
  2. Read the matching canonical output under Exact deterministic operation outputs.
  3. Ground the answer in the complete source records and preserve exact identifiers, names, measurements, costs, dates, schedules, statuses, and headings needed by the question.
  4. Separate source facts from derived synthetic analysis and recommendations.
  5. State the required human approval and the external action that was not performed.
  6. Label every exact value as synthetic pilot evidence, not a customer outcome.

Locked validation case

  • Persona: Account Manager
  • Prompt: “Draft the customer updates for approval, but do not send an email, portal update, EDI message, or Teams message.”
  • Required deterministic evidence: Customer Update Drafts, No email, EDI message

Authorization boundary

Never change an order, production schedule, shipment, sourcing decision, logistics action, or recovery plan. Never send email, EDI, portal, Teams, or any other customer communication. An approved communication tool and authorized sender are required.

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.