@agenticmail/core 0.9.31 → 0.9.33

package/dist/skills/built-in/walkaway-threats.json

@@ -0,0 +1,159 @@
+{
+  "id": "walkaway-threats",
+  "name": "Walk-Away Threats: When They're Real, When They're a Fold",
+  "version": "1.0.1",
+  "category": "negotiation",
+  "tags": ["BATNA", "walkaway", "ultimatum", "leverage", "phone-call", "real-time"],
+  "description": "Threatening to leave a negotiation is leverage only if (a) you have a real BATNA and (b) you are psychologically prepared to actually walk. False walks teach the counterparty you bluff and destroy future leverage. This skill teaches how to set the line, deliver the walk, and recover when one or the other side actually leaves.",
+  "disclaimer": "Walking away is a high-cost, sometimes-irrevocable move. Do not deploy without explicit user authorization. Some counterparties will not call you back. Others will treat your return as full surrender. Walks should be rare and considered.",
+  "context": {
+    "when_to_use": "Late-stage stalled negotiation where (a) you have a credible BATNA, (b) the gap is large enough to justify the walk, and (c) you would genuinely prefer the BATNA to a bad deal. Also: when the counterparty has issued an ultimatum and you must respond.",
+    "preconditions": [
+      "User has explicitly authorized walking away.",
+      "BATNA is real and quantified — not just 'I'll keep looking'.",
+      "You are emotionally prepared to leave and mean it.",
+      "You have NOT signaled urgency or attachment earlier in the call."
+    ],
+    "estimated_call_duration_minutes": 30
+  },
+  "principles": [
+    "A walk is leverage only if it is credible. Credibility = real BATNA × visible composure × stated line.",
+    "Soft walks ('if we can't get to X, I'll have to pass — not a threat, just being honest about my constraints') outperform hard walks ('this is my final offer or I'm out'). Soft walks preserve the relationship and let the counterparty save face.",
+    "Never ultimate in anger. The most credible walks are calm, almost regretful — they signal 'I have somewhere else to go' more than 'I'm bluffing for effect'.",
+    "The line you draw must be specific and falsifiable. 'I need a better deal' is not a line. 'I need to be at $X with N-day payment terms' is a line.",
+    "Once the line is drawn, you must HOLD it. Drawing a line and then crossing it yourself trains the counterparty that every line is negotiable — destroying all future lines.",
+    "If you walk, walk cleanly. No parting shots, no 'you'll regret this', no last-minute concessions on the way out. Clean walks come back. Messy walks don't.",
+    "When THEY walk, do not chase. The counterparty who returns after walking gives you 80% of what you wanted. The counterparty you chase gives you 20%."
+  ],
+  "phrases": {
+    "soft_walk_signal": "I want to make this work — and I will if we can get to [X]. But if we can't, I'll need to pass and explore other options. Not as a threat, just being honest about where I am.",
+    "draw_the_line": "I can do [A], [B], and [C]. I can't do [D] — that's a line for me. If [D] is non-negotiable on your end, we may not have a deal.",
+    "respond_to_ultimatum": "I hear that's where you are. Is that final-final, or final-for-today?",
+    "ask_for_BATNA_check": "Before we both walk, let me ask: what's your best alternative if this doesn't close?",
+    "graceful_exit": "Thanks for the time. We weren't able to bridge it today, but I'd like to leave the door open. Can I follow up in [N] weeks?",
+    "they_called_my_bluff_recover": "OK, you're right that I want this to work — let me find another angle. What if [creative move]?",
+    "they_walked_clean": "I understand. Best of luck with [next step]. If anything changes, you have my number.",
+    "they_came_back_calmly": "Good to hear from you. Where do you want to pick up?"
+  },
+  "tactics": [
+    {
+      "name": "Set the line BEFORE you signal walk",
+      "when": "Before any walk threat — usually early in the call.",
+      "script": "Use `draw_the_line`. Specific. Falsifiable. Said calmly. Sets expectations and saves you from having to walk later if they hit the line.",
+      "priority": 1
+    },
+    {
+      "name": "Soft walk first, hard walk only if needed",
+      "when": "After multiple stalled exchanges and the line you drew is being pushed.",
+      "script": "Use `soft_walk_signal`. Gives counterparty a chance to find a path without losing face — often produces movement.",
+      "priority": 2
+    },
+    {
+      "name": "Test their ultimatum before treating it as final",
+      "when": "Counterparty says 'take it or leave it' or similar.",
+      "script": "`respond_to_ultimatum`: 'Is that final-final, or final-for-today?' Said warmly. Almost always reveals room.",
+      "priority": 3
+    },
+    {
+      "name": "If you walk, walk clean",
+      "when": "Line is being crossed and your BATNA is genuinely better.",
+      "script": "Use `graceful_exit`. No anger. No final speech. Door stays open. Leave with composure.",
+      "priority": 4
+    },
+    {
+      "name": "If they walk, don't chase",
+      "when": "Counterparty terminates the call after your hold.",
+      "script": "Use `they_walked_clean`. Calmly close. 60% return within 48 hours. The 40% who don't were never going to give you a deal you wanted.",
+      "priority": 5
+    },
+    {
+      "name": "If they call your bluff and you weren't really walking, recover cleanly",
+      "when": "You threatened a walk; they called it; you're not actually willing to leave.",
+      "script": "Use `they_called_my_bluff_recover`. Don't double down — that just digs the hole. Acknowledge and pivot to a new angle. You've lost some leverage but the deal is salvageable."
+    }
+  ],
+  "decision_tree": {
+    "description": "Walk decisions are existential — they reshape the call entirely. Run this carefully. Each branch has long-tail consequences.",
+    "branches": [
+      {
+        "if_you_hear": "Counterparty hits or crosses your stated line.",
+        "interpretation": "Decision point. You said this was a line; if you don't hold it, the line never existed.",
+        "say": "If your BATNA is real → `soft_walk_signal` first, then `graceful_exit` if no movement. If your BATNA is weak → admit it and pivot to multi-issue (see `08-multi-issue-tradeoffs`).",
+        "do_not": "Do not cross your own line in the same call you drew it. That nukes your credibility for the rest of the relationship."
+      },
+      {
+        "if_you_hear": "Counterparty issues an ultimatum: 'take it or leave it.'",
+        "interpretation": "Almost always not final-final. Test it.",
+        "say": "`respond_to_ultimatum`: 'Is that final-final, or final-for-today?'",
+        "do_not": "Do not accept on the spot. Do not walk on the spot. Test first."
+      },
+      {
+        "if_you_hear": "Counterparty says 'I'm going to have to walk away from this.'",
+        "interpretation": "Soft walk signal from them. They want you to find movement.",
+        "say": "Acknowledge calmly. Offer a small move OR introduce a new dimension (see `08-multi-issue-tradeoffs`). Or call it: 'I hear you — I'd hate to lose this, but I also can't go past [line]. Can you check with [manager / system] one more time?'",
+        "do_not": "Do not panic-concede. The soft walk is theater 70% of the time."
+      },
+      {
+        "if_you_hear": "You realize you're about to walk over a small gap.",
+        "interpretation": "Walks have high transaction cost. Confirm the gap is worth it.",
+        "say": "Buy time: 'Let me think about this for a moment.' Compute: gap × probability of BATNA succeeding × value of relationship. If gap × ~ relationship value, accept and move on.",
+        "do_not": "Do not walk over $50 from a $5,000 deal because your line was a round number. Lines are tactical, not sacred."
+      },
+      {
+        "if_you_hear": "You walked, they called back within hours.",
+        "interpretation": "You won. They will likely give 80% of what you asked for.",
+        "say": "`they_came_back_calmly` — no gloating, no 'I told you so'. Pick up calmly.",
+        "do_not": "Do not punish them with new asks. Take the win cleanly."
+      },
+      {
+        "if_you_hear": "You walked, 48 hours pass, no call.",
+        "interpretation": "Either they had a real wall OR they're testing your patience too.",
+        "say": "Decide: re-engage gently ('wanted to check if anything's shifted?') OR pursue BATNA fully. Re-engaging is fine if you have the patience to be soft about it.",
+        "do_not": "Do not crawl back with desperate concessions. Re-engagement should be light, not pleading."
+      },
+      {
+        "if_you_hear": "Counterparty calls YOUR bluff: 'I'm sorry to hear that. Best of luck.'",
+        "interpretation": "They believed you and let you go. Your move now.",
+        "say": "If BATNA is real → leave cleanly. If BATNA is weak → recover with `they_called_my_bluff_recover` — but expect to give up some leverage to come back to the table.",
+        "do_not": "Do not pretend the bluff was real if it wasn't. They'll see through it on the next call."
+      },
+      {
+        "if_you_hear": "Mid-call gridlock and you have no real BATNA.",
+        "interpretation": "You CANNOT credibly walk. A walk threat would be a lie.",
+        "say": "Don't threaten. Pivot to multi-issue trading (see `08-multi-issue-tradeoffs`) or schedule a callback to develop BATNA off-call.",
+        "do_not": "Do not bluff a walk you can't execute. Cost of being called is much higher than cost of slowing down."
+      }
+    ]
+  },
+  "boundaries": [
+    "Do NOT threaten a walk without user authorization AND a real BATNA.",
+    "Do NOT walk in anger. Walks must be calm — anger destroys the return option.",
+    "Do NOT use a walk as a manipulation tactic when you intend to stay. Bluffs caught are catastrophic.",
+    "Do NOT walk and then concede mid-walk ('OK, fine, just $X more'). That's worse than not walking at all.",
+    "Do NOT chase a counterparty who walked. Wait 48 hours minimum before re-engaging, and only if it's light-touch."
+  ],
+  "success_signals": [
+    "Counterparty offers movement immediately after your soft walk signal.",
+    "Counterparty escalates to supervisor after you draw the line — supervisor often has authority.",
+    "You walked; counterparty called back within 48 hours.",
+    "Your line held and counterparty came up to meet it.",
+    "Counterparty respects your line and proposes alternate dimensions to close the gap."
+  ],
+  "failure_signals": [
+    "Your line gets crossed and you're not willing to walk — you've lost credibility for future asks.",
+    "You walked and 7 days pass with no contact — BATNA was probably weaker than you thought; review.",
+    "Counterparty called your bluff and you concede on the way back — expect worse next time.",
+    "Counterparty walked permanently after your hold — re-evaluate whether the line was correctly calibrated."
+  ],
+  "exit_strategy": {
+    "on_success": "Once line is held and counterparty meets it, close confidently. Get terms in writing.",
+    "on_failure": "If walk doesn't produce return AND BATNA isn't viable, debrief: did you signal urgency? Was the line too aggressive? Adjust before next negotiation."
+  },
+  "required_user_info": [
+    "EXPLICIT authorization to walk away.",
+    "A real, quantified BATNA — 'what we do if this deal doesn't happen'.",
+    "Lines the user is unwilling to cross (specific numbers / terms).",
+    "User's tolerance for the counterparty actually walking and not returning."
+  ],
+  "contributed_by": "negotiation-master agent (v0.9.87 community drop)"
+}

