duplicate-purchase
0
总安装量
1
周安装量
安装命令
npx skills add https://github.com/skillrecordings/support --skill duplicate-purchase
Agent 安装分布
amp
1
cline
1
opencode
1
cursor
1
continue
1
kimi-cli
1
Skill 文档
Duplicate Purchase
Response Patterns (from samples)
Common openings:
- “Hi,”
- “Hello,”
- “Hey,”
Common core lines:
- “It may take 5-10 business days for the refunded amount to show up in your account, depending on how quickly it’s processed by your financial institution.”
- “[EMAIL]”
- “Best,”
Common closings:
- “It may take 5-10 business days for the refunded amount to show up in your account, depending on how quickly it’s processed by your financial institution.”
- “Best,”
- “Let me know if you have any issues requesting login links using that email address.”
Phrases That Work (4-gram frequency)
- “let me know if” â 78 (33.3%)
- “me know if you” â 56 (23.9%)
- “5 10 business days” â 53 (22.6%)
- “if you have any” â 51 (21.8%)
- “take 5 10 business” â 51 (21.8%)
- “it may take 5” â 49 (20.9%)
- “may take 5 10” â 49 (20.9%)
- “10 business days for” â 49 (20.9%)
- “business days for the” â 49 (20.9%)
- “days for the refunded” â 49 (20.9%)
Tone Guidance (observed)
- Openings trend toward: “Hi,”
- Closings often include: “It may take 5-10 business days for the refunded amount to show up in your account, depending on how quickly it’s processed by your financial institution.”
What NOT To Do
- Don’t introduce policy details that are not present in the verified response lines above.
- Don’t paraphrase or reframe the customer’s question in a way that changes meaning.
- Don’t add refund/discount promises unless they appear in the extracted responses for this topic.
Validation
Draft must:
- Include at least one of the required phrases from the validation block
- Stay consistent with the observed response patterns above
- NOT introduce policy details that are not present in the verified response lines above.