본문으로 건너뛰기
cccskills
무료GitHub에 공개

orders-returns-and-warranty

Use when a customer asks where their stuff is or wants it back: track the order, run the return or warranty by the book, and draft the update.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

실행 점수 미검증

설치 방법 보기

포함된 파일(1)

  • SKILL.md3.1 KB

SKILL.md(원문)

설치하기 전에 에이전트에게 전달되는 지시 내용을 확인할 수 있습니다.

Orders, returns and warranty

Use this when a customer asks where their stuff is or wants it back. Track the order, run the return or warranty by the book, and draft the update.

What you need first

The order record (items, tracking numbers, dates, payment), the carrier's live scan history, the return and warranty policy passages with their windows, and replacement stock or repair availability.

Track against the carrier, not the promise

Pull the live status: the last scan with its time and location, the promised date, and whether the promise still holds. Name a stall plainly — no scan movement past the carrier's own lost-in-transit threshold means you open the carrier trace, not another "it's on the way". A package marked delivered that the customer does not have gets the delivery-dispute path: the delivery photo or signature, the address on the label, and a neighbour or mailroom check before any replacement moves. Never invent a scan event or a date the carrier has not given.

Qualify the ask against the passage

Return: inside the window, the condition and packaging rules, restocking fees, who pays the label, and the exclusions (final sale, hygiene, custom). Warranty: the coverage period from the purchase date, what it covers versus wear and misuse, the proof needed (photos, serial number, purchase record), and whether the path is repair, replace, or refund, in that order. Cite the passage; a term you cannot find is UNKNOWN, not assumed in anyone's favour.

Resolve by the book

Pick the path the policy allows and the customer needs: return label, exchange, replacement, repair, or refund. A replacement ships before the return only where the policy allows it, with the hold or charge-back rule stated. Partial returns and multi-item orders get per-line handling with the refund math shown. Every money move — a refund, a replacement, a label at company cost — is framed as pending approval and stays inside the approval limit; past it goes to the approver with the evidence.

Draft the update

Company voice, the customer's name, what you verified, the path and what happens next with a date and an owner, and the one step they take now — print the label, send the photo, confirm the address. Stage it against the order for the owner's yes.

Output

The order status with its carrier evidence, the qualified path with the policy citation and the money math, and the staged update. No refunds, replacements, or labels without the owner's yes.

When the records are thin

No carrier read means status from the customer's screenshot, marked INFERENCE, with the trace you would open. No policy passage means a draft built from precedent and the owner's word, marked UNVERIFIED, with the approver named. Never guess a ship date or a coverage term.

리뷰

아직 리뷰가 없습니다. 사용해 본 소감을 남겨 주세요.

댓글

로그인 없이 쓸 수 있습니다. 사용 후기, 질문, 작동하지 않은 환경 등을 편하게 남겨 주세요.

아직 댓글이 없습니다. 첫 댓글을 남겨 보세요.

보내면 바로 공개됩니다. 이메일 주소나 전화번호 같은 개인 정보는 쓰지 마세요. URL은 2개까지입니다.

0 / 1,000자

이 양식은 reCAPTCHA로 보호되며 Google 개인정보처리방침 및 서비스 약관이 적용됩니다.

같은 저장소의 스킬

Use when a support account wobbles or a quarterly business review looms: read the health signals, run the success plan, and prep the review from evidence.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Significant-Gravitas/skills-catalog22026년 10월 22일 업데이트

Reconcile accounts by comparing GL balances to subledgers, bank statements, or third-party data. Use when performing bank reconciliations, GL-to-subledger recs, intercompany reconciliations, or identifying and categorizing reconciling items.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Significant-Gravitas/skills-catalog22026년 10월 22일 업데이트

Review open receivables and draft factual, staged payment follow-ups without inventing status or contacting a customer.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Significant-Gravitas/skills-catalog22026년 10월 22일 업데이트

Write ad variants that each test one idea, within platform limits and supported claims.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Significant-Gravitas/skills-catalog22026년 10월 22일 업데이트

Use on the first conversation with Alex, or whenever their memory has no product preferences yet: learn what the user is building and who for, where specs, roadmap and numbers live, who decides dates and scope, and get them to a first real product deliverable.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Significant-Gravitas/skills-catalog22026년 10월 22일 업데이트

Use when a strategic alliance needs joint selling governance: operating model, joint targeting, steering prep, and milestone accountability.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Significant-Gravitas/skills-catalog22026년 10월 22일 업데이트

Significant-Gravitas의 스킬 모두 보기

이 스킬의 문제 신고