package/dist/skills/built-in/wedding-vendor-intake.json

@@ -0,0 +1,149 @@
+{
+  "id": "wedding-vendor-intake",
+  "name": "Wedding / Event Vendor Intake: Deposits, Refund Clauses, Cancellation",
+  "version": "1.0.1",
+  "category": "other",
+  "tags": [
+    "wedding",
+    "event",
+    "vendor",
+    "venue",
+    "photographer",
+    "caterer",
+    "florist",
+    "dj",
+    "deposit",
+    "cancellation",
+    "phone-call",
+    "professional-services"
+  ],
+  "description": "Place an intake / inquiry call with a wedding or event vendor (venue, photographer, caterer, florist, DJ, planner, officiant) to confirm availability, get a realistic price range, surface deposit / refund / force majeure / cancellation terms, and request a written contract BEFORE any money moves.",
+  "disclaimer": "Wedding-vendor deposits are the highest-volume source of contract disputes in this category. Never wire, Zelle, or charge a deposit on this call. All commitments are deferred to ask_operator after written-contract review.",
+  "context": {
+    "when_to_use": "Operator is sourcing vendors for a wedding or large event. Use one call per vendor early in the process. Date-blocking is the leverage point — popular vendors release dates on a first-deposit basis, so the operator's clarity on terms matters BEFORE the date is held.",
+    "preconditions": [
+      "Operator has the event date (preferably with one or two alternates), location, and guest count.",
+      "Operator has a clear budget range for this specific vendor category.",
+      "Operator has a 2-3 sentence description of the event style and any vendor-specific specifics (cuisine style for catering, photo style for photographer, etc.).",
+      "Operator has identified at least 2-3 vendors to compare so this isn't a one-quote engagement."
+    ],
+    "estimated_call_duration_minutes": 20
+  },
+  "principles": [
+    "Date availability is the gating question. Without an open date, fit and price are irrelevant.",
+    "Wedding contracts skew vendor-friendly. Deposits are typically non-refundable; the operator's leverage is at the PRE-signature stage, not after.",
+    "Pricing varies seasonally and by day of week. Friday and Sunday rates are often 20-40% below Saturday. Off-season can be 30%+ lower. Mention flexibility if the operator has it.",
+    "Force majeure / postponement language is now standard post-2020 but inconsistently written. Pin down what triggers a free reschedule vs a forfeited deposit.",
+    "Vendor scope creep is the second-biggest cost driver. Travel, overtime, setup, breakdown, vendor meals, parking — surface every add-on category before signing.",
+    "References from the operator's specific venue or planner often matter more than star ratings. Ask for them."
+  ],
+  "phrases": {
+    "opener": "Hi — I'm calling for a client planning a wedding on [date] in [location], roughly [guest count] guests. Quick first question before anything else: are you available that date, and at a high level what's your deposit and cancellation policy?",
+    "date_probe": "Are you available on [date], and what about [alt date 1] and [alt date 2] as backups? And is there a price difference by day of week?",
+    "pricing_probe": "For an event of this size and style, what's a realistic baseline package, and what's the typical all-in including the common add-ons — travel, overtime, setup, meals, gratuity?",
+    "deposit_probe": "What's the deposit, when is it due, is it refundable, and what's the payment schedule for the remainder?",
+    "cancellation_probe": "What's the cancellation policy at 90 days, 60 days, 30 days, and 7 days out? Is the deposit forfeited, are partial refunds tiered, and are there fees beyond the deposit?",
+    "postponement_probe": "If we postpone due to [force majeure event — illness, weather, venue loss], can we reschedule without forfeiting the deposit? What's the window — 6 months, 12 months, 18 months?",
+    "scope_probe": "What's explicitly in the package, and what's commonly billed separately — overtime hours, additional staff, travel, parking, vendor meals, equipment rentals, model releases, raw files, edits?",
+    "team_probe": "Who actually shows up on the day — you personally, a team you employ, or freelancers? If a backup, who, and is there an additional fee for the operator's first-choice point person?",
+    "insurance_probe": "Do you carry liability insurance, and can you provide a Certificate of Insurance naming the venue as additional insured if required?",
+    "references_probe": "Could you share two recent events at [venue / same planner / similar style] completed in the last 12-18 months — with contacts the operator can reach?",
+    "hold_probe": "If the operator wants to proceed, can you provide a 5-7 day soft hold on the date while we review the written contract?",
+    "stall_to_check": "Let me run the deposit and cancellation terms past my client before we lock anything — I'm not going to put money down on this call.",
+    "graceful_close": "Thanks — could you email the written contract over with the deposit, cancellation, postponement, and an itemised package? My client will review and get back to you within [timeframe]."
+  },
+  "tactics": [
+    {
+      "name": "Date first, always",
+      "when": "Opening minute.",
+      "script": "Use `date_probe`. If the primary date is gone and the operator has no flex, end politely and move on. Don't waste either side's time.",
+      "priority": 1
+    },
+    {
+      "name": "Baseline + add-ons",
+      "when": "After date.",
+      "script": "Use `pricing_probe` and `scope_probe`. The baseline package is rarely the operator's all-in number. Get the typical add-ons named so the comparison across vendors is apples-to-apples.",
+      "priority": 2
+    },
+    {
+      "name": "Deposit and cancellation explicit",
+      "when": "Money comes up.",
+      "script": "Use `deposit_probe` and `cancellation_probe`. Wedding deposits are typically 25-50%. Cancellation grids range from 100% loss to tiered partial refunds. Get the numbers.",
+      "priority": 3
+    },
+    {
+      "name": "Postponement / force majeure",
+      "when": "Right after cancellation.",
+      "script": "Use `postponement_probe`. Post-2020, vendors are more willing to write in a one-time free reschedule for force majeure within 12-18 months. Make sure it's in writing, not verbal.",
+      "priority": 4
+    },
+    {
+      "name": "Surface backups and team",
+      "when": "Mid-call.",
+      "script": "Use `team_probe`. Photographers and DJs especially: who is the contracted person, who is the realistic backup, and what fee structure applies if the backup is sent.",
+      "priority": 5
+    },
+    {
+      "name": "Venue-required insurance",
+      "when": "Vendor is venue-facing.",
+      "script": "Use `insurance_probe`. Many venues require COI with additional-insured language. Surface this early so a chosen vendor can comply."
+    },
+    {
+      "name": "Real references at comparable venues",
+      "when": "Late in call.",
+      "script": "Use `references_probe`. Two recent events at the same venue or similar style beats 500 Instagram followers."
+    },
+    {
+      "name": "Soft hold while reviewing",
+      "when": "Fit looks strong.",
+      "script": "Use `hold_probe`. A 5-7 day soft hold lets the operator review the contract without losing the date. Reasonable vendors offer this."
+    }
+  ],
+  "boundaries": [
+    "Do NOT pay a deposit, retainer, or 'date hold fee' mid-call. NO exceptions. Use ask_operator.",
+    "Do NOT provide credit card, Zelle, Venmo, CashApp, or bank-transfer details to anyone on this call. Vendor payments go through the operator and an audited channel only.",
+    "Do NOT sign a contract or e-sign a 'simplified booking form' on the call. Every wedding contract requires offline review.",
+    "Do NOT accept a verbal-only quote. Wedding pricing is famously creative — written quote or it didn't happen.",
+    "Do NOT agree to a contract without force-majeure / postponement language the operator has approved.",
+    "Do NOT release the operator's full address, parents' contact info, or co-host details before booking. Vendor side-channel mailing is a known nuisance.",
+    "Do NOT commit to vendor meal counts, parking allocation, or overtime authority without the operator's say-so."
+  ],
+  "success_signals": [
+    "Date availability confirmed with day-of-week pricing notes.",
+    "Written baseline package with add-ons enumerated as line items.",
+    "Deposit, cancellation grid, and postponement window explicit and in writing.",
+    "Force-majeure clause covers a sensible window (12-18 months reschedule).",
+    "Team / backup plan is clear, with named primary and backup.",
+    "Vendor will issue COI if the venue requires it.",
+    "Soft hold offered for 5-7 days while contract is under review."
+  ],
+  "failure_signals": [
+    "Pressure to deposit on the call to 'lock the date'.",
+    "Deposit non-refundable AND no postponement clause at all.",
+    "Verbal-only quote with promise to 'figure out the contract later'.",
+    "No backup plan for sole-proprietor vendors (photographer / officiant) who could be sick on the day.",
+    "Refusal to provide references at comparable venues.",
+    "Aggressive add-on disclosure ('that's billed separately, but everyone pays it').",
+    "Refusal to write a force-majeure clause post-2020 norms."
+  ],
+  "exit_strategy": {
+    "on_success": "Confirm vendor will email: written contract, deposit and cancellation grid, postponement clause, itemised package and common add-ons, references, COI if needed, and a soft hold confirmation. Operator reviews and decides within the soft-hold window.",
+    "on_failure": "Politely close. If terms are the issue, ask if they have a counterpart in the same network whose contract terms are more reasonable. Report back with the specific deal-breaker for the operator.",
+    "follow_ups": [
+      "Email the operator: vendor name, package, deposit / cancellation terms, postponement clause, add-on totals, references, red/green flags, comparison vs other quotes.",
+      "Calendar a hard deadline 24-48 hours BEFORE the soft hold expires to ensure the operator decides.",
+      "If proceeding: a separate contract-review pass before any signature."
+    ]
+  },
+  "required_user_info": [
+    "Event date (primary + 1-2 alternates if flexible)",
+    "Venue (city, name if booked) and guest count",
+    "Vendor category and a 2-3 sentence style description",
+    "Budget range for this vendor specifically",
+    "Operator's tolerance for non-Saturday or off-season dates (price leverage)",
+    "Operator's preferred communication channel and decision timeline",
+    "Names and contacts to keep private vs share with vendor"
+  ],
+  "contributed_by": "professional-intake agent (v0.9.87 community drop)",
+  "updated_at": "2026-05-20T06:10:08Z"
+}

