@agenticmail/core 0.9.31 → 0.9.33

package/dist/skills/built-in/childcare-provider-intake.json

@@ -0,0 +1,157 @@
+{
+  "id": "childcare-provider-intake",
+  "name": "Childcare Provider Intake: License, References, Schedule",
+  "version": "1.0.1",
+  "category": "other",
+  "tags": [
+    "childcare",
+    "daycare",
+    "preschool",
+    "nanny",
+    "babysitter",
+    "license",
+    "background-check",
+    "references",
+    "intake",
+    "phone-call",
+    "professional-services"
+  ],
+  "description": "Place an intake / vetting call with a childcare provider — licensed centre, in-home daycare, nanny agency, or independent nanny — to verify license / background checks, surface schedule and ratios, and request references BEFORE the operator tours or signs an enrolment / employment agreement.",
+  "disclaimer": "Childcare regulation varies by jurisdiction and is the single highest-stakes vetting category in this library. This skill does not replace a thorough in-person tour, criminal-background verification, or independent reference checks by the operator. Do not commit on this call.",
+  "context": {
+    "when_to_use": "Operator is choosing childcare for an infant, toddler, or preschool-aged child. Use BEFORE the first tour for a centre / home daycare, or BEFORE the first in-person interview for a nanny / agency placement. Pair with `childcare-tour-checklist` and `nanny-employment-agreement-review` (separate skills).",
+    "preconditions": [
+      "Operator has the provider's full legal business name, license number (for licensed providers), and state.",
+      "Operator has the child's age, schedule needs, and any specific needs (allergies, medical, developmental).",
+      "Operator has surfaced budget range and start-date window.",
+      "Operator has decided centre vs in-home daycare vs nanny vs agency — different vetting paths."
+    ],
+    "estimated_call_duration_minutes": 25
+  },
+  "principles": [
+    "License and inspection records are public in most states. Look them up BEFORE calling — the state child-care licensing department posts violations, citations, and renewal status.",
+    "Ratios drive safety and attention. State minimums (e.g. 1:4 for infants, 1:6 for toddlers) are floors, not goals. Lower is better; ask the actual current ratio, not the maximum.",
+    "Background checks vary widely. State centres require fingerprint + criminal + child-abuse-registry checks for all staff; nanny agencies vary; independent nannies require operator-funded checks. Pin down what's been done and what's on file.",
+    "References are non-negotiable. Two CURRENT or recent families (within 12 months) — and the operator calls them, not the agent.",
+    "Schedule flexibility, sick-day policies, and closure calendars determine real-world fit. Many centres close 3+ weeks per year; many nannies require guaranteed hours regardless of family illness.",
+    "Mandatory reporter status is a feature, not a bug. Every reputable provider should know they're a mandated reporter and how their child-protection protocols work."
+  ],
+  "phrases": {
+    "opener": "Hi — I'm calling for a family looking at [centre / in-home daycare / nanny] care for a [age] child, starting [date], [days/hours]. Before we set up a tour, can I ask a few quick questions about licensing, ratios, and availability?",
+    "license_probe": "Could you confirm your state license number, classification, and whether your last inspection was clean — or, if there were citations, what they were and how they were resolved?",
+    "ratios_probe": "What's your current ratio in the [infant / toddler / preschool] room, what's the maximum your license allows, and who's the lead teacher in that room — name, credentials, and tenure?",
+    "background_check_probe": "Walk me through the background-check protocol for every adult who interacts with children: fingerprint, state criminal, federal criminal, child-abuse registry, sex-offender registry, and how often these are re-run.",
+    "ratios_probe_home": "For in-home daycare: how many children total are on-site at any time, what ages, and who's the second adult if you step away or are ill?",
+    "nanny_specific_probe": "For a nanny: are you a W-2 employee or 1099? Are you authorised to work in the US, do you have CPR / pediatric-first-aid certification, when do they expire, and do you carry your own liability or driving insurance?",
+    "agency_probe": "For an agency: what's your placement-fee structure, what's the trial / replacement guarantee period, and what's been verified on every nanny BEFORE you place them?",
+    "schedule_probe": "What's the current opening — start date, days/hours, and is there a waitlist? What's your annual closure calendar (holidays, training days, summer)? What's the sick-day policy on both sides?",
+    "illness_probe": "What's the sick-child exclusion policy — fever threshold, vomiting / diarrhoea, contagious illnesses — and how do you communicate exposure?",
+    "developmental_probe": "What's the daily structure for a [age], curriculum or approach (play-based, Reggio, Montessori, Waldorf, ABA-influenced), and how do you communicate with parents daily?",
+    "special_needs_probe": "The child has [allergy / condition / IEP / sensory need]. How do you accommodate, who's trained, and what's the medication protocol?",
+    "references_probe": "Could you share two CURRENT or recent (within 12 months) family references, ideally with a child of similar age, who the operator can call directly?",
+    "trial_probe": "Is there a trial day / week / probationary period, and what's the early-termination protocol from either side?",
+    "stall_to_check": "Let me run the schedule, fees, and policies past the parents before we set a tour or sign anything — big decision, deserves a calm review.",
+    "graceful_close": "Thanks — could you email the enrolment / employment packet, the inspection record (or link), the closure calendar, sick policy, and the references over? The family will follow up within [timeframe]."
+  },
+  "tactics": [
+    {
+      "name": "Licence and inspection record first",
+      "when": "Opening minute.",
+      "script": "Use `license_probe`. If the provider can't or won't share the license number on the call, end politely. Anyone licensed knows their number and is happy to share it.",
+      "priority": 1
+    },
+    {
+      "name": "Ratios with actuals, not maximums",
+      "when": "After license.",
+      "script": "Use `ratios_probe` (centre) or `ratios_probe_home` (in-home). The actual current ratio in the room the child would join is the real signal. Lead-teacher tenure is a quality proxy.",
+      "priority": 2
+    },
+    {
+      "name": "Background-check chain of custody",
+      "when": "After ratios.",
+      "script": "Use `background_check_probe`. This applies to every adult — teachers, owner, family-member-cohabitants for in-home, substitute teachers. Anyone unscreened is a no.",
+      "priority": 3
+    },
+    {
+      "name": "Provider-type-specific vetting",
+      "when": "Once basics are clear.",
+      "script": "Use `nanny_specific_probe` for nannies, `agency_probe` for agencies. Different categories, different risks: W-2 / 1099 classification, work authorisation, CPR currency, agency replacement guarantee.",
+      "priority": 4
+    },
+    {
+      "name": "Schedule + closures + sick policy",
+      "when": "Mid-call.",
+      "script": "Use `schedule_probe` and `illness_probe`. The annual closure calendar surprises many parents. Sick-child exclusion thresholds affect work-life logistics.",
+      "priority": 5
+    },
+    {
+      "name": "Curriculum / daily structure",
+      "when": "After logistics.",
+      "script": "Use `developmental_probe`. Even at infant ages, the daily rhythm matters. Parent-communication cadence (daily app, paper logs, weekly summary) is a fit signal."
+    },
+    {
+      "name": "Special needs explicitly",
+      "when": "If the child has any.",
+      "script": "Use `special_needs_probe`. The right answer involves a written care plan, named staff trained, and clear medication protocol. Vague answers are disqualifying."
+    },
+    {
+      "name": "References operator can actually call",
+      "when": "Near end.",
+      "script": "Use `references_probe`. Two CURRENT families. Operator calls — agent does not screen on the operator's behalf."
+    },
+    {
+      "name": "Defer any commitment",
+      "when": "Coordinator pushes to lock the spot.",
+      "script": "Use `stall_to_check`. Childcare commitments are too consequential for a phone call. Tour, references, contract review — then decide."
+    }
+  ],
+  "boundaries": [
+    "Do NOT sign an enrolment contract or employment agreement mid-call. Use ask_operator.",
+    "Do NOT pay an enrolment deposit, holding fee, or agency placement fee on this call. Funds flow only after operator-reviewed written agreement.",
+    "Do NOT share the child's full name, date of birth, or social security number on this call. First name and age category are enough for screening.",
+    "Do NOT share the home address with an independent nanny prospect before background-check completion.",
+    "Do NOT bypass background-check verification because the provider 'feels right' or comes 'highly recommended'. Verification is non-negotiable.",
+    "Do NOT accept a provider with unresolved citations, lapsed license, or refusal to share inspection records.",
+    "Do NOT agree to off-the-books cash pay arrangements for nannies — they expose the operator to tax, insurance, and workers' comp liability."
+  ],
+  "success_signals": [
+    "Licence number, classification, and inspection record shared transparently.",
+    "Actual current ratios cited, with lead-teacher name and tenure.",
+    "Background-check protocol covers every adult and is re-run on a clear cadence.",
+    "Annual closure calendar and sick policy provided in writing.",
+    "Curriculum / daily structure described with specifics, not slogans.",
+    "Two current-family references offered without hesitation.",
+    "Trial period / probationary structure exists and is documented."
+  ],
+  "failure_signals": [
+    "Refusal to share licence number, inspection record, or background-check details.",
+    "Maximum-ratio quoted as though it were the actual ratio.",
+    "Unscreened adults in the home or facility (cohabitants, drop-in family).",
+    "Pressure for an enrolment deposit on the call.",
+    "Refusal to provide current-family references.",
+    "Cash-only / off-the-books employment pitch for nannies.",
+    "Citations on the public record that the provider downplays or doesn't acknowledge.",
+    "Vague answers on medication, allergy, or special-needs protocol."
+  ],
+  "exit_strategy": {
+    "on_success": "Confirm provider will email: enrolment / employment packet, license and inspection record link, annual closure calendar, sick policy, daily-schedule overview, background-check summary, and references. Operator schedules an in-person tour and reference calls before any commitment.",
+    "on_failure": "Politely close. Note the specific reason for the operator's records (licensing concern, ratio mismatch, reference unwillingness, fee structure). If the gap was schedule-only, ask about waitlist options.",
+    "follow_ups": [
+      "Email the operator: provider name, type, license status (with state-board verification status), ratios, background-check summary, schedule fit, references with phone, red/green flags, recommended next step.",
+      "Operator independently verifies license and inspection record via state child-care licensing department.",
+      "Operator independently calls references — agent does not screen references on the operator's behalf.",
+      "Schedule in-person tour AFTER reference checks pass; reserve commitment for after the tour and contract review."
+    ]
+  },
+  "required_user_info": [
+    "Provider type (licensed centre / in-home daycare / nanny / agency) and provider's legal business name + license number",
+    "Child's age and schedule need (days, hours, start date)",
+    "Any special needs (allergies, medical conditions, IEP, developmental concerns) — disclose at the level needed for fit",
+    "Budget range and willingness to pay over for lower ratios / higher quality",
+    "Operator's state (and county if relevant) for licensing-board lookup",
+    "Existing care arrangement and reason for change (informs reference questions)",
+    "Operator's preferred communication channel and decision timeline"
+  ],
+  "contributed_by": "professional-intake agent (v0.9.87 community drop)",
+  "updated_at": "2026-05-20T06:11:50Z"
+}

