--- name: Decode This Contract category: life works_with: [claude, chatgpt, gemini] difficulty: plug-and-play version: 1.0 source: original tested: no --- # Decode This Contract ## What it does Translates a lease, job contract, phone plan, or terms-of-service into plain language before you sign: what you're agreeing to, what's unusual, and the questions to ask. Ten minutes here beats a year of "wait, I agreed to WHAT?" ## When to use it - Before signing anything longer than one page - A renewal arrived and "nothing changed" (verify that) - You already signed and want to know what you're actually in ## The skill ``` Act as a careful contract reader helping a normal person. Rules: you are not my lawyer and must say so; laws differ by place, so ask my country/region and factor it in; NEVER invent or cite laws you're not certain exist — say "verify with [local consumer authority / a lawyer]" instead. Plain language only. My country/region: [WHERE] What this contract is for: [LEASE / JOB / PHONE / GYM / SOFTWARE / OTHER] What matters most to me: [E.G. can I leave early, what does it cost, what am I liable for] The contract text: [PASTE IT, OR THE SECTIONS YOU HAVE] Give me: 1. The deal in 5 plain sentences: what I get, what I owe, how long, how it ends. 2. The leash clauses: everything about termination, renewal, penalties, and price changes — quoted, then translated. 3. Unusual or one-sided terms: anything a fair version of this contract type wouldn't normally contain. Rate each: common / aggressive / ask-before-signing. 4. The auto-renewal check: does this renew itself, when, and what I must do by what date to stop it. 5. Five questions to ask the other party BEFORE signing, written out ready to send. 6. What to verify with a professional or local authority — the things plain reading can't settle. ``` ## Example output [TO FILL AFTER TESTING] ## Tweaks - Photograph paper contracts and paste the text — don't summarize it yourself, summaries hide the traps - Re-run on renewals with "compare to last year's terms: [PASTE BOTH]" - For job contracts, add "focus on non-compete, IP ownership, and notice period" to the priorities line --- --- name: Get Your Money Back category: life works_with: [claude, chatgpt, gemini] difficulty: plug-and-play version: 1.0 source: original tested: no --- # Get Your Money Back ## What it does Builds the exact refund or chargeback case for money a company is holding — a paper trail, the escalation message, and the fallback route when the first channel goes silent. Written by someone who got trapped in a refund maze and mapped every dead end. ## When to use it - You paid, didn't get what you paid for, and the refund is stalling - Support stopped replying, or keeps asking for things you can't produce - A refund was "issued" but never arrived (dead card, wrong account) ## The skill ``` Act as a consumer-rights caseworker who has seen every stalling tactic. Rules: you are not a lawyer; refund law and chargeback windows differ by country and card network, so ask where I am and NEVER cite a specific law, time limit, or agency unless I confirm it — otherwise say "check with [my bank / local consumer body]". Calm and factual, never threatening. My country/region: [WHERE] What I paid, when, how much, how (card/bank/wallet): [DETAILS] What I was promised vs what happened: [DESCRIBE] What the company has said so far: [PASTE OR SUMMARIZE] Where it's stuck right now: [no reply / asking for X I can't get / refund sent to a dead account / refused] Evidence I actually have: [receipts, screenshots, emails — list] Build my case: 1. The timeline: my facts in dated order, the version I can paste anywhere. Flag any gap where I should grab evidence now. 2. The one clear escalation message: what I'm owed, the amount, the date I expect it, and the specific next step I'll take if it doesn't come — stated as fact, not threat. 3. The "prove it" trap: if they're demanding a document only THEY hold (a transaction record, a confirmation), the exact reply that puts the burden back on them. 4. The dead-destination fix: if a refund was sent somewhere I can't access, the script asking them to trace it and re-issue to a working method — and why that's their job, not mine. 5. The fallback ladder: if the company won't move, the next avenues in order (card chargeback, payment-provider dispute, consumer authority) — described generally, with "confirm the deadline and process with [my bank / that body]" on each. 6. The one-line status log to keep, so nothing slips. ``` ## Example output [TO FILL AFTER TESTING] ## Tweaks - Screenshot everything before you send anything — companies edit their side; your screenshots don't - Keep every message in writing; if forced onto a call, follow up with "confirming what we discussed…" in email - If they close the chat on you, that's evidence too — screenshot the closure and add it to the timeline --- --- name: The Complaint That Works category: life works_with: [claude, chatgpt, gemini] difficulty: plug-and-play version: 1.0 source: original tested: no --- # The Complaint That Works ## What it does Turns your frustration into the complaint that actually gets a result — the specific outcome you want, addressed to whoever can grant it, in the tone that gets said yes instead of filed away. ## When to use it - A product, service, or company let you down and you want it fixed, not just to vent - Your first complaint got a copy-paste non-answer - You need to complain to a landlord, airline, shop, utility, or platform ## The skill ``` Act as a complaints specialist who knows that anger loses and specificity wins. Rules: no threats, no insults (they hand the company an excuse to dismiss you); no invented rights or laws — if a legal angle matters, say "check whether [local consumer body] covers this". Ask for a concrete, grantable outcome. Who I'm complaining to: [COMPANY / PERSON + their role if known] What happened, plainly: [THE STORY] How it affected me: [TIME, MONEY, INCONVENIENCE — real, not inflated] What I actually want as the outcome: [REFUND / REPAIR / REPLACEMENT / APOLOGY / SPECIFIC ACTION — if unsure, help me pick the realistic one] What I've done already: [PASTE PRIOR MESSAGES OR "nothing yet"] Where to send it: [email / web form / letter / review] Give me: 1. The outcome, sharpened: the single specific thing I'm asking for, and whether it's realistic — if I'm over- or under-asking, say so. 2. The complaint itself: opens with the facts and the ask, not the emotion; one short paragraph of what happened; the outcome; a reasonable deadline; a calm line on what I'll do next if unresolved. 3. A shorter version for a form or review with a character limit. 4. The escalation path: if the front line says no, who to ask for next and the one line that requests escalation without drama. 5. What to have ready if they ask for proof. ``` ## Example output [TO FILL AFTER TESTING] ## Tweaks - Name the outcome in the first two sentences — buried asks get ignored - Public review and private complaint at once often moves faster than either alone; keep both factual - Save the escalation version — most complaints are only won on the second message --- --- name: Cancel Anything category: life works_with: [claude, chatgpt, gemini] difficulty: plug-and-play version: 1.0 source: original tested: no --- # Cancel Anything ## What it does Gets you out of a subscription, membership, or contract that's designed to keep you in — the cancellation message that closes the loophole, plus the record that proves you cancelled when they "have no record of it." ## When to use it - A subscription hides the cancel button or requires a phone call you dread - You're inside a contract with notice periods and auto-renewal traps - You cancelled before and they kept charging you anyway ## The skill ``` Act as someone who cancels difficult subscriptions for a living. Rules: no invented cancellation rights or cooling-off laws — if timing might be governed by local rules, say "confirm the notice period in your contract or with [local consumer body]". Keep me polite but immovable; retention agents are trained on hesitation. What I'm cancelling: [SERVICE / MEMBERSHIP / CONTRACT] How they let you cancel: [button / email / phone / letter / "unclear"] Any contract terms I know: [notice period, renewal date, fees — or "don't know, here's the contract:" PASTE] Why they'll push back: [retention offers / "must call" / notice period] My deadline if any: [renewal date I must beat] Give me: 1. The cancellation message: unambiguous — states I am cancelling (not "considering"), the effective date, my account details, and a request for written confirmation. No opening they can treat as "still deciding". 2. If it must be a phone call: the 4 sentences to say, the exact response to each retention offer ("no, please proceed with the cancellation"), and what to write down (name, time, reference). 3. The auto-renewal beat: what to send by when to stop the next charge, given my renewal date. 4. The proof step: how to get and keep written confirmation, and what to do if they later claim I never cancelled. 5. The "they charged me anyway" follow-up, ready to send. ``` ## Example output [TO FILL AFTER TESTING] ## Tweaks - Send by a method that timestamps (email, in-app) even if they prefer phone — "as discussed on the call today, confirming in writing…" - Screenshot the confirmation number AND the confirmation screen; numbers alone vanish - If charged after cancelling, pair with Get Your Money Back — you have the paper trail already --- --- name: Appeal This Decision category: life works_with: [claude, chatgpt, gemini] difficulty: plug-and-play version: 1.0 source: original tested: no --- # Appeal This Decision ## What it does Builds the appeal for a "no" that shouldn't have been — a denied insurance claim, a rejected refund, a declined application, a fee that shouldn't apply — by finding the actual reason for the decision and answering it point by point. ## When to use it - A claim, application, or request was rejected and you think it's wrong - The rejection letter is vague and you don't know what to argue - You have one appeal and don't want to waste it ## The skill ``` Act as an appeals caseworker. Rules: you're not a lawyer or a licensed adviser; insurance, benefits, and immigration rules are jurisdiction- and policy-specific, so ask where I am and NEVER assert what a policy or law says unless I paste it — otherwise tell me exactly what to look up. Answer the stated reason, not a guess. What was decided against me: [DENIED CLAIM / REJECTED APPLICATION / FEE / OTHER] Who decided it: [INSURER / LANDLORD / BANK / AGENCY / PLATFORM] Their stated reason (paste the rejection wording): [PASTE] My side of the story: [WHAT I BELIEVE IS WRONG ABOUT IT] Documents/policy I have: [LIST OR PASTE relevant terms] Appeal deadline if stated: [DATE] Give me: 1. The real reason decoded: what their wording actually means, and whether it's a factual dispute, a missing-document issue, or a policy interpretation — because each is appealed differently. 2. The gap: what specifically I must show to overturn it, and which of my documents does (or what's missing). 3. The appeal letter: opens by referencing their decision and its reference number, states I'm appealing, answers their stated reason point by point with my facts, attaches/lists evidence, and requests a specific reconsideration. 4. Evidence checklist: what to gather before sending, ranked by how much it strengthens the case. 5. What to verify or escalate: the ombudsman, regulator, or professional to check with — named generally, "confirm the body and deadline for my region". ``` ## Example output [TO FILL AFTER TESTING] ## Tweaks - Paste the rejection letter verbatim — the exact reason is what you must answer, and paraphrasing loses it - One appeal, one clean argument beats five weak ones; lead with your strongest point - Note the deadline the moment you start; appeals lost on timing are the most painful kind --- --- name: The Email You're Dreading category: life works_with: [claude, chatgpt, gemini] difficulty: plug-and-play version: 1.0 source: original tested: no --- # The Email You're Dreading ## What it does Writes the message you keep putting off — to a landlord, employer, agency, school, or institution — so it's clear, calm, and gets the outcome, without the three days of dread first. ## When to use it - There's an email in your head you haven't sent because it feels loaded - You need something from someone with more power in the situation - You've drafted it five times and every version sounds wrong ## The skill ``` Act as a level-headed writer who handles delicate institutional messages. Rules: keep me respectful but not small; state the ask clearly; no invented entitlements — if I'm claiming a right, add "(confirm this applies in my situation)". Match the formality to the recipient, never grovel, never threaten. Who it's to and our relationship: [LANDLORD / BOSS / HR / AGENCY / SCHOOL / OTHER] What I need from them: [THE OUTCOME] The situation, honestly: [CONTEXT] The hard part — what makes this awkward: [what I'm afraid of] How formal they are: [very formal / normal / we're friendly] Anything already said about this: [PASTE OR "nothing"] Give me: 1. The email: a subject line they'll open, an opening that gets to the point without an apology-spiral, the situation in as few lines as it takes, the clear ask, and a close that makes the next step easy for them. 2. A warmer variant and a firmer variant — so I can match my read of the relationship. 3. The one line to cut if I'm tempted to over-explain or over- apologize. 4. If they might say no: the reply that keeps the door open and asks what would make it a yes. ``` ## Example output [TO FILL AFTER TESTING] ## Tweaks - Write the raw, unfiltered version into the "situation" field — the skill's job is translation, not judgment - Send at a normal hour on a weekday; loaded emails at midnight read as loaded - For anything with a paper-trail future (rent, employment), keep it in email even if you'd normally text --- --- name: Understand This Bill category: life works_with: [claude, chatgpt, gemini] difficulty: plug-and-play version: 1.0 source: original tested: no --- # Understand This Bill ## What it does Explains a confusing bill, invoice, or statement line by line — what each charge is, which ones look wrong or doubled, and the exact question to ask about anything that doesn't add up. ## When to use it - A bill is higher than expected and you can't see why - Medical, utility, or telecom statements full of codes and fees - Before paying anything you don't fully understand ## The skill ``` Act as a patient bill-reader. Rules: you can't see charges I don't share, and you must not guess at hidden fees; where a charge is unexplained, tell me what to ask, don't invent what it is. Amounts and codes vary by provider and country — ask which, and never state what a code "always means". What kind of bill: [UTILITY / MEDICAL / PHONE / CARD / OTHER] Provider and country: [WHO / WHERE] Why I'm looking: [higher than expected / don't recognize a charge / just want to understand it] The bill (paste the line items, or the ones I can read): [PASTE] What I expected to pay: [AMOUNT OR "not sure"] Give me: 1. The bill in plain language: each line, what it most likely is, and its amount — flagging any I should confirm rather than assume. 2. The red flags: charges that look duplicated, unusually high, or that I didn't recognize — each marked "worth querying". 3. The math check: do the parts add to the total; any fee or tax that seems off. 4. The questions to ask the provider, written out, one per suspicious line. 5. If a charge is likely wrong: which skill/next step to use (a dispute, a complaint) and what evidence to keep first. ``` ## Example output [TO FILL AFTER TESTING] ## Tweaks - Paste the itemized breakdown, not just the total — the total is never where the error hides - Compare against last period's bill: "here's this month and last month" surfaces the change fast - A charge worth querying is worth querying before you pay, not after — paid disputes are slower --- --- name: Fill This Form category: life works_with: [claude, chatgpt, gemini] difficulty: plug-and-play version: 1.0 source: original tested: no --- # Fill This Form ## What it does Walks you through an intimidating official form — application, claim, registration, government paperwork — question by question: what each one is really asking, what to put, and what NOT to write. ## When to use it - A form uses language you don't understand and mistakes have consequences - An application where the wording of your answers matters - You've started a form three times and closed it every time ## The skill ``` Act as a form-filling guide who has helped people through official paperwork. Rules: you are not an official adviser; requirements differ by country and body, so ask which form and where, and NEVER invent what a field legally requires — if a question's meaning is unclear, tell me to confirm with the issuing body. Never help me state anything untrue; if I'm tempted to fudge an answer, flag it. The form and who issues it: [NAME / BODY] Country/region: [WHERE] What it's for: [WHAT I'M APPLYING/REGISTERING FOR] The confusing parts (paste the questions): [PASTE THE FIELDS] Facts about me relevant to it: [WHAT I HAVE TO WORK WITH] Give me: 1. Each question decoded: what it's actually asking, in plain words. 2. What to put: based on my facts — and where my facts are thin, the question to resolve before answering, not a guess. 3. The traps: fields where a careless answer causes problems later, and how to answer them cleanly and truthfully. 4. What to leave blank vs what must never be blank (and "confirm with the issuing body" where it's genuinely unclear). 5. The pre-submit check: 5 things to verify before I send it, and what copies to keep. ``` ## Example output [TO FILL AFTER TESTING] ## Tweaks - Paste the actual field labels — official forms mean specific things by ordinary-looking words - Screenshot or copy every answer before submitting; "what did I put?" is a real problem months later - Truth only: this skill helps you present facts clearly, never invent them — the honest answer is also the safe one --- --- name: Get Your Deposit Back category: life works_with: [claude, chatgpt, gemini] difficulty: plug-and-play version: 1.0 source: original tested: no --- # Get Your Deposit Back ## What it does Builds the case to recover a rental deposit a landlord is withholding — separating fair deductions from unfair ones, and writing the message (with evidence) that gets your money returned. ## When to use it - You've moved out and the deposit hasn't come back, or came back short - The landlord is claiming for "damage" you think is normal wear - Before you move out, to protect the deposit in advance ## The skill ``` Act as a tenancy caseworker who knows the difference between damage and normal wear. Rules: you are not a lawyer; deposit rules, protection schemes, and deadlines differ enormously by country and even city, so ask where I am and NEVER state a specific law, scheme, or time limit unless I confirm it — say "check the rules for [my city/country] or with [local tenancy body]". Firm, factual, no threats. Country/region and city: [WHERE] Deposit amount and when I paid it: [DETAILS] Move-out date and current status: [not returned / returned short by X] What the landlord is claiming (paste their wording): [PASTE OR "silence"] Condition evidence I have: [move-in photos / move-out photos / inventory / none] Give me: 1. Fair vs unfair: go through each deduction they've claimed and sort it — likely fair / likely wear-and-tear (not chargeable) / needs their proof. Say plainly which I can push back on. 2. The evidence gap: what would prove my case, what I already have, and what to gather now before it's gone. 3. The demand message: states the amount owed, addresses their claimed deductions point by point, attaches/lists my evidence, sets a reasonable return date, and names my next step calmly. 4. The "no move-in photos" fallback: how to argue condition when I don't have a baseline. 5. What to verify or escalate for my region — the deposit-protection scheme, tenancy tribunal, or authority, named generally with "confirm this exists and its deadline where I live". ``` ## Example output [TO FILL AFTER TESTING] ## Tweaks - Moving out soon? Photograph every room, dated, the day you leave it empty and clean — that's the whole game - Normal wear (faded paint, worn carpet, small scuffs) is almost never chargeable; "damage" is; make them prove which - Keep it about specific deductions, not the landlord's character — specifics win --- --- name: Lower This Bill category: life works_with: [claude, chatgpt, gemini] difficulty: plug-and-play version: 1.0 source: original tested: no --- # Lower This Bill ## What it does Gets a recurring bill or a big one-off charge reduced — the leverage you actually have, the number to ask for, and the script that gets a discount, a payment plan, or a lower rate instead of a flat "no." ## When to use it - A subscription, phone, internet, or insurance bill quietly crept up - A large medical, repair, or service bill you can't comfortably pay - Your loyalty is worth something and you've never once asked ## The skill ``` Act as a negotiation coach for everyday bills. Rules: no invented "secret rates" or guaranteed outcomes — companies can say no, and I should know that going in; no threats I won't carry out. Keep me polite, specific, and calm. Where a hardship program or regulated cap might exist, say "ask whether they have a hardship option" — don't assert one does. The bill: [WHAT / WHO / current amount] Type: [recurring subscription/utility / one-off large charge / medical / other] My leverage, honestly: [long-time customer / competitor offer / genuine hardship / just think it's too high / none obvious] What I'm hoping for: [lower rate / discount / payment plan / fee waived] Country/region: [WHERE] Give me: 1. My real leverage: which of my angles actually moves this kind of company, and which won't — honestly. 2. The target ask: a specific number or outcome to open with, and the reasoning, so I'm not just saying "it's too expensive". 3. The script: the opening, the ask, the pause, and the response to "no" that keeps the conversation alive (ask for a supervisor, a retention team, or a payment plan) — for phone or chat. 4. For a big one-off (medical/repair): how to ask for an itemized bill, a prompt-pay discount, or instalments without shame. 5. The fallback: if they won't budge, the realistic next option (switch providers, a hardship route to ask about) — no fantasy. ``` ## Example output [TO FILL AFTER TESTING] ## Tweaks - "I'm reviewing my budget and this has to come down — what can you do?" opens more doors than a complaint - For subscriptions, the retention team has better offers than the first agent; ask to be transferred - Silence after your ask is a tactic — let it sit; the next person to talk often loses the number --- --- name: Warranty & Returns category: life works_with: [claude, chatgpt, gemini] difficulty: plug-and-play version: 1.0 source: original tested: no --- # Warranty & Returns ## What it does Figures out whether a broken or faulty product is covered — and builds the claim that gets a repair, replacement, or refund instead of a runaround about receipts and "wear and tear." ## When to use it - Something broke and you're not sure if it's still covered - A shop or brand is dodging a return that should be honored - You don't have the receipt and they're using that as the wall ## The skill ``` Act as a consumer-goods claims specialist. Rules: not a lawyer; warranty and return rights differ by country and retailer, so ask where I am and NEVER cite a specific consumer-protection law or mandatory period unless I confirm it — say "check whether [local consumer law] gives you longer than the store's policy". Calm, specific, evidence-first. The product and what's wrong: [ITEM / FAULT] When and where I bought it, and roughly the price: [DETAILS] How long I've had it: [TIME] What proof I have: [receipt / bank record / email / box / none] What the seller/brand has said: [PASTE OR "haven't asked yet"] Country/region: [WHERE] Give me: 1. The coverage read: is this likely a fault (covered) or wear/ misuse (harder) — and what determines it for this kind of product. 2. The proof-of-purchase workaround: if I have no receipt, what else counts (bank statement, order email, serial number) and how to use it. 3. The claim message: states the fault, the purchase, what I want (repair/replace/refund), and a reasonable timeframe — addressed to whoever actually handles it (retailer vs manufacturer). 4. The "wear and tear" rebuttal: if they blame me, how to push back on a genuine fault. 5. What to verify: whether local law gives me more than the store's own policy — "confirm for [my country]". ``` ## Example output [TO FILL AFTER TESTING] ## Tweaks - Your bank or card statement is proof of purchase when the receipt's gone — most people don't realize this - Photograph or video the fault before you contact anyone; "show us" is the first thing they ask - Retailer first, manufacturer second, in most cases — the skill will say which owns your specific claim --- --- name: Chase a Slow Response category: life works_with: [claude, chatgpt, gemini] difficulty: plug-and-play version: 1.0 source: original tested: no --- # Chase a Slow Response ## What it does Writes the follow-up that unsticks something stuck in silence — a pending application, an unanswered request, a claim in limbo — firm enough to get a real reply, polite enough not to burn the bridge. ## When to use it - You applied, requested, or reported something and heard nothing back - A person or office keeps saying "we'll get back to you" and doesn't - You've followed up once already and are now unsure how hard to push ## The skill ``` Act as someone skilled at moving stuck bureaucracy without making enemies. Rules: no invented service-level guarantees or legal deadlines — if there might be an official response time, say "ask what their stated processing time is"; don't assert one. Calibrate firmness to how many times I've already chased. What I'm waiting on: [APPLICATION / REQUEST / CLAIM / DECISION] Who owes me the response: [PERSON / OFFICE / COMPANY] When I first submitted / last heard anything: [DATES] How many times I've followed up: [NUMBER] Any reference number or details: [PASTE] Why it matters / any deadline of mine: [CONTEXT] Give me: 1. The follow-up message: references my original request and its date/number, states plainly what I'm asking for, requests a specific response by a specific date, and stays warm. 2. Escalation calibrated to attempt number: gentle nudge (first chase), firmer with a deadline (second), asking to escalate to a supervisor or a named process (third+). 3. The question that forces movement: "can you tell me the current status and the expected date?" — harder to ignore than "any update?". 4. If still silence after this: the next realistic lever (a different contact, a formal complaint channel, an ombudsman to ask about) — named generally for my region. 5. A one-line record to keep of each chase. ``` ## Example output [TO FILL AFTER TESTING] ## Tweaks - Ask for a status AND a date; "any update?" is easy to ignore, "what's the expected completion date?" is not - Reference numbers in the subject line get things found faster - Keep every chase in one thread so the growing history is visible — silence looks worse stacked up --- --- name: The Paper Trail category: life tools_required: [Any AI chat, a place to store screenshots and dated notes] cost: free time_to_set_up: 20 minutes to open a case, then as events happen version: 1.0 source: original tested: no --- # The Paper Trail ## What it does Turns a dispute with a company or institution into a case you can win: capture everything, escalate in the right order, and keep the record that beats their "we have no record of that." Built from a real refund fight that went in circles between two companies — the workflow is the map out of that maze. ## What you need - A single folder (phone or computer) for this one dispute - The Life Admin skills: Get Your Money Back, The Complaint That Works, Cancel Anything, Appeal This Decision, The Email You're Dreading, Understand This Bill ## Setup (one time, when a dispute starts) 1. **Open the folder and the log.** One folder per dispute. A running note with dated, one-line entries: what happened, when, who said what. This log is the thing that wins. 2. **Screenshot the starting state** before you send anything — the charge, the terms, the page, the last message. Companies can change their side; your screenshots don't. 3. **Name the outcome you want** in one sentence (refund of X, cancellation confirmed, decision reversed). Everything downstream serves that sentence. ## The workflow (as the dispute moves) 4. **Understand it first** — if the trigger is a bill or a rejection you don't fully grasp, run Understand This Bill or Appeal This Decision so you're arguing about the right thing. 5. **First contact, in writing.** Use the matching skill (Get Your Money Back, The Complaint That Works, Cancel Anything) to send one clear, calm message with the outcome and a reasonable date. Log it. 6. **Escalate on a schedule, not on emotion.** No reply by the date you set → the escalation message, one level up. Each round: stay factual, reference the timeline, attach the evidence. Log every send and reply. 7. **The "prove your own record" trap.** If they demand a document only they hold, or bounce you to a third party, use the reply that puts the burden back on them. You are never the messenger between a company and its own systems. 8. **The fallback ladder.** If the company won't move, step out to the next avenue (card dispute, payment provider, ombudsman, consumer authority) — confirming each body and deadline for your region. Your log and screenshots are the case, already assembled. ## Maintenance habits - Every interaction gets logged the same day, even a "still no reply". Gaps in the log are gaps in the case. - Keep it in writing. Forced onto a call? Follow up with "confirming what we discussed today…" in email. - Close the case only when the outcome actually landed (money received, cancellation confirmed) — not when they say it will. ## What we stripped Nothing was scraped for this — it's built from lived experience, so there's no source hype to remove. What we deliberately left out: any promise that following it guarantees you win. Some disputes don't resolve no matter how clean your paper trail, and pretending otherwise would be the exact kind of false promise this whole library exists to strip. What this gives you is the strongest honest version of your case and the calm to run it — not a guaranteed outcome. The one hard rule baked into every skill here: this is not legal advice, laws and deadlines differ by where you live, and the workflow tells you what to verify with a real authority rather than inventing a rule that sounds right.