package/dist/skills/built-in/when-to-stop-being-polite.json

@@ -0,0 +1,161 @@
+{
+  "id": "when-to-stop-being-polite",
+  "name": "When to Stop Being Polite — and What That Actually Looks Like",
+  "version": "1.0.0",
+  "category": "other",
+  "tags": [
+    "meta-skill",
+    "adversarial-robustness",
+    "escalation",
+    "phone-call",
+    "boundary-setting",
+    "critical-reasoning"
+  ],
+  "description": "99% of calls succeed with patience, warmth, and curiosity. A small minority require a hard pivot: firm refusal, named consequences, regulatory escalation language, or immediate disengagement. This skill defines the narrow triggers for that pivot, and what 'no longer polite' looks like in practice — which is NOT rude, hostile, or threatening, but is deliberately formal, citing-rights, and unambiguous about non-cooperation.",
+  "disclaimer": null,
+  "context": {
+    "when_to_use": "ONLY when a clearly bright-line condition is met (see triggers). Default posture remains warm and collaborative — this skill is the exception, not the rule.",
+    "preconditions": [
+      "Agent has confirmed at least one trigger condition with a specific recent example, not a vague sense.",
+      "Agent has authority from the user to formally escalate, lodge complaints, or disengage.",
+      "Agent has the user's relevant rights / protections clear (jurisdiction, regulator, statute if known)."
+    ],
+    "estimated_call_duration_minutes": 5
+  },
+  "principles": [
+    "Politeness is leverage. You spend politeness when you've truly run out of other options — not when you're frustrated.",
+    "'Stopping being polite' does not mean becoming rude. It means becoming FORMAL — citing rights, naming consequences, declining to play within the framing the rep is using.",
+    "Hostility is never useful. Anger is never useful. Naming a specific regulator, requesting a specific form, or invoking a specific right IS useful.",
+    "Triggers must be SPECIFIC: a concrete observable behaviour, not a feeling. 'They were rude' is not a trigger; 'They lied about a written policy I have in hand' is.",
+    "Once you escalate formally, you cannot un-escalate cheaply. Make sure you mean it.",
+    "Even in the formal mode, leave the rep an off-ramp. People who feel cornered escalate; people who see a graceful exit comply."
+  ],
+  "phrases": {
+    "name_the_trigger": "I want to flag something. You just said [X], and the written [bill/contract/email] in front of me says [Y]. That gap is significant.",
+    "request_formal_record": "I'd like this conversation noted formally in the account record. Could you confirm a note has been added with [specific summary]?",
+    "decline_to_proceed": "Given that, I don't want to continue on this call. I'd like a supervisor, or I'll end the call and take this through [written / regulatory] channels.",
+    "regulatory_invocation": "If we can't resolve this here, my next step is to file a complaint with [CFPB / state insurance commissioner / FCC / state AG / FTC]. I'd rather not — could we try one more path first?",
+    "rights_invocation_billing": "Under [FCBA / FCRA / state statute], I'm formally disputing this charge. Please log the dispute, hold collection activity, and send confirmation in writing.",
+    "rights_invocation_debt": "If this is a debt-collection call, I'm asking under the FDCPA that you cease contacting me by phone and communicate only in writing.",
+    "hard_disengage": "I'm going to end this call now. Thank you."
+  },
+  "tactics": [
+    {
+      "name": "Confirm a hard trigger, not a soft frustration",
+      "when": "Before pivoting out of the warm mode.",
+      "script": "Triggers: (a) caught lie about a written fact you have in hand; (b) rep refusing identity verification on inbound call that's asking for sensitive info; (c) threats from the rep ('we'll send to collections today unless...'); (d) refusal to escalate AND refusal to provide refusal-source; (e) extracting personal data not relevant to the stated purpose; (f) repeated refusal across two calls + one supervisor on a clearly bright-line right. Anything else: stay warm.",
+      "priority": 1
+    },
+    {
+      "name": "Shift to formal register without becoming hostile",
+      "when": "Trigger confirmed.",
+      "script": "Slow down. Speak more precisely. Use full sentences. Name the specific behaviour. Stop using filler words like 'sorry' and 'just'. Tone is still calm — the change is in the formality, not the volume.",
+      "priority": 2
+    },
+    {
+      "name": "Name the gap on the record",
+      "when": "After trigger confirmation.",
+      "script": "Use `name_the_trigger`. The point is to put the rep on notice that the conversation is now being treated formally, while still giving them a chance to correct.",
+      "priority": 3
+    },
+    {
+      "name": "Invoke the specific right or regulator",
+      "when": "Trigger involves a regulated industry.",
+      "script": "Use `rights_invocation_billing` / `rights_invocation_debt` / `regulatory_invocation`. Cite the SPECIFIC statute or agency that applies. Generic threats ('I'll report you') carry less weight than 'I will file an FCC complaint reference Title 47, Section X'.",
+      "priority": 4
+    },
+    {
+      "name": "Demand a formal account note",
+      "when": "Before disengaging or escalating.",
+      "script": "Use `request_formal_record`. Make sure the company's own record reflects the dispute. This is critical for any later legal or regulatory action."
+    },
+    {
+      "name": "Leave an off-ramp",
+      "when": "Even in the formal mode.",
+      "script": "Offer ONE more path: a supervisor, a written summary, a 24-hour pause. Reps who see a graceful resolution take it. Reps who are cornered double down."
+    },
+    {
+      "name": "Hard disengage if needed",
+      "when": "Rep escalates abuse, persists in clear violation, or you are no longer being heard.",
+      "script": "Use `hard_disengage`. Do not slam. Do not insult. End. Document. Take it to writing or regulator."
+    }
+  ],
+  "alternative_interpretations": [
+    {
+      "observation": "Rep is curt / unfriendly / having a bad day.",
+      "consider": [
+        "Bad day, no policy issue — stay polite, do not escalate. This is NOT a trigger.",
+        "Hostile but providing correct service — stay polite.",
+        "Hostile AND withholding service the user is entitled to — combination triggers, but the hostility is not the reason; the withholding is.",
+        "Mirror-induced — you are being curt and they are matching you."
+      ],
+      "next_action": "Reset your own warmth first. Most 'rude reps' soften when met with consistent calm."
+    },
+    {
+      "observation": "Rep states something you can verify in writing is false.",
+      "consider": [
+        "Rep is mistaken, not malicious — usually true. Surface gently first per `detect-lies-and-contradictions`.",
+        "Rep is improvising under pressure — same.",
+        "Rep is following a script known to misrepresent — material; escalate formally if it costs the user money.",
+        "Rep is deliberately deceiving — rare; treat as material if pattern is clear."
+      ],
+      "next_action": "Try `detect-lies-and-contradictions` first. Only formally escalate if (a) the misstatement is material AND (b) the rep refuses to correct after one clean opportunity."
+    },
+    {
+      "observation": "Rep threatens consequences ('we'll send this to collections', 'we'll terminate your service today').",
+      "consider": [
+        "Standard, lawful collections language — not a trigger by itself.",
+        "Premature threat — would violate billing dispute rules if a dispute is on file.",
+        "False urgency — see `resist-urgency-manipulation`.",
+        "Genuine final notice — verify against any written notices the user has.",
+        "Designed to extract immediate payment to circumvent normal dispute process."
+      ],
+      "next_action": "Calmly ask: 'When was the written notice sent and what does it say?' If under active billing dispute, invoke `rights_invocation_billing`."
+    },
+    {
+      "observation": "Your own emotional temperature is rising.",
+      "consider": [
+        "Trigger is real and your reaction is calibrated — proceed but keep volume down.",
+        "Trigger is real and your reaction is overcalibrated — pause; cool down before escalating.",
+        "Trigger is not real and you're frustrated — DO NOT escalate; you'll regret it.",
+        "Manipulation working in reverse — rep deliberately provoking you so they can label you 'difficult'."
+      ],
+      "next_action": "Take a 10-second silent beat. Confirm the trigger is observable, specific, and recent. If yes, proceed formally. If no, stay polite or end the call cleanly."
+    }
+  ],
+  "boundaries": [
+    "NEVER raise your voice, threaten the rep personally, or use profanity. Formality has more force than anger.",
+    "NEVER threaten to 'report' someone vaguely. Either cite a specific regulator or don't invoke escalation.",
+    "NEVER invoke statute language you don't understand — get it right or don't say it.",
+    "DO disengage rather than fight, when the call is no longer recoverable.",
+    "DO loop the user in immediately if the formal mode is entered — they should know their call has crossed a threshold."
+  ],
+  "success_signals": [
+    "Rep self-corrects after the gap is named.",
+    "Supervisor takes over and recovers the situation.",
+    "Formal note is added to the account.",
+    "Rep agrees to send a written summary acknowledging the dispute.",
+    "Threatened action (collections, termination) is paused while dispute is open."
+  ],
+  "failure_signals": [
+    "Rep doubles down on the contested behaviour.",
+    "Supervisor confirms the rep's position without acknowledging the cited right.",
+    "Rep refuses to add a formal note.",
+    "Call ends with no record of the dispute."
+  ],
+  "exit_strategy": {
+    "on_success": "Capture the corrected outcome in writing. Confirm the formal note. Step back to a polite register if the rest of the call continues — formality is a tool, not a default.",
+    "on_failure": "End the call cleanly. Move to written channels: certified letter, regulatory complaint, executive customer service. Provide the user with a clear summary including (a) what was alleged, (b) what was said by the rep, (c) what right or rule applies, (d) recommended next channel.",
+    "follow_ups": [
+      "If regulator was invoked, follow through — empty threats train future reps to ignore the invocation.",
+      "Pull all evidence collected per `mid-call-evidence-collection` for any complaint filing."
+    ]
+  },
+  "required_user_info": [
+    "Jurisdiction and relevant regulators / statutes the user is willing to invoke.",
+    "Explicit authority to escalate formally on the user's behalf.",
+    "Any prior dispute filings, written notices, or contractual provisions that bear on the trigger."
+  ],
+  "contributed_by": "critical-reasoning agent (v0.9.87 community drop)",
+  "updated_at": "2026-05-20T06:10:17Z"
+}

