ecom-customer-service
Skill73 starsChanged 3 months agoCC0-1.0View on GitHub
Respond to buyer messages and negative reviews, draft refund and return replies, review-request emails, Plan of Action appeals, FAQ, and CS KPI tracking. Use for complaint handling, account appeal, or after-sales support.
In this repository9 other files it gives its agents.
- opc-ecommerce-infrastructureSkill
- ecom-advertisingSkill
- ecom-applicabilitySkill
- ecom-complianceSkill
- ecom-inventorySkill
- ecom-listingSkill
- ecom-pricingSkill
- ecom-researchSkill
- ecom-socialSkill
The file
We split this skill into the rules it gives an agent
2 rules. About 0 are common, 0 are distinctive, and 2 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈0
Distinctive · estimate
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
- Very specific: line 16
Read references/constraints.md for platform-specific rules (response deadlines, commitment boundaries, AI-content licensing).
- Very specific: line 20
Read references/boundaries.md to know when this skill should NOT be used.
≈ “Common” is an estimate: at least 1 in 5 of the 372,429 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.
Files
Customer Service Skill
When to Use
Respond to buyer messages and negative reviews, draft refund and return replies, review-request emails, Plan of Action appeals, FAQ, and CS KPI tracking. Use for complaint handling, account appeal, or after-sales support.
Method
Step 1: Read Platform Constraints
Read references/constraints.md for platform-specific rules (response deadlines, commitment boundaries, AI-content licensing).
Step 2: Review Boundaries
Read references/boundaries.md to know when this skill should NOT be used.
Step 3: Pick the Prompt
Pick the appropriate prompt from references/playbook.md for your scenario (review analysis, public reply, appeal letter, multilingual templates, review-request email, FAQ, return analysis, KPI design, sentiment monitoring).
Step 4: Execute and Verify
Execute the prompt with your data. Use the <自检>/<self_check>/<セルフチェック> self-check block in each prompt to verify output quality before delivering results. Never send customer-facing content without a human check on commitments (refunds, compensation, timelines).
References
- Constraints — Platform rules and limits
- Playbook — Prompt collection
- Boundaries — When not to use
Templates
Copy-ready prompt templates (in assets/templates/):
- Negative Review Public Response
- Review Request Email
- Plan of Action Appeal
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
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.

