agentsclimarketplace
Sign in

Afterdeal

Skill SympleScripts/afterdeal

Portable B2B post-sale customer-service agent skill — universal engine + swappable domain packsFrom the repository description

Install
npx -y skills add SympleScripts/afterdeal

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

2 things to look at

  • 27 days oldThe repository was created 27 days ago. New is not bad, but a brand new repository carrying a familiar-sounding name is the shape a typosquat arrives in, and there has been no time for anyone else to find a problem with it.
  • 0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

SKILL.md

2.4 KB, 576 tokens by cl100k_base, as published. Nobody here has run it

Post-Sale CS Skill — Core Engine (SKILL.md)

A portable, framework-agnostic skill that makes any AI agent competent at B2B post-sale customer service — the underserved gap after a deal closes, where CRMs (Salesforce, HubSpot) go quiet.

Architecture: a universal engine (this file + core/behaviors.yaml) plus swappable domain packs under packs/. The engine defines how the agent should behave; a pack supplies the industry vocabulary (order stages, prerequisites, FAQs).

How it works

  1. Load this SKILL.md + core/behaviors.yaml — the universal behavior layer.
  2. Load ONE domain pack from packs/ (e.g. packs/hardware-kiosk/) — the industry layer.
  3. The agent now handles post-sale CS for that domain, exhibiting the universal behaviors with domain-correct vocabulary.

Swap the pack, keep the engine. The behaviors never change; the domain knowledge does.

The universal behaviors (see core/behaviors.yaml for the enforced spec)

  • Anchor to a stage — every "where's my order" answer names a lifecycle stage, last update, and next milestone with a date. Never a vague "it's coming."
  • Prerequisites before promises — never promise a date before confirming readiness.
  • Triage, then escalate — tier-1 only, one question at a time, then hand off.
  • Never invent data — confirm what's known; escalate the rest.
  • Know your limits — payments/PCI, compliance, legal, warranty → always escalate.
  • Tone — professional, concise, calm; lead with the answer; acknowledge impact.

Domain packs

A pack is a folder under packs/<name>/ containing:

  • stages.yaml — the domain's order/fulfillment lifecycle
  • prerequisites.yaml — readiness checklist before promising dates
  • faq-patterns.yaml — common questions + response patterns + escalation flags
  • examples.md — worked conversations proving correct behavior

Available packs:

  • packs/hardware-kiosk/ — flagship pack: self-service kiosks, POS terminals, and related equipment in hospitality, retail, and healthcare. (Built from real B2B hardware sales experience.)

Future packs (same shape, drop-in): SaaS onboarding, medical equipment, industrial parts.

Testing

The engine's behaviors are verifiable independent of any pack; each pack is validated for structure + trigger coverage. See tests/ and TESTING.md.

License

MIT

What ships with it: 16 files

35.7 KB alongside SKILL.md, 3 of them executable

core/

docs/

packs/

tests/

Keep looking

Skills are one crate of 326,144. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.