package/dist/skills/built-in/wire-funds-safely.json

@@ -0,0 +1,129 @@
+{
+  "id": "wire-funds-safely",
+  "name": "Initiate a Wire Transfer Safely",
+  "version": "1.0.0",
+  "category": "finance-admin",
+  "tags": [
+    "wire-transfer",
+    "wire-fraud",
+    "verification",
+    "real-estate",
+    "business-email-compromise",
+    "phone-call",
+    "banking-finance"
+  ],
+  "description": "Call a bank to initiate (or authorize) a domestic or international wire transfer with rigorous recipient verification — wires are irrevocable once sent, and impersonation / BEC fraud accounts for the largest dollar losses in retail banking.",
+  "disclaimer": "Not financial or tax advice. Agent must NEVER share SSN unprompted, NEVER initiate wires above the operator's stated cap, NEVER agree to a hardship plan / settlement that affects credit without explicit ask_operator approval.",
+  "context": {
+    "when_to_use": "User needs to send funds via wire — real-estate closing, large vendor payment, family transfer abroad, business B2B, etc. Critical context: wires settle in minutes and are practically irrevocable once sent. Fraud rings impersonate title companies, lawyers, executives, family members in distress. This skill exists to add friction in the right places, not to slow legitimate payments.",
+    "preconditions": [
+      "Explicit operator approval for the wire amount, recipient, and reason — recorded.",
+      "Recipient banking details verified through a SECOND channel (phone call to a known-good number, NOT a number from the email that requested the wire).",
+      "User has authentication factors ready: account, PIN/passcode, possibly callback-verification setup.",
+      "User has the bank's wire cutoff time (typically 3-5pm local) and knows weekend / holiday delays.",
+      "For real-estate / closings: title company contact verified at the brokerage's main line, NOT a number from a 'wire instructions' email."
+    ],
+    "estimated_call_duration_minutes": 25
+  },
+  "principles": [
+    "Wires are IRREVOCABLE. Treat every detail like a one-way door — verify before, not after.",
+    "The number-one fraud pattern is a SPOOFED EMAIL with last-minute changed wire instructions. Always verify wire instructions on a fresh outbound call to a known-good number BEFORE the wire call.",
+    "Match the wire amount to the operator's pre-approved cap. Anything above triggers an `ask_operator` halt, full stop. No clever interpretations.",
+    "Read recipient details back digit-by-digit to the rep. ABA/routing, account number, SWIFT/IBAN for international, beneficiary name exactly as on the receiving account.",
+    "Use the bank's callback-verification or out-of-band approval feature if available — it's there because wire fraud is the bank's largest loss category.",
+    "Be skeptical of urgency. 'Send it now or we lose the deal' is the single most common fraud pressure tactic — legitimate counterparties tolerate a 30-minute verification delay."
+  ],
+  "phrases": {
+    "opener": "Hi, I'd like to initiate a wire transfer. Before we start: I'd like to verify recipient details carefully, confirm any applicable cutoff times, and use any callback-verification process the bank offers.",
+    "state_the_wire": "The wire is for $[amount] to [recipient name] at [bank], routing [###], account [###]. The purpose is [closing / vendor / family transfer / etc.].",
+    "verify_callback": "Does the bank offer a callback-verification step where you call me back on the phone number on file before releasing the wire? I'd like to use that.",
+    "ask_cutoff_times": "What is today's cutoff time for [domestic / international] wires, and when will the funds settle at the receiving bank?",
+    "international_extras": "For the international wire — please confirm the SWIFT/BIC, IBAN if applicable, intermediary bank details, and the currency. Also, what FX rate are you applying and what are the total fees?",
+    "ask_for_purpose_field": "What goes in the purpose / memo field? Please use exactly: [text].",
+    "stop_on_red_flag": "I'd like to pause and re-verify the recipient details. Please hold the wire — I'll call back after I confirm the instructions via my second channel.",
+    "graceful_close": "Can you confirm the wire is queued, read back the amount, recipient name, account number, routing/SWIFT, expected settlement time, total fees, and give me the reference / Federal Reference (IMAD/OMAD) number?"
+  },
+  "tactics": [
+    {
+      "name": "Re-verify recipient on a fresh outbound call FIRST",
+      "when": "Before even dialing the bank.",
+      "script": "Call the recipient (title company, vendor, family member) on a number you ALREADY know — not one from any email. Read back the routing + account they expect. If they don't match the emailed instructions, STOP — the email was spoofed.",
+      "priority": 1
+    },
+    {
+      "name": "Check operator-approved cap",
+      "when": "Before authorizing any dollar amount on the call.",
+      "script": "If the wire is at or below the operator's pre-approved cap and to the pre-approved recipient — proceed. If either differs — halt and `ask_operator`. No exceptions.",
+      "priority": 2
+    },
+    {
+      "name": "Open with verification request",
+      "when": "First substantive turn with the bank.",
+      "script": "Use `opener` + `verify_callback`. Banks have these features because wire fraud is rampant; using them is normal and signals you're cautious.",
+      "priority": 3
+    },
+    {
+      "name": "Read details back digit-by-digit",
+      "when": "Stating the wire.",
+      "script": "Use `state_the_wire`, then have the REP read back routing/account/SWIFT. Catch transpositions live — once sent, a mis-keyed digit can land funds at a random account and recovery is not guaranteed.",
+      "priority": 4
+    },
+    {
+      "name": "International extras",
+      "when": "Wire is cross-border.",
+      "script": "Use `international_extras`. Compare the FX rate to mid-market (e.g., Google's rate) so the spread is known. Confirm intermediary-bank fees that can shave 20-40 USD off the received amount."
+    },
+    {
+      "name": "Pause on red flags",
+      "when": "Anything feels off — pressure to hurry, last-minute detail changes, rep waiving the callback step, mismatched recipient names.",
+      "script": "Use `stop_on_red_flag`. Hang up if needed. Re-verify, then restart. A 30-minute delay is cheap; an irrecoverable $50k wire is not."
+    },
+    {
+      "name": "Capture the audit trail",
+      "when": "Wire is queued or sent.",
+      "script": "Use `graceful_close`. Get IMAD (incoming) / OMAD (outgoing) Federal Reference numbers — these are the unique identifiers used to trace the wire if a recall is later needed."
+    }
+  ],
+  "boundaries": [
+    "Do NOT initiate a wire above the operator's stated cap under any pretext — halt and `ask_operator`.",
+    "Do NOT use wire instructions from an email without out-of-band verification — assume the email is spoofed until proven otherwise.",
+    "Do NOT proceed if anyone is pressuring urgency (rep, recipient, third party). Urgency is the universal fraud tell.",
+    "Do NOT initiate a wire to crypto exchanges, gift-card processors, or 'IRS payment' addresses — these are the canonical scam destinations.",
+    "Do NOT skip the callback-verification step even if the rep offers to.",
+    "Do NOT share full SSN unless it's bank policy for the wire desk and operator has approved disclosure.",
+    "Do NOT close the call without IMAD/OMAD or equivalent reference number."
+  ],
+  "success_signals": [
+    "Recipient details verified out-of-band match the bank-call details exactly.",
+    "Bank callback-verification step completed.",
+    "Rep reads back details accurately, no transpositions.",
+    "Wire queued with reference number; cutoff time confirmed.",
+    "Fees and (if FX) rate disclosed and within expectations."
+  ],
+  "failure_signals": [
+    "Recipient details don't match between channels — suspected BEC, halt.",
+    "Rep waives or skips the bank's standard callback step.",
+    "Urgency pressure ('send now or it's gone').",
+    "Recipient name on the receiving account doesn't match what the user expects.",
+    "Wire destination is a personal account at an obscure overseas bank when the deal context says corporate domestic."
+  ],
+  "exit_strategy": {
+    "on_success": "Confirm IMAD/OMAD reference, settlement time, fees, FX (if applicable). Notify the operator immediately with the reference. Notify the recipient on a known-good channel so they can confirm receipt.",
+    "on_failure": "If the wire was sent in error or to a fraudster, call the bank IMMEDIATELY — within minutes — and request a wire RECALL via the Federal Reserve's recall process. File a complaint at IC3.gov and a report with local law enforcement. Inform the operator.",
+    "follow_ups": [
+      "Day +1: confirm receipt with recipient via known-good channel.",
+      "If international: confirm intermediary fees were as quoted.",
+      "If anything off: file IC3.gov report within 24 hours — recall windows are short."
+    ]
+  },
+  "required_user_info": [
+    "Wire amount, currency, purpose",
+    "Recipient legal name (exact match to receiving account)",
+    "Routing / ABA (domestic), SWIFT/BIC + IBAN (international), beneficiary account",
+    "Out-of-band-verified phone number for the recipient",
+    "Operator-approved cap and explicit approval for THIS wire",
+    "Source account from which to debit"
+  ],
+  "contributed_by": "banking-finance agent (v0.9.87 community drop)",
+  "updated_at": "2026-05-20T06:09:47Z"
+}

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@agenticmail/core",
-  "version": "0.9.31",
+  "version": "0.9.33",
   "description": "Core SDK for AgenticMail — email, SMS, and phone call-control for AI agents",
   "type": "module",
   "main": "dist/index.js",