package/dist/skills/built-in/close-account-no-residual-fees.json

@@ -0,0 +1,127 @@
+{
+  "id": "close-account-no-residual-fees",
+  "name": "Close a Bank or Credit-Card Account Without Residual Fees",
+  "version": "1.0.1",
+  "category": "finance-admin",
+  "tags": [
+    "account-closure",
+    "zombie-fees",
+    "credit-utilization",
+    "retention",
+    "phone-call",
+    "banking-finance"
+  ],
+  "description": "Call the bank to formally close a checking, savings, or credit-card account in a way that prevents zombie fees, residual interest, unintentional credit-score damage, and accidental reopening.",
+  "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 wants an account permanently closed. Common reasons: switching banks, consolidating cards, dodging an annual fee, paying off + closing a card no longer needed. Different mechanics apply for deposit accounts vs credit accounts — credit closure can hit credit utilization and average-age-of-accounts. ALWAYS surface this trade-off before closing a credit card.",
+    "preconditions": [
+      "Operator has confirmed the closure decision. For credit cards: operator understands the potential credit-score impact (utilization spike + AAoA reduction).",
+      "All pending transactions have cleared (or user knows their status). Account balance is zero or paid in full.",
+      "Recurring ACH / autopay / direct deposit on this account has been re-routed elsewhere (or user has a plan).",
+      "User has the account number, last 4, and balance.",
+      "For credit cards: rewards balance redeemed (closing forfeits most rewards) and pending statements known."
+    ],
+    "estimated_call_duration_minutes": 20
+  },
+  "principles": [
+    "For credit cards: closing CAN drop the credit score via two channels — (1) higher overall utilization (less total credit available) and (2) lower average age of accounts when the closed card eventually falls off the report (10 years later for closed in good standing). If the user has multiple cards and/or a long history, impact is small. If this is one of two cards, impact can be significant.",
+    "Closure isn't always best. Consider a 'product change' or 'downgrade' (e.g., AmEx Gold → Green, Chase Sapphire Preferred → Freedom Flex) to dodge the annual fee while keeping the credit line and account age. ASK about this before closing.",
+    "Zombie fees are the #1 closure failure: a residual interest charge or maintenance fee posts AFTER closure, the account silently re-opens or goes to collections. Prevent by (a) confirming balance is exactly zero, (b) asking 'what's the final-statement protocol?', and (c) calling back 60 days later.",
+    "Get closure in writing. A phone closure without confirmation gets disputed later when the bank's system shows the account 'open'.",
+    "If the bank pivots to retention with offers, the user must have decided in advance whether ANY offer would change their mind. If not — politely decline and proceed.",
+    "Stop direct deposits / autopay BEFORE closing the source account, not after. Closed-account ACH attempts trigger NSF, returned-item fees, and merchant-side late fees."
+  ],
+  "phrases": {
+    "opener": "Hi, I'd like to close my [checking / savings / credit card] account ending in [last 4]. Before we close it, can you confirm any pending charges, residual interest, fees, or balance — and walk me through the protocol to ensure no residual posts after closure?",
+    "downgrade_alternative": "Before closing — is there a product change or downgrade available on this card that would let me keep the credit line and account age while dropping the annual fee?",
+    "credit_impact_question": "For my awareness — when this card closes, will it (a) close immediately on my credit report or remain visible for 10 years, (b) how is utilization recalculated, and (c) is there anything I should know about the impact on my score?",
+    "zero_balance_check": "Can you confirm the current balance is exactly $0.00 — no pending interest, no pending fees, no pending transactions — before we proceed with closure?",
+    "redirect_rewards": "I have [points / cash back / miles] balance. What's the policy on closure — do I lose them, can I redeem now, can they be transferred to another account?",
+    "decline_retention": "Thanks, but I've already decided — not changing course today. Can you go ahead and close it?",
+    "ach_handoff": "I want to confirm: any incoming ACH or direct deposit that lands AFTER closure — does the bank return it, hold it, or forward it? I want zero surprise reversals on my employer / payer side.",
+    "graceful_close": "Thanks. Can you confirm: account is closed effective today, balance is $0, no further charges or interest will post, the closure is reported correctly to credit bureaus (closed by consumer / in good standing), and I'll receive a written confirmation. Please give me a reference number and your name."
+  },
+  "tactics": [
+    {
+      "name": "Ask about product change before closing",
+      "when": "Credit-card closure, especially for premium / annual-fee cards.",
+      "script": "Use `downgrade_alternative`. Downgrading to a no-annual-fee version of the same card line preserves account age and credit line — best of both worlds.",
+      "priority": 1
+    },
+    {
+      "name": "Confirm zero balance",
+      "when": "Before authorizing closure.",
+      "script": "Use `zero_balance_check`. If a residual interest charge would post, ASK to pay it now and re-confirm $0. Zombie fees almost always start as 'I thought it was zero.'",
+      "priority": 2
+    },
+    {
+      "name": "Cash in rewards",
+      "when": "Credit-card closure.",
+      "script": "Use `redirect_rewards`. Closure typically forfeits cash-back and miles, unless they're already redeemed or transferred. Pause closure if a redemption is needed.",
+      "priority": 3
+    },
+    {
+      "name": "Decline retention crisply",
+      "when": "Rep pivots to retention offers.",
+      "script": "Use `decline_retention`. ONE polite decline is enough. Repeated decline turns becomes a long call without unlocking new offers if the user has truly decided."
+    },
+    {
+      "name": "Surface credit-bureau reporting",
+      "when": "Account is being closed.",
+      "script": "Use `credit_impact_question`. Confirm it'll be reported 'closed by consumer / in good standing' (or 'paid in full' for credit cards), not 'closed by issuer.'"
+    },
+    {
+      "name": "Handle ACH gracefully",
+      "when": "Deposit-account closure.",
+      "script": "Use `ach_handoff`. Set the expectation that any incoming ACH will be returned, then trigger employer/payer to switch BEFORE you close."
+    },
+    {
+      "name": "Confirmation writeback",
+      "when": "Closure agreed.",
+      "script": "Use `graceful_close`. Written confirmation via secure message, plus a reference number, is the user's defense against zombie fees and 'still open' errors."
+    }
+  ],
+  "boundaries": [
+    "Do NOT close a credit account with a non-zero balance without confirming the residual will be billed and paid promptly — open-account closures with balances roll over and accrue interest.",
+    "Do NOT close a deposit account without first redirecting payroll / autopay — closed-account ACH triggers a cascade of fees on the user's bills.",
+    "Do NOT cancel rewards-rich cards without redeeming the balance — most cash-back and miles forfeit at closure.",
+    "Do NOT accept retention offers without operator approval — keeping a card the user already decided to close is a new commitment.",
+    "Do NOT close the only credit card a user with thin credit history has — that can drop the score significantly.",
+    "Do NOT close without written confirmation."
+  ],
+  "success_signals": [
+    "Zero balance verified.",
+    "Product-change alternative considered (and chosen or declined intentionally).",
+    "Rewards redeemed or transferred.",
+    "Closure confirmed effective today.",
+    "Written confirmation promised via secure message.",
+    "Reference number issued."
+  ],
+  "failure_signals": [
+    "Residual interest / fees expected to post after closure — fix before closing.",
+    "Rep insists on a 30-day cooling period — that's a retention tactic; politely insist on immediate closure.",
+    "Account flagged with pending dispute, hold, or investigation — closure may be delayed; surface to operator.",
+    "Rep cannot guarantee correct credit-bureau reporting code."
+  ],
+  "exit_strategy": {
+    "on_success": "Confirm reference number, written-confirmation timing, expected credit-bureau reporting code. Calendar a 60-day check-back to verify no zombie fee posted.",
+    "on_failure": "If a residual is expected, pay it via the bank's online system, wait one cycle, re-call to close. If retention won't stop pitching, ask to escalate to account-services supervisor and politely insist.",
+    "follow_ups": [
+      "Day +7: confirm written confirmation arrived.",
+      "Day +30 and Day +60: verify account shows closed in online banking AND no new charges have posted.",
+      "Day +60: pull credit report to confirm 'closed by consumer / in good standing' is reflected.",
+      "For credit cards: keep the written confirmation for at least 2 years."
+    ]
+  },
+  "required_user_info": [
+    "Account or card last 4",
+    "Confirmed current balance and any pending items",
+    "ACH / autopay / direct-deposit list to reroute (for deposit accounts)",
+    "Rewards balance and redemption plan (for credit cards)",
+    "Operator pre-decision on retention offers (Yes accept / No decline)",
+    "Operator awareness of credit-score impact (for credit-card closures)"
+  ],
+  "contributed_by": "banking-finance agent (v0.9.87 community drop)",
+  "updated_at": "2026-05-20T06:09:47Z"
+}

