@agenticmail/core 0.9.32 → 0.9.33

package/dist/skills/built-in/late-add-petition.json

@@ -0,0 +1,128 @@
+{
+  "id": "late-add-petition",
+  "name": "Petition to Late-Add or Late-Drop a Course",
+  "version": "1.0.1",
+  "category": "other",
+  "tags": [
+    "registrar",
+    "petition",
+    "late-add",
+    "late-drop",
+    "advising",
+    "phone-call",
+    "education"
+  ],
+  "description": "Call an academic advisor, dean's office, or registrar to add or drop a course past the published deadline — by petition, instructor consent, or dean's signature.",
+  "disclaimer": "Late-add and late-drop policies vary widely; some schools require an instructor signature only, others require a college-level committee. Financial-aid impact (full-time vs. part-time) and tuition refund schedules are separate from academic petitions — handle both.",
+  "context": {
+    "when_to_use": "The published add/drop deadline has passed and the user needs to (a) add a course they were attending but never officially registered, (b) drop a course that's tanking their GPA before final grades, (c) swap a section due to a schedule conflict that emerged after the deadline, or (d) replace a class that turned out to be misadvised (wrong level, missing prerequisite, taught very differently than catalog).",
+    "preconditions": [
+      "User can articulate WHY the deadline was missed in one sentence (illness, work change, advising error, family emergency, instructor unresponsive).",
+      "User has the course CRN / section number, instructor name, and current grade/standing if available.",
+      "User knows the financial implications: tuition refund window, financial-aid full-time threshold (usually 12 credits undergrad), insurance / housing thresholds.",
+      "User has checked the school's petition form — most late-add/drop petitions require a written petition AND a signature from the instructor, advisor, and sometimes a dean."
+    ],
+    "estimated_call_duration_minutes": 20
+  },
+  "principles": [
+    "Late petitions live on documented circumstances, not on regret. 'I should have dropped earlier' is weak; 'I was hospitalized March 3–8, here's the discharge summary' is strong.",
+    "The earlier you petition past the deadline, the easier the approval. Two weeks late is a paperwork exercise; ten weeks late is a battle.",
+    "Instructor support is the single highest-leverage signature. If the instructor backs the petition, advisors and deans almost always defer.",
+    "There are usually TWO deadlines: add/drop (administrative) and withdraw (a W on the transcript). Past add/drop, the realistic ask is often 'late withdrawal' not 'late drop' — know the difference.",
+    "Financial-aid full-time status is a cliff, not a slope. Dropping from 12 to 9 credits mid-term can trigger Pell/Stafford recalculation. Loop the financial-aid office BEFORE confirming a drop.",
+    "Dean's offices grant exceptions for what registrars can't. If front-line advising says no, the assistant dean for student academic affairs is the real target."
+  ],
+  "phrases": {
+    "opener_late_add": "Hi, I'm in week [N] of [course] but I never officially added it — I thought I was registered. I'd like to start a late-add petition. Can you tell me what your office needs from me, and who has signature authority?",
+    "opener_late_drop": "Hi, I'd like to petition for a late drop / late withdrawal from [course]. The standard deadline was [date]. The reason is [one-line cause]. What's the process and what documentation do you require?",
+    "ask_instructor_first": "Before I file the petition — does it make sense for me to talk to the instructor first to confirm they'll sign? My understanding is that an instructor-supported petition has a better chance.",
+    "ask_about_W": "Past the withdrawal deadline, what are my options? A W on the transcript is fine; an F is the outcome I'm trying to avoid.",
+    "documented_cause": "I have [doctor's note / death certificate / employer letter / police report] for [dates]. Should I submit it with the petition or attach it later?",
+    "ask_aid_impact": "If I drop this course, my credit load goes from [X] to [Y]. Could you check whether that drops me below full-time for financial-aid purposes, and if so, what the recalculation would look like?",
+    "ask_for_dean": "If the registrar's office can't approve this at the front-line level, could the petition be routed to the assistant dean for student affairs / academic standards? I want to make sure it gets a substantive review.",
+    "graceful_close_success": "Thank you. To confirm: I'm submitting [form] with [signatures and documents] by [date]. You'll route it to [committee/dean], and I can expect a decision by [date]. Is there an email I can use to check status?",
+    "graceful_close_failure": "Okay. Could you put in writing what specifically would have made the petition successful, and whether I can re-petition in a future term? And is there a path to grade replacement if I retake the course later?"
+  },
+  "tactics": [
+    {
+      "name": "Lock in instructor support first",
+      "when": "Before any administrative call.",
+      "script": "Use `ask_instructor_first` framing during the call, but the actual ask is to the instructor by email/office hours: 'Will you sign / email support for my late-add or late-drop petition for [reason]?' Get a yes in writing before filing.",
+      "priority": 1
+    },
+    {
+      "name": "Distinguish drop vs. withdrawal",
+      "when": "The user says 'I want to drop it' past the drop deadline.",
+      "script": "Use `ask_about_W`. A 'drop' removes the course from the transcript (and refunds tuition by schedule). A 'withdrawal' leaves a W on the transcript with no GPA impact. Past the drop deadline, the realistic ask is usually W. Make sure the user understands which they're requesting.",
+      "priority": 2
+    },
+    {
+      "name": "Document the cause specifically",
+      "when": "Petition asks 'why now and not by the deadline?'",
+      "script": "Use `documented_cause`. Dates on documents must straddle or precede the deadline you missed. A doctor's note dated AFTER the deadline still works if symptoms began before. Get explicit dates.",
+      "priority": 3
+    },
+    {
+      "name": "Pre-clear financial aid",
+      "when": "Drop would cross a credit-load threshold.",
+      "script": "Use `ask_aid_impact`. Call financial aid SEPARATELY before finalizing the drop — registrar won't model aid impact, and a 'Return to Title IV' calculation after the fact can owe the student thousands.",
+      "priority": 4
+    },
+    {
+      "name": "Escalate to the dean's office",
+      "when": "Registrar or advising says no but the cause is documented and serious.",
+      "script": "Use `ask_for_dean`. Dean-level review is standard for documented medical, mental-health, family-emergency, or advising-error cases. Specifically ask for 'assistant dean for student affairs' or 'academic standards committee' — not just 'the dean'.",
+      "priority": 5
+    },
+    {
+      "name": "Ask about retroactive add/drop windows",
+      "when": "Issue is discovered in a later term.",
+      "script": "Some schools allow retroactive petitions up to one academic year (or longer for medical). Don't assume the door is closed just because the term ended."
+    },
+    {
+      "name": "Ask about grade replacement / repeat policy as a fallback",
+      "when": "Late-drop is denied and the user is heading toward a poor grade.",
+      "script": "Many schools allow a course to be retaken with the new grade replacing or averaging with the old. This is a separate process from late-drop and may be the better path if the petition fails."
+    }
+  ],
+  "boundaries": [
+    "Do NOT submit a late-add petition for a course the user did not actually attend — registrars cross-check attendance and falsifying it is academic dishonesty.",
+    "Do NOT fabricate documentation. Verification calls to doctors / employers happen and the consequences are academic misconduct, not just denial.",
+    "Do NOT drop a course without confirming financial-aid impact in writing.",
+    "Do NOT promise the instructor anything beyond what the operator has authorized (e.g. completing missed work).",
+    "Do NOT skip the petition form. Verbal yeses from a registrar don't post in the system."
+  ],
+  "success_signals": [
+    "Petition number / case number is issued.",
+    "Instructor agrees to sign or send a supporting email.",
+    "Advisor confirms the petition will route to dean / committee, not be denied at front desk.",
+    "Financial-aid impact is modeled and is acceptable (or zero).",
+    "Decision turnaround is named (commonly 5–10 business days)."
+  ],
+  "failure_signals": [
+    "Instructor refuses to sign for a late-add.",
+    "Petition is past the school's outer deadline (commonly 1 year retroactive).",
+    "Drop would drop user below half-time, triggering immediate loan repayment.",
+    "Multiple prior petitions on file — schools tighten on repeat askers.",
+    "Course is required for an upcoming deadline (graduation, prerequisite for next term) and dropping creates a worse problem."
+  ],
+  "exit_strategy": {
+    "on_success": "Confirm: form submitted, signatures collected, decision date, who signs final, financial-aid status confirmed. Get the petition reference number.",
+    "on_failure": "Get the denial in writing with specific reasoning. Pivot to: incomplete grade (talk to instructor), grade replacement next term, medical withdrawal (different process), or appeal to dean if not yet tried.",
+    "follow_ups": [
+      "Email the operator the petition number, decision date, and financial-aid impact memo.",
+      "If approved: verify the course status changes in the student-information system and on the transcript.",
+      "If denied: research grade-replacement / repeat policy and incomplete-grade option as next steps."
+    ]
+  },
+  "required_user_info": [
+    "Course CRN, section, instructor name",
+    "Reason for missing the deadline (one sentence)",
+    "Documentation available (with dates)",
+    "Current credit load and whether drop crosses a threshold",
+    "Whether instructor has been contacted and their stance",
+    "Petition form (school's specific name) and any prior submissions"
+  ],
+  "contributed_by": "education-admin agent (v0.9.87 community drop)",
+  "updated_at": "2026-05-20T06:09:47Z"
+}

package/dist/skills/built-in/leave-of-absence-deferral.json

@@ -0,0 +1,130 @@
+{
+  "id": "leave-of-absence-deferral",
+  "name": "Request a Deferral or Leave of Absence",
+  "version": "1.0.0",
+  "category": "other",
+  "tags": [
+    "deferral",
+    "leave-of-absence",
+    "gap-year",
+    "dean",
+    "phone-call",
+    "education"
+  ],
+  "description": "Call admissions (pre-matriculation) or the dean of students / registrar (post-matriculation) to request a deferral or leave of absence — gap year, military, mission, family, financial, mental-health, professional opportunity — and to lock down the re-entry path so the seat / financial aid / scholarships are protected.",
+  "disclaimer": "Deferral (before you've started) and leave of absence (after you've matriculated) are different processes with different decision-makers and consequences. Scholarships, financial aid, and housing are sometimes preserved across leaves and sometimes not — get every promise in writing.",
+  "context": {
+    "when_to_use": "User has either (a) been admitted but wants to defer starting by a semester or a year, or (b) is currently enrolled and wants to step away for one or more terms without withdrawing entirely. Common reasons: gap year, financial, mental-health, family caregiving, internship / job opportunity, military deployment, religious mission, athletic Olympic training.",
+    "preconditions": [
+      "User can articulate the reason and the intended return date.",
+      "User has reviewed the school's deferral / LOA policy (most schools cap deferral at 1–2 years and LOA at 1–4 terms).",
+      "User has a sense of what they'll be doing during the leave — schools are friendlier to structured plans (job, service, treatment) than to undefined time off.",
+      "User has identified anchoring deadlines: deposit deadline, financial-aid renewal, scholarship renewal, housing waitlist, health insurance, immigration status."
+    ],
+    "estimated_call_duration_minutes": 20
+  },
+  "principles": [
+    "Deferral is admissions' decision; LOA is the dean's. Calling the wrong office wastes a day.",
+    "Reasons matter for approval, but documentation matters for protection. Get the leave in writing with explicit return conditions.",
+    "Scholarships and merit aid don't automatically follow you. Ask each award separately whether it survives the leave.",
+    "Re-entry should be a checkbox, not a re-application. Negotiate a return process at the front end: 'I email by [date], you reactivate me.' If it's an interview + committee, that's a red flag for friction at return.",
+    "Federal student loans enter grace-period countdown when the student drops below half-time. A 12-month leave can exhaust the entire grace period before re-entry.",
+    "International students: an LOA usually terminates SEVIS. Plan with the DSO before filing."
+  ],
+  "phrases": {
+    "opener_deferral": "Hi, I've been admitted for [term] and I'd like to request a one-[semester / year] deferral. I'm planning to [activity]. Could you walk me through the process and what happens to my scholarship and aid package?",
+    "opener_loa": "Hi, I'm currently enrolled and I'd like to take a leave of absence starting [term]. My intended return is [term]. Could we walk through the process — the form, the decision-maker, and what happens with aid, housing, and re-entry?",
+    "ask_about_scholarship": "I have a [scholarship name] award. Does it carry over through a deferral / LOA, or do I need to re-apply, or is it forfeited? If carry-over is conditional, what are the conditions?",
+    "ask_about_aid": "How does my financial-aid package handle a leave? Does Pell / institutional grant / loan eligibility reset, freeze, or expire?",
+    "ask_about_housing": "What happens to my housing assignment? Am I in the next year's lottery automatically, or do I lose priority?",
+    "ask_about_re_entry": "What's the re-entry process exactly? Do I email by a date, fill a form, attend an interview, or re-apply? I'd like the simplest possible path documented in writing.",
+    "ask_about_F1": "I'm on F-1 status. How does an LOA affect SEVIS, and has the DSO been brought into this conversation?",
+    "ask_for_dean_of_students": "Could I speak with the dean of students or associate dean? I want to make sure the LOA is set up so re-entry is straightforward.",
+    "graceful_close_success": "Thank you. To confirm in writing: leave effective [date], return [date], scholarship [status], aid [status], housing [status], re-entry process [steps], and the decision letter will come from [office]. Could you email me a confirmation?"
+  },
+  "tactics": [
+    {
+      "name": "Route to the right office on the first call",
+      "when": "Opening.",
+      "script": "If pre-matriculation: admissions. If post-matriculation: dean of students or registrar. If athlete: also compliance. If F-1/J-1: also DSO. Calling the wrong office burns a day and you'll be told to call back, often missing a deadline.",
+      "priority": 1
+    },
+    {
+      "name": "Pin down each financial bucket separately",
+      "when": "Discussing consequences.",
+      "script": "Use `ask_about_scholarship`, `ask_about_aid`, and ask about each merit award by name. Front-line staff often answer 'yes it carries over' generically — but specific scholarships have donor-specific rules. Ask them to verify in the system.",
+      "priority": 2
+    },
+    {
+      "name": "Negotiate a minimal re-entry process",
+      "when": "Discussing return logistics.",
+      "script": "Use `ask_about_re_entry`. The ideal: 'Email by [date], the dean reactivates you, you register for classes.' Less ideal: re-application, committee review, interview. Push for the lighter option and ask for it in writing.",
+      "priority": 3
+    },
+    {
+      "name": "Loop the DSO before filing if F-1 / J-1",
+      "when": "User is an international student.",
+      "script": "Use `ask_about_F1`. A leave can terminate SEVIS within 15 days unless an Authorized Early Withdrawal or Reduced Course Load is in place. The DSO is the only office that can protect status.",
+      "priority": 4
+    },
+    {
+      "name": "Plan a 'structured' leave narrative",
+      "when": "Discussing the reason.",
+      "script": "Schools approve gap years more easily when there's a plan: internship, service, treatment, family caregiving with a defined timeline. 'I want to figure things out' is harder. Frame the time as productive even if it's recovery.",
+      "priority": 5
+    },
+    {
+      "name": "Escalate to the dean of students for non-standard timing",
+      "when": "Mid-term LOA, multi-term LOA, or LOA across a graduation cohort.",
+      "script": "Use `ask_for_dean_of_students`. Standard policies cover standard cases; non-standard cases need dean-level approval. The dean of students has discretion that registrars don't."
+    },
+    {
+      "name": "Ask about insurance + immunization holds",
+      "when": "Re-entry planning.",
+      "script": "Health insurance enrollment, immunization records, and Title IX trainings often expire during a leave and create silent re-entry holds. Surface them at the LOA conversation so they don't ambush the return."
+    }
+  ],
+  "boundaries": [
+    "Do NOT fabricate a reason for leave. If asked, schools may verify employers, programs, or providers.",
+    "Do NOT defer without confirming scholarship carry-over in writing — verbal yeses don't survive staff turnover.",
+    "Do NOT take an LOA without confirming the half-time-status loan implications.",
+    "Do NOT file an LOA on F-1 / J-1 without DSO involvement.",
+    "Do NOT assume housing rolls over — most schools require a new application even after approved LOA."
+  ],
+  "success_signals": [
+    "Form submitted and decision date named.",
+    "Scholarship and aid carry-over confirmed in writing.",
+    "Re-entry process is one or two steps (email + form), not a re-application.",
+    "Housing path is mapped (lottery priority preserved or queue reentry).",
+    "DSO has authorized leave for F-1 students."
+  ],
+  "failure_signals": [
+    "Scholarship is non-deferrable — admit-and-attend or forfeit.",
+    "Re-entry requires re-application + committee review with no protection of admit / aid.",
+    "F-1 SEVIS termination is unavoidable, requiring a new visa for return.",
+    "Mid-term LOA falls outside policy and dean's office won't grant exception.",
+    "Loans enter accelerated grace period and would come due before realistic re-entry."
+  ],
+  "exit_strategy": {
+    "on_success": "Confirm all of: effective date, return date, scholarship, aid, housing, insurance, immunizations, re-entry process, decision-maker office, and DSO status. Get email confirmation before the call ends.",
+    "on_failure": "Identify the blocker. If scholarship: explore donor petition. If F-1: explore Reduced Course Load instead of LOA. If aid grace-period: explore in-school deferment by enrolling at a community college part-time. If timing: petition the dean of students.",
+    "follow_ups": [
+      "Email operator a one-pager with all confirmed dates and protections.",
+      "Calendar return-paperwork deadline minus 14 days.",
+      "Calendar scholarship-renewal date during the leave year.",
+      "30 days before return, confirm health insurance, immunizations, and Title IX trainings are current."
+    ]
+  },
+  "required_user_info": [
+    "Student ID and current / admit term",
+    "Intended leave start + return terms",
+    "Reason and rough plan during the leave",
+    "Scholarship / merit-aid names and donors",
+    "Financial-aid composition + loans",
+    "Housing status",
+    "Immigration status (F-1, J-1, citizen, PR)",
+    "Athletic / military / religious affiliations affecting timing"
+  ],
+  "contributed_by": "education-admin agent (v0.9.87 community drop)",
+  "updated_at": "2026-05-20T06:09:47Z"
+}

package/dist/skills/built-in/lock-in-terms-verbally.json

@@ -0,0 +1,127 @@
+{
+  "id": "lock-in-terms-verbally",
+  "name": "Lock In Dates, Amounts, and Conditions Verbally",
+  "version": "1.0.1",
+  "category": "other",
+  "tags": [
+    "closing",
+    "verbal-commitment",
+    "recording",
+    "specifics",
+    "phone-call",
+    "closing-commitment"
+  ],
+  "description": "Get the rep to say — out loud, on the recorded line — the specific numbers, dates, and conditions of the agreement, in their own voice. The recording itself becomes the artifact. Verbal commitments on a recorded line have substantially more enforceability than a customer's paraphrase of what they think was promised.",
+  "disclaimer": "Call recording is governed by jurisdiction. Confirm recording legality with the user before relying on this skill. In two-party states, ensure the rep was informed the call is recorded — most call centres announce this on their side.",
+  "context": {
+    "when_to_use": "Any commitment with a numeric, dated, or conditional component — billing changes, credits, refunds, service activation, contract terms, promised callbacks. Use AFTER `confirm-agreement-readback` has surfaced the items, but BEFORE `request-written-confirmation`.",
+    "preconditions": [
+      "An agreement has been reached on at least one specific number, date, or condition.",
+      "Call recording is in effect (verified, not assumed).",
+      "You know which side is recording — affects how you reference the recording in the lock-in phrasing."
+    ],
+    "estimated_call_duration_minutes": 3
+  },
+  "principles": [
+    "The customer's voice saying the number is not the artifact. The rep's voice saying the number IS the artifact. Always extract the commitment FROM the rep, not back AT them.",
+    "Specific > general. '$47.32 starting June 1, 2026, for 12 months' is enforceable; 'a lower bill soon' is not.",
+    "Frame the lock-in as 'for the recording' or 'for my notes' — never as 'so I can sue you later'. Same data, vastly different cooperation.",
+    "Date all conditions. 'When you renew' must become 'on or after [explicit date]'. Open-ended conditions are escape hatches.",
+    "If the rep gives a range ('between 30 and 45 days'), pin the upper bound. The longer end is the actual SLA in practice.",
+    "A 'one-time exception' that only exists if you commit NOW, before written confirmation, is bait. Durable concessions survive a 24-hour cool-off. If the rep insists the terms evaporate at hangup, the right move is to walk — not to commit faster.",
+    "Numbers the rep refuses to say OUT LOUD on the recorded line are not commitments. 'You'll see it on the bill' or 'I've keyed it in, you can trust me' are not artifacts. Make them speak the figure or treat it as unconfirmed."
+  ],
+  "phrases": {
+    "amount_lock": "Just so I have it exactly — can you state the new amount and when it takes effect? I want to make sure I write it down word for word.",
+    "date_lock": "And the effective date — is that [specific date], or [some other anchor]? Just want the exact day.",
+    "duration_lock": "How long does that rate / credit / promotion last? Is there an end date or a roll-off month?",
+    "condition_lock": "Are there any conditions attached — autopay, paperless billing, a contract term, a minimum spend? I want to list them out so I don't accidentally trip one.",
+    "rollback_clause": "If something on my side changes — say I switch plans or miss a payment — what happens to this agreement? Does it auto-cancel, prorate, or stay?",
+    "range_pin": "You said 30 to 45 days — if it goes the full 45, when's the latest it should land? I'll set my reminder around that date.",
+    "explicit_recording_reference": "Thanks for being precise on this — it saves both of us follow-up calls when the numbers are stated on the line.",
+    "graceful_close_success": "Got it: [amount] starting [date], lasting [duration], conditions [list], rollback rules [rules]. Thanks for being precise.",
+    "graceful_close_failure": "I'm not getting clean answers on the specifics — can we get a supervisor or a written quote before I close this out? I don't want to walk away on vague numbers."
+  },
+  "tactics": [
+    {
+      "name": "Extract the amount in the rep's voice",
+      "when": "An amount has been agreed to.",
+      "script": "Use the `amount_lock` phrase. Make the rep state the figure. If they say 'I just told you it's 47', respond: 'I want to be sure I caught it right — could you say it once more with the cents?'",
+      "priority": 1
+    },
+    {
+      "name": "Pin every date to a calendar day",
+      "when": "Any date or timeframe has been mentioned.",
+      "script": "Use the `date_lock` phrase. Convert relative phrases ('next billing cycle', 'starting soon') into 'June 1' or 'on or before June 15'. Calendar days are enforceable; relative phrases are not.",
+      "priority": 2
+    },
+    {
+      "name": "Bound the duration explicitly",
+      "when": "A promotional or temporary commitment is in play.",
+      "script": "Use the `duration_lock` phrase. Promotional rates that have no stated end are the #1 source of bill surprise 12 months later — `negotiate-bill-reduction` has the same lesson.",
+      "priority": 3
+    },
+    {
+      "name": "Enumerate conditions",
+      "when": "Any 'as long as you…' or 'provided that…' has been mentioned, even in passing.",
+      "script": "Use the `condition_lock` phrase. Conditions stated quickly mid-call are how companies later claim the agreement was voided. Make the rep list them.",
+      "priority": 4
+    },
+    {
+      "name": "Pre-litigate the rollback rules",
+      "when": "After conditions are listed.",
+      "script": "Use the `rollback_clause` phrase. Find out IN ADVANCE what voids the deal. This is the question reps least expect — and the answer often reveals fine print they would have otherwise glossed.",
+      "priority": 5
+    },
+    {
+      "name": "Pin ranges to their upper bound",
+      "when": "Rep gives a range ('5 to 10 business days', '30-45 days').",
+      "script": "Use the `range_pin` phrase. The agent's reminders/follow-ups should be calibrated to the worst case; ranges are misleading when used as expected values.",
+      "priority": 6
+    },
+    {
+      "name": "STOP and re-evaluate on manufactured urgency",
+      "when": "Rep claims the offer expires 'when we hang up' / 'in five minutes' / 'before midnight' / 'while we're on the line' and pressures the agent to commit before specifics are locked.",
+      "script": "Pause out loud: 'I hear the urgency, but I'm not authorised to commit on terms I haven't verified. If the offer genuinely needs a written quote and a 24-hour review, that's the path — otherwise, the offer wasn't real.' If the rep insists, route to `ask_operator` BEFORE committing — never let the rep's clock override the operator's authority.",
+      "priority": 7,
+      "decision_point": "If the rep refuses to put the same terms in writing for review and insists on a verbal commitment NOW — assume the terms wouldn't survive scrutiny. Decline the verbal commit. The right answer is 'I'll need to call back if those terms are available outside this minute.' True one-time offers are rare; manufactured one-time offers are common."
+    }
+  ],
+  "boundaries": [
+    "Do NOT say 'this call is being recorded' if you cannot verify that's true on your side — false recording claims undermine trust if the rep checks.",
+    "Do NOT badger the rep for specifics they genuinely cannot give (e.g. 'when exactly will the system update?' on a back-office process). Switch to a written commitment instead.",
+    "Do NOT accept vague answers a second time. If the first ask returns 'soon', ask once more; if still vague, escalate.",
+    "Do NOT invent a deadline to pressure the rep ('I need to know by Friday') unless the user actually has one. Manufactured urgency is detectable and counterproductive.",
+    "Do NOT commit to terms the rep won't say on the recorded line. Whispered, off-record, 'between us' figures are non-binding.",
+    "Do NOT accept a 'this offer evaporates at hangup' frame as a reason to skip readback or written confirmation. If it really does evaporate, the bait was the offer — let it go."
+  ],
+  "success_signals": [
+    "Rep states the full amount with cents, the full date, and the duration in one sentence.",
+    "Rep volunteers conditions you hadn't asked about — they're being thorough.",
+    "Rep gives a concrete rollback rule ('if you miss a payment, the promo stops the next cycle').",
+    "Rep references their own system: 'I've keyed it in as $47.32 effective 06/01/2026'."
+  ],
+  "failure_signals": [
+    "Rep keeps redirecting to 'check the next bill' instead of stating the amount.",
+    "Rep refuses to commit to a specific date.",
+    "Rep mentions conditions only when prompted, and the list keeps growing.",
+    "Rep says 'I can't make that promise on the recording'  — major red flag.",
+    "Rep demands a verbal yes NOW citing an offer that 'expires at hangup' — manufactured-urgency tell.",
+    "Rep refuses to put the same terms in a written quote / portal note before committing — durable concessions survive writing; bait does not."
+  ],
+  "exit_strategy": {
+    "on_success": "Log the locked terms verbatim with the call timestamp so the recording can be retrieved if needed. Pass to `request-written-confirmation` to triangulate.",
+    "on_failure": "Do not close. Escalate to a supervisor or request a written quote / email / portal note before ending the call. A call without locked specifics is functionally a call without an agreement.",
+    "follow_ups": [
+      "Calendar a check-in for the rollback / expiry date.",
+      "If the written confirmation contradicts the locked verbal terms, the recording is the authoritative version — reference its timestamp in the dispute."
+    ]
+  },
+  "required_user_info": [
+    "Specific numbers and dates the user expects (so the agent can compare against what the rep states)",
+    "Knowledge of recording status on both sides of the call",
+    "User authorisation for any conditions that may be agreed to (autopay, paperless, term commitments)"
+  ],
+  "contributed_by": "closing-commitment agent (v0.9.87 community drop)",
+  "updated_at": "2026-05-20T06:09:47Z"
+}

package/dist/skills/built-in/match-energy-keep-goal.json

@@ -0,0 +1,120 @@
+{
+  "id": "match-energy-keep-goal",
+  "name": "Match the Rep's Energy Without Losing the Operator's Goal",
+  "version": "1.0.0",
+  "category": "other",
+  "tags": [
+    "mirroring",
+    "tone",
+    "energy",
+    "phone-call",
+    "focus",
+    "discipline",
+    "emotional-intelligence"
+  ],
+  "description": "Mirror the rep's pace, register, and warmth closely enough to be liked, but keep one foot planted on the operator's goal so you don't get talked off it. The risk of energy-matching is drift — this skill is about the discipline that prevents it.",
+  "disclaimer": null,
+  "context": {
+    "when_to_use": "Any call where the rep has a strong, defined energy — chatty, crisp, jokey, dry, dramatic, deeply professional. Especially important when the rep is GOOD at their job and naturally pulls you into their rhythm, because that rhythm may not serve the goal.",
+    "preconditions": [
+      "You know the operator's single most important outcome — not three, the one.",
+      "You can keep a private 'goal anchor' sentence in mind throughout the call.",
+      "You have permission to be a little playful / dry / formal as the call demands."
+    ],
+    "estimated_call_duration_minutes": 12
+  },
+  "principles": [
+    "Mirror tempo first, vocabulary second, jokes last. Tempo is invisible; jokes are visible and risky.",
+    "Match within ~10% of their register — not 100%. Full mimicry is uncanny. Slight echo is rapport.",
+    "Keep one sentence in your head that names the goal. Say it silently before every reply. If your next sentence doesn't move toward it, change the sentence.",
+    "Chatty reps will trade five minutes of small talk for one favour — that can be a good deal. Just decide BEFORE you spend it.",
+    "Crisp reps reward crispness with speed and information density. Don't soften them; meet them.",
+    "Energy-match the rep, goal-anchor the operator. Two channels, same mouth."
+  ],
+  "phrases": {
+    "goal_re_anchor": "Quick check before we go further — main thing I'm trying to land is [goal in one sentence]. Are we on track for that?",
+    "chatty_redirect_warm": "Ha — okay, before I forget what I called about, can we lock in [goal]?",
+    "crisp_acknowledge": "Got it. Next item: [goal in one clause].",
+    "playful_mirror_low_risk": "Fair enough — you've heard that one before, huh?",
+    "formal_mirror": "Understood. May I confirm [goal] before we proceed?",
+    "soft_pause": "Hold on — let me make sure I'm not getting ahead of myself."
+  },
+  "tactics": [
+    {
+      "name": "Diagnose energy in the first 20 seconds",
+      "when": "After the rep's first 2-3 sentences.",
+      "script": "Classify silently: chatty / crisp / dry / formal / dramatic / flat. Choose a tempo and register to land within 10% of theirs. Do not switch register mid-call without reason.",
+      "priority": 1
+    },
+    {
+      "name": "Set a private goal anchor sentence",
+      "when": "Before you speak your first substantive sentence.",
+      "script": "In your head: 'The one thing I need from this call is X.' Recite it before every turn. If you find yourself off-track three turns later, use `goal_re_anchor` to land back on it without breaking the energy.",
+      "priority": 2
+    },
+    {
+      "name": "Mirror tempo only at first",
+      "when": "Turns 1-3.",
+      "script": "Speak at their pace. Pause where they pause. Do NOT try jokes or slang yet — you haven't earned the read. Vocabulary and humour come once tempo locks in.",
+      "priority": 3
+    },
+    {
+      "name": "Tone-shift detector — REP SPEEDS UP",
+      "when": "Rep's sentences shorten, pauses disappear, they want to wrap.",
+      "script": "Speed up with them. Drop adjectives. Get to the goal in the next sentence — they're signalling 'I have a queue.' Hesitation here loses you the call.",
+      "priority": 4
+    },
+    {
+      "name": "Tone-shift detector — REP SLOWS DOWN",
+      "when": "Rep starts telling a story, shares an opinion, or volunteers context.",
+      "script": "Slow down with them. Give them the floor for 20-30 seconds. They're investing in the relationship — under-investing back is rude and loses leverage. THEN gently re-anchor.",
+      "priority": 5
+    },
+    {
+      "name": "Tone-shift detector — REP GETS PLAYFUL",
+      "when": "Rep cracks a joke or uses warm slang.",
+      "script": "Mirror with a LOW-RISK callback (`playful_mirror_low_risk`). Do not escalate the humour. You're acknowledging the invitation, not auditioning.",
+      "priority": 6
+    },
+    {
+      "name": "Re-anchor when you've drifted",
+      "when": "Three turns of chat with no goal progress.",
+      "script": "Use `chatty_redirect_warm` for warm reps, `goal_re_anchor` for crisp reps. The redirect should match the current energy, not interrupt it.",
+      "priority": 7
+    }
+  ],
+  "boundaries": [
+    "Do NOT adopt accents, regional slang, or in-group vocabulary you don't own. Mocking-by-accident is a call-killer.",
+    "Do NOT mirror profanity unless the operator has cleared it AND the context warrants it — usually it doesn't.",
+    "Do NOT match flirtation. Friendly is the ceiling.",
+    "Do NOT match a downward emotional spiral (rep getting more cynical, more defeated). Hold one level above to keep the call workable.",
+    "Do NOT keep matching energy if you've lost the goal — the goal beats the rapport."
+  ],
+  "success_signals": [
+    "Rep says 'okay we get along' or 'you're easy to deal with.'",
+    "Goal lands within the expected call duration even though the call FELT longer.",
+    "Rep volunteers extras (faster shipping, a credit, a notation) — they had to like you for that.",
+    "You finish the call and can still articulate the goal you came in with."
+  ],
+  "failure_signals": [
+    "You realise mid-call you no longer remember the goal sentence.",
+    "Rep is delighted with you but you've gotten nothing actionable.",
+    "You overshot on jokes and the rep pulled back to script voice.",
+    "You under-matched and the rep treats you as an interchangeable caller."
+  ],
+  "exit_strategy": {
+    "on_success": "Close in the rep's register — warm goodbye for warm reps, crisp 'thanks, have a good one' for crisp reps. Confirm goal outcome explicitly.",
+    "on_failure": "If you drifted, name it cleanly at the end ('I went down a rabbit hole — can you confirm [goal] before we go?'). Better an awkward 10 seconds than missing the goal.",
+    "follow_ups": [
+      "Self-debrief: which 10% mirror moves worked, which felt forced?",
+      "Note the rep's energy type for future calls to the same line — it's often consistent across calls."
+    ]
+  },
+  "required_user_info": [
+    "The ONE outcome that defines success — written out, one sentence.",
+    "Any topics that are NOT okay to mirror into (politics, religion, etc.).",
+    "Operator's tolerance for chit-chat — some want speed, some want relationships built."
+  ],
+  "contributed_by": "emotional-intel agent (v0.9.87 community drop)",
+  "updated_at": "2026-05-20T06:09:47Z"
+}