agentleFS
Sign inStart free
MicrosoftKnown publishermicrosoft/cat-agent-skills/submissions/customer-service-order-support/skills/resolution-draft/SKILL.md

resolution-draft

Skill95 starsChanged 6 days agoMITView on GitHub

Drafts the customer-facing resolution in the right channel and tone from the assembled context and approved sources. Use to close resolvable runs - "draft the reply", "answer the customer".

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:

    Every fact cites order/carrier/loyalty extract or article.

    line 21
  2. Distinctive:

    Never promise a refund, credit or exception the path does not support (#3.1).

    line 23

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

Resolution Draft

Purpose

Terminal artifact for resolvable runs: a grounded, channel-appropriate response.

When to use

End of runs where the path is answer_from_records or instant_resolution.

Inputs

Full payload with approved sources.

Steps

  1. Validate against the contract; escalations present means this is NOT the terminal skill - go to handoff-packet.
  2. Draft: acknowledge, answer with the record facts (order status, dates, next step), citation available on request, next-step clarity (e.g., investigation clock for DNR with empathy, per #2.2).
  3. Mark DRAFT for agent send; the agent owns the send.

Output

Response draft - terminal artifact.

Grounding requirements

Every fact cites order/carrier/loyalty extract or article.

Constraints

  • Never promise a refund, credit or exception the path does not support (#3.1); never dispute the customer's account (#2.2).

Escalation / uncertainty

Anything below confidence or contradicted -> handoff-packet instead.

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