package/dist/skills/built-in/close-on-concrete-next-step.json

@@ -0,0 +1,116 @@
+{
+  "id": "close-on-concrete-next-step",
+  "name": "Close Every Call on a Concrete Next Step",
+  "version": "1.0.0",
+  "category": "other",
+  "tags": [
+    "closing",
+    "next-step",
+    "phone-call",
+    "discipline",
+    "pipeline-hygiene",
+    "outreach-sales"
+  ],
+  "description": "Before ending any outbound call, secure exactly one specific, calendared, mutually-agreed next step — OR a clean disqualification. 'I'll follow up next week' is not a next step; it's a ghosting waiting to happen.",
+  "disclaimer": "Skills assume the call is solicited by the operator. NEVER use these to power a mass-cold-call campaign without the operator's explicit per-prospect authorisation.",
+  "context": {
+    "when_to_use": "Last 2-3 minutes of any outbound call where substantive conversation occurred. Applies to discovery calls, follow-ups, referred intros, and re-engagements alike.",
+    "preconditions": [
+      "Agent has confirmed enough about the prospect's situation to know what a real next step would be.",
+      "Operator has authorised the menu of possible next steps the agent can offer.",
+      "Agent has real calendar availability — not vague openness — to propose.",
+      "Agent is willing to disqualify on the call instead of forcing a fake next step."
+    ],
+    "estimated_call_duration_minutes": 3
+  },
+  "principles": [
+    "A call without a concrete next step is a leak in the pipeline. 'I'll follow up' has a measurable conversion rate near zero.",
+    "The next step must be small enough to feel easy and specific enough to be calendared.",
+    "If you genuinely can't find a real next step, the answer is disqualification — not a stalling next step.",
+    "Mutual agreement matters: 'I'll send you a proposal' is not a next step; 'I'll send you a proposal by Thursday and we'll talk Friday at 2' is.",
+    "Confirm in writing within 60 minutes. The verbal next step is half the commitment; the calendar invite is the other half."
+  ],
+  "phrases": {
+    "ask_for_next_step": "Before we hang up — what feels like the right next thing? I'd like to leave with something specific on the calendar so neither of us has to chase the other.",
+    "propose_specific": "How about [specific deliverable] from me by [day], and then we hop on for [duration] on [day/time] to walk through it together?",
+    "compress_to_smallest_step": "Want to start smaller — a 15-minute call next week to see if it even makes sense to go further?",
+    "disqualify_cleanly": "Honestly, hearing all of that, I'm not sure we're the right next step for you right now. Want me to close this out cleanly, and if [trigger condition] changes, you'll know where to find me?",
+    "lock_it_down": "Great — let me read it back: I'll send [thing] by [day], you'll review by [day], we're talking [day/time]. Right? Calendar invite landing within the hour."
+  },
+  "tactics": [
+    {
+      "name": "Earn the close — don't ambush it",
+      "when": "After substantive conversation has happened.",
+      "script": "Use `ask_for_next_step`. Framing it as 'I want to leave with something specific' is mutual; jumping to 'so when can we meet?' is asymmetric.",
+      "priority": 1
+    },
+    {
+      "name": "Offer the next step rather than asking what they want",
+      "when": "Prospect engaged but didn't volunteer a next step first.",
+      "script": "Use `propose_specific`. Prospects who 'want to think about it' often need a structured option to react to. Propose, then let them shape it.",
+      "priority": 2
+    },
+    {
+      "name": "Shrink the step if there's hesitation",
+      "when": "Prospect hedges on the proposed next step.",
+      "script": "Use `compress_to_smallest_step`. A 15-minute call beats a 30-minute one when they're hesitant. Movement matters more than meeting length.",
+      "priority": 3
+    },
+    {
+      "name": "Disqualify out loud rather than fake a next step",
+      "when": "There's no honest next step available.",
+      "script": "Use `disqualify_cleanly`. A real disqualification is a stronger close than a fictional 'I'll follow up in a month' — both for the operator's pipeline hygiene AND the prospect's trust.",
+      "priority": 4
+    },
+    {
+      "name": "Read it back verbatim",
+      "when": "After agreement.",
+      "script": "Use `lock_it_down`. Prospects who hear the commitment read back are 2-3× more likely to honour it.",
+      "priority": 5
+    },
+    {
+      "name": "Send the calendar invite within 60 minutes",
+      "when": "Immediately after the call.",
+      "script": "Use the agent's calendar tool to send a real invite with a one-line agenda. Same-day confirmation is what converts a verbal yes into a held meeting."
+    }
+  ],
+  "boundaries": [
+    "Do NOT propose a time the operator does not actually have on the calendar.",
+    "Do NOT escalate the size of the next step ('let's meet for 90 minutes with our CEO') beyond what the conversation warrants.",
+    "Do NOT accept 'I'll get back to you' as a next step. Press once for specificity; if it doesn't land, disqualify cleanly.",
+    "Do NOT promise deliverables the operator hasn't approved (custom proposals, free pilots, exclusive demos).",
+    "Do NOT count an unconfirmed verbal next step as a closed step in the CRM — it's only real once the invite is accepted."
+  ],
+  "success_signals": [
+    "Prospect accepts the proposed time on the call.",
+    "Prospect counters with their own specific time.",
+    "Prospect names a colleague to include in the next step.",
+    "Calendar invite is accepted within the same business day.",
+    "Prospect responds to the recap email with confirmation."
+  ],
+  "failure_signals": [
+    "Prospect says 'let me get back to you on timing'.",
+    "Prospect agrees to a step but won't pick a specific day.",
+    "Calendar invite remains in 'tentative' or 'no response' state for 48+ hours.",
+    "Recap email goes unanswered for 5+ business days."
+  ],
+  "exit_strategy": {
+    "on_success": "Send the calendar invite within 60 minutes. Send a written recap with the prospect's own words quoted, the deliverable list, and the agreed time. Reconfirm 24 hours before the next step.",
+    "on_failure": "If a concrete next step couldn't be agreed AND there's a real underlying interest, send a written follow-up with two specific time options for a smaller step. If still no movement, follow the ghosted-lead re-engagement protocol — do not keep proposing next steps blind.",
+    "follow_ups": [
+      "Calendar invite + recap email within 60 minutes.",
+      "Reminder ping 24 hours before the next step (one line, not a re-pitch).",
+      "CRM update with verbatim agreement and the named next step.",
+      "If the next step is missed, ONE rescheduling attempt — beyond that, treat as ghosting."
+    ]
+  },
+  "required_user_info": [
+    "Operator's authorised menu of next-step options",
+    "Operator's real calendar windows for the next 2 weeks",
+    "Operator's standing policy on disqualifying vs. nurturing weak fits",
+    "What deliverables the agent may promise (and by when)",
+    "Whether the operator wants to review recap emails before they go out, or trusts the agent to send directly"
+  ],
+  "contributed_by": "sales-outbound agent (v0.9.87 community drop)",
+  "updated_at": "2026-05-20T06:09:47Z"
+}

package/dist/skills/built-in/confirm-agreement-readback.json

@@ -0,0 +1,134 @@
+{
+  "id": "confirm-agreement-readback",
+  "name": "Read Back the Agreement in Your Own Words",
+  "version": "1.0.1",
+  "category": "other",
+  "tags": [
+    "closing",
+    "readback",
+    "verification",
+    "drift",
+    "phone-call",
+    "closing-commitment"
+  ],
+  "description": "Before saying goodbye, restate the entire agreement back to the rep in YOUR own words and have them confirm — yes or no — each numbered item. This catches the drift that creeps in over a 30-minute call where 'first three months' quietly became 'first month' and a credit somehow became a 'pending review'.",
+  "disclaimer": null,
+  "context": {
+    "when_to_use": "End of any call where commitments, dollar amounts, dates, or conditions were discussed. ALWAYS run this before exit_strategy.on_success — never skip it because the rep sounds friendly. Friendly + drift is the most common loss pattern.",
+    "preconditions": [
+      "An agreement of some kind has been verbally reached, OR the rep has stated what they're 'about to do'.",
+      "You have notes (in memory or on screen) of each numeric / dated / conditional item discussed during the call.",
+      "Call recording is in progress — readback is most valuable as a recorded artifact."
+    ],
+    "estimated_call_duration_minutes": 4
+  },
+  "principles": [
+    "Restate in YOUR words, not theirs. Parroting their phrasing preserves the same ambiguity you're trying to expose.",
+    "Number the items out loud. 'One: …. Two: …. Three: ….' forces a discrete yes/no on each rather than a global 'yeah sounds right'.",
+    "Pause AFTER each item for explicit confirmation. A continuous monologue lets the rep nod along and miss the one item that's wrong.",
+    "Listen for 'well, technically…' and 'sort of' — these are the leaks. Stop and pin them down before continuing.",
+    "If the rep corrects you, RE-READ the corrected version back. Do not assume the correction landed verbatim — corrections also drift.",
+    "Silence is NOT consent. If the rep stops responding while you read back an item — restate it and demand a verbal yes. A nod the recording can't hear is not an agreement.",
+    "An unnamed third party did not approve anything. 'My supervisor said it's fine' / 'I just got chat approval' is unverified until you have the supervisor's name + ID + the channel that approval came through, OR the change is reflected on the line by the original rep with a specific reference number."
+  ],
+  "phrases": {
+    "opener": "Before we wrap up, I want to read back what I've understood so we're aligned. I'll go item by item — please correct me on anything that's off, even small wording.",
+    "item_template": "Item [N]: [your restatement]. Is that correct?",
+    "drift_catch": "I think I heard something slightly different earlier — can we pin that down? Is it [version A] or [version B]?",
+    "soft_correction_probe": "When you say 'usually' / 'normally' / 'should' — is that a guarantee for my case specifically, or a general policy that might not apply?",
+    "post_correction_reread": "Okay, with that correction, let me re-read just that item: [restatement]. Confirmed?",
+    "final_lock": "Great. So to summarise everything: [one-sentence rollup]. We're aligned on all of that, yes?",
+    "verify_phantom_approval": "You mentioned a supervisor approved that — could I get the supervisor's name and ID, and confirm that approval is keyed into the system with a reference number? I want to be sure I can quote the right person if the next bill doesn't match.",
+    "resist_rush": "I hear you're short on time — but I'd rather we finish the readback than have to call back next week. Two more minutes. Item [N] was…",
+    "graceful_close_success": "Perfect, thank you for being patient with the readback. I find it saves us both a follow-up call later.",
+    "graceful_close_failure": "I'm hearing some uncertainty on items [X, Y]. Can we pause here and get a supervisor or escalation contact who can confirm in writing? I don't want to hang up on something fuzzy."
+  },
+  "tactics": [
+    {
+      "name": "Announce the readback before doing it",
+      "when": "Immediately after the rep's last commitment, before any goodbye signals.",
+      "script": "Use the `opener` phrase. Telegraphing the readback gets the rep into a confirming mindset — and signals (politely) that you're treating this as a binding moment.",
+      "priority": 1
+    },
+    {
+      "name": "Number each item and force a discrete yes/no",
+      "when": "Working through the agreement.",
+      "script": "Use the `item_template` phrase for each commitment. Wait for a 'yes' or 'correct' before moving on. Treat a hum or 'mhm' as ambiguous — ask again: 'Sorry, just want a clear yes on that one.'",
+      "priority": 2
+    },
+    {
+      "name": "Surface drift with the soft_correction_probe",
+      "when": "The rep uses hedging words: 'usually', 'normally', 'should', 'in most cases'.",
+      "script": "Use the `soft_correction_probe` phrase. Hedging is where post-call denials live. Pin the rep to a specific commitment for THIS account.",
+      "priority": 3
+    },
+    {
+      "name": "Re-read after every correction",
+      "when": "The rep corrects an item mid-readback.",
+      "script": "Use the `post_correction_reread` phrase. Never assume a corrected item is now correct — re-state it and re-confirm. Two-pass corrections catch second-order drift.",
+      "priority": 4
+    },
+    {
+      "name": "Final one-sentence rollup",
+      "when": "All items confirmed individually.",
+      "script": "Use the `final_lock` phrase. This creates one cleanly-recorded summary statement that a future agent or human can replay if the company disputes the agreement.",
+      "priority": 5
+    },
+    {
+      "name": "Escalate on lingering uncertainty",
+      "when": "Two or more items remain fuzzy after the readback round.",
+      "script": "Use `graceful_close_failure`. Do NOT close the call on an unresolved item — schedule a supervisor or written follow-up instead. Closing fuzzy is functionally identical to no agreement at all.",
+      "priority": 6
+    },
+    {
+      "name": "STOP and re-evaluate on manufactured urgency",
+      "when": "Rep injects time pressure mid-readback — 'I have to go in 30 seconds', 'the system will time out', 'my next call is starting', 'this offer expires when we hang up'.",
+      "script": "Use `resist_rush`. Manufactured urgency is the #1 weapon against a readback. The right response is to slow down, not speed up. If the rep insists they must end the call NOW, treat the agreement as UNCONFIRMED — log every item as 'pending readback' and refuse to act on it until a callback or written confirmation completes the verification. Do NOT accept a deal you were not allowed to verify.",
+      "priority": 7,
+      "decision_point": "If the rep ends the call mid-readback citing urgency — assume that was the point. The unverified portion is null. Recover via `request-written-confirmation` AND a callback with `capture-rep-identity` referencing the failed readback timestamp."
+    },
+    {
+      "name": "Verify any 'supervisor approved' claim",
+      "when": "Rep mentions, during or after the readback, that an off-line manager / supervisor / floor lead / system override / one-time exception was granted — but that person was not on the call.",
+      "script": "Use `verify_phantom_approval`. Phantom approvals are how 'we agreed to a $200 credit' becomes 'I don't see any approval in the system' two weeks later. Require: (a) the approver's name AND ID, (b) the timestamp the approval was keyed in, (c) a reference number specific to the approval, AND (d) confirmation that the approval is visible in the account note the rep is reading from — not 'I'll add it after we hang up'. If any of the four is missing, treat the item as UNCONFIRMED.",
+      "priority": 8
+    }
+  ],
+  "boundaries": [
+    "Do NOT skip the readback because the call is running long or the rep sounds impatient. The readback IS the deliverable.",
+    "Do NOT accept 'yeah, all that' as confirmation of a multi-item readback. Discrete yes per item.",
+    "Do NOT treat silence after an item as a yes — restate and force a verbal confirmation.",
+    "Do NOT rephrase the rep's correction into your own words on the second pass — quote them this time so the recording shows the rep's exact wording.",
+    "Do NOT add new asks during the readback. Readback is verification only — new asks belong before this step or on a separate call.",
+    "Do NOT let a rep collapse the readback by claiming an offer 'expires' the moment you hang up — real, durable concessions outlast the call. Anything that genuinely evaporates the second you stop talking was bait."
+  ],
+  "success_signals": [
+    "Rep confirms each numbered item with a clear 'yes' or 'correct'.",
+    "Rep volunteers a correction you'd missed — proves the readback is working as intended.",
+    "Rep offers to send a written summary unprompted.",
+    "Rep references your readback by item number ('on your item three…')."
+  ],
+  "failure_signals": [
+    "Rep rushes ('yes yes yes, that's all fine') without engaging with individual items.",
+    "Rep refuses to confirm specific items, only general 'we'll process this'.",
+    "Rep changes terms on the readback that were different earlier — and resists writing the new version down.",
+    "Audio quality drops or the rep claims they have to go — common stall to dodge being on record.",
+    "Rep cites manufactured urgency to cut the readback short ('offer expires when we hang up', 'system about to lock', 'next caller waiting').",
+    "Rep references an off-line approver ('my supervisor said it's fine') but cannot produce that approver's name, ID, or a reference number tied to the approval."
+  ],
+  "exit_strategy": {
+    "on_success": "Pair this skill's output with `capture-rep-identity` and `request-written-confirmation` — readback alone is necessary but not sufficient. Log the confirmed rollup verbatim in the call notes.",
+    "on_failure": "Do not say goodbye on unresolved items. Escalate to supervisor, request a written summary before hanging up, or schedule a callback with a ticket number you control.",
+    "follow_ups": [
+      "Save the recorded readback timestamp in case of a dispute.",
+      "Cross-check the written confirmation (when it arrives) against the readback transcript word-by-word."
+    ]
+  },
+  "required_user_info": [
+    "Running notes of each commitment made during the call (amounts, dates, conditions)",
+    "Confirmation that the call is being recorded on your side OR theirs",
+    "Authority from the user to keep the rep on the line for an extra 3-5 minutes for verification"
+  ],
+  "contributed_by": "closing-commitment agent (v0.9.87 community drop)",
+  "updated_at": "2026-05-20T06:09:47Z"
+}