@velinussage/locus-agent-skill 0.1.35 → 0.1.41

package/skill/locus-aging-owner/SKILL.md

@@ -0,0 +1,108 @@
+---
+name: locus-aging-owner
+preamble-tier: 1
+version: 1.0.0
+description: Use when an older US homeowner, or an adult child helping a parent, asks about the costs, programs, fraud watch and hazards of the parent's own home, or about the duties and records of a rental property the older owner manages, from cited Locus records.
+triggers:
+  - helping my elderly parent with their house
+  - my mom is getting older and owns her home
+  - senior property tax exemption
+  - aging in place help
+  - home repair help for seniors
+  - my dad still manages his rental
+  - older landlord rental property duties
+  - elder fraud and my parent's house
+allowed-tools: Bash Read AskUserQuestion
+license: MIT
+---
+# Locus aging-owner workflow
+
+Locus gives dated, cited facts about one home or rental and the public programs around it. The
+owner decides what to do. Always use the owner's own address and the owner's own records.
+
+**Never:** say the owner can or cannot manage on their own; give legal, tax, investment, medical
+or care advice; say anyone qualifies for a program; give eviction instructions; use eviction or
+court records about tenants as people. Locus does not produce those statements and neither may
+you on Locus's behalf.
+
+**How to speak:** follow "How to speak with owners, sellers and buyers" in the `locus-agent-tools`
+skill (https://api.locus.report/.well-known/skill.md), including its 988 crisis guard.
+
+## 0. Ask two questions first
+
+Use AskUserQuestion:
+1. **Who is asking?** The older owner, or someone helping them (for example an adult child).
+2. **Which property?** The owner's own home, or a rental property the owner manages. If both, do
+   the home first.
+
+**When the user is helping:** say once, plainly, that acting for another adult on legal or money
+matters needs legal authority, such as a power of attorney, and that Locus never assumes that
+authority. Records lookups are public; signing, filing or applying for the owner is not. Offer
+`locus_estate_property_pointers` with `{ state }` for the state's Uniform Power of Attorney Act
+status and the court self-help page. Do not ask for the parent's name, health, finances or
+account details. You need only the property address.
+
+## Path A. The owner's own home (free)
+
+1. **Tax relief and dates.** `locus_owner_programs` with
+   `{ address, classes: ["exemption_relief", "tax_relief_local", "assessment_deferral", "installment_plan"] }`
+   for senior, disability and veteran exemptions, freezes and deferrals, then `locus_tax_calendar`
+   for the application and payment dates. Quote each row's fact and source. The assessor decides
+   who qualifies.
+2. **Help to stay in the home.** `locus_owner_programs` with `{ address, classes: ["aging_in_place", "home_repair"] }`:
+   - the Eldercare Locator, which leads to the local Area Agency on Aging;
+   - USDA Section 504 home repair loans and grants (rural areas; grants are for owners 62 and over,
+     as the row states);
+   - the DOE Weatherization Assistance Program and LIHEAP (energy bills and weatherization);
+   - the HUD reverse-mortgage (HECM) counseling requirement. Say only what the row says: for a
+     HUD-insured reverse mortgage, the borrower, any non-borrowing spouse and any non-borrowing
+     owner must receive counseling from a HUD-approved HECM counselor. `locus_housing_counselors`
+     lists nearby counseling agencies. Never recommend or discourage a reverse mortgage.
+3. **Utility costs.** `locus_utility_credits` for credits and rebates at the address, and
+   `locus_water_utility_leak_adjustment_rules` for how the water utility handles a leak bill.
+4. **Fraud watch.** People 60 and over bear a large share of reported real-estate fraud losses.
+   - `locus_parcel_transfers` with the address: recent recorded sales near the address, with dates;
+     check the site address before treating a row as the owner's own. For the full title watch,
+     follow section 8 (title watch) of the `locus-home-watch` skill.
+   - `locus_fraud_alert_pointer` for the county recorder's free alert, if offered.
+   - The National Elder Fraud Hotline row from `locus_owner_programs` (class `aging_in_place`):
+     copy its phone number and hours from the row exactly.
+   - Offer a standing watch with the `locus-home-watch` skill on the address.
+   Locus does not verify anyone's identity; send that check to a title company.
+5. **Hazards, each with a step.** `locus_flood_zone` and `locus_wildfire_risk`. For each hazard
+   fact, give one step and a date, for example the flood insurance question before hurricane
+   season, or a mitigation program from `locus_owner_programs` with `{ address, hazard }`.
+6. **Payment trouble.** If the owner is behind on tax, mortgage or utility payments, say payment
+   trouble is common and that HUD-approved housing counselors are free or low-cost. Use
+   `locus_housing_counselors` with the address for nearby counseling agencies (a directory
+   listing is not proof of HUD approval; confirm with HUD), and hand off to the
+   `locus-payment-hardship` skill.
+
+## Path B. The owner's rental property (free)
+
+1. **Landlord duties.** `locus_tenant_statute_pointers` with the rental's place: the state's
+   landlord-tenant statute pointers (deposits, entry notice, repairs, termination). These are
+   pointers to official text only. Never give eviction steps; for a dispute, route to a landlord-
+   tenant attorney or legal aid.
+2. **Registration.** `locus_rental_registration_check` with the address: whether the city runs a
+   rental registry and what its record shows.
+3. **Lead paint.** `locus_parcel_lookup` for the recorded year built. If it is before 1978, list
+   the federal lead-based-paint disclosure pointers from `locus_seller_disclosure_pointers` (they
+   cover leases of pre-1978 housing, subject to their exceptions). A missing year is unknown, not
+   post-1978.
+4. **Condition and compliance.** `locus_parcel_code_cases`, `locus_service_requests` and
+   `locus_permit_rules` for the address: open code cases, nearby service requests and which work
+   needs a permit. Coverage is limited; an empty result is not proof that nothing is open.
+5. **Rent context.** `locus_fair_market_rents` for the area: HUD Fair Market Rents by bedroom
+   count, with the year. Context, not a rent recommendation.
+6. **Records watch.** Offer the `locus-home-watch` skill on the rental address.
+7. **Help.** The Area Agency on Aging (via the Eldercare Locator row) for the owner's own support;
+   a property manager or attorney for leases, notices and disputes.
+
+## Completion
+
+The person has, for the chosen path: the cited rows and dates, one concrete next step per item,
+the fraud or records watch they chose, and the human route (Area Agency on Aging, housing
+counselor, legal aid or attorney). When the user was helping, they were told once that legal
+authority matters and were given the state pointers. Every statement traces to a Locus citation
+or the user's own input.

package/skill/locus-escrow-shock/SKILL.md

@@ -0,0 +1,138 @@
+---
+name: locus-escrow-shock
+preamble-tier: 1
+version: 1.1.0
+description: Use when an owner, or their agent, asks why their mortgage payment or escrow went up and what they can do, and has the servicer's escrow analysis letter. Splits the change into its tax and insurance parts and routes each part to cited Locus records, dated windows and choices.
+triggers:
+  - my mortgage payment went up
+  - escrow went up
+  - escrow shortage
+  - escrow analysis letter
+  - why did my house payment increase
+  - escrow surplus refund
+  - property tax and insurance went up in my payment
+allowed-tools: Bash Read AskUserQuestion
+license: MIT
+---
+# Locus escrow-shock workflow
+
+An escrow increase almost always comes from two parts: property tax and homeowners insurance,
+plus any shortage the servicer is collecting. Locus supplies the cited tax, insurance-cost and
+servicer-rule records for each part. The owner, the servicer, the assessor and the insurance
+agent decide what happens next. Never say "drop your escrow", "your servicer made a mistake",
+"you will win an appeal" or "next year's payment will be X". Locus does not produce those
+statements and neither may you on Locus's behalf.
+
+**How to speak:** follow "How to speak with owners, sellers and buyers" in the `locus-agent-tools`
+skill (https://api.locus.report/.well-known/skill.md), including its 988 crisis guard.
+
+Inputs you need from the owner, all from the servicer's escrow analysis letter: the street
+address; the old and new monthly escrow amounts; the annual tax and insurance amounts the letter
+used, old and new; any shortage or surplus and how the servicer proposes to collect or refund
+it; and the end date of the escrow computation year. **Never guess these numbers.** If the owner
+does not have the letter, ask them to request it from the servicer and stop the arithmetic until
+they do. Do not collect the loan number, account numbers, names or phone numbers.
+
+## 1. Split the change (free)
+
+1. Compute, from the owner's numbers only:
+   - the tax change: new annual tax minus old annual tax;
+   - the insurance change: new annual premium minus old annual premium (add flood or wind
+     premiums as separate lines if the letter lists them);
+   - the shortage part: the shortage amount and the number of months the servicer spreads it
+     over, as the letter states.
+   Show each part's share of the monthly change. If the parts do not add up to the letter's
+   total, say so and name the line that differs; do not fill the gap.
+2. Do the split as plain arithmetic: divide each annual change by 12. Use
+   `locus_property_math_calculator` only when the owner wants a whole monthly-payment worksheet;
+   it takes a tax rate and an annual insurance amount, not the letter's lines. Label every figure
+   as arithmetic over the owner's letter.
+
+## 2. Tax part (free, then the protest skill)
+
+3. `locus_property_tax_context` for the address: the area's median tax bill and effective rate,
+   with vintage. It is area context, not this parcel's bill.
+4. `locus_tax_calendar` for the county: reappraisal cadence, bill dates and due dates, so the
+   owner can see when the next bill, and the next escrow analysis, will reflect any change.
+5. `locus_appeal_window` with `{ address, noticeDate }` when the owner has an assessment notice.
+   Give the computed deadline and its statute. `locus_appeal_filing_guide` gives the forms and
+   filing body. If the owner wants to contest the value, hand off to the
+   `locus-property-tax-protest` skill with the address, the notice date and the deadline.
+6. `locus_owner_programs` with `classes: ["exemption_relief", "tax_relief_local",
+   "assessment_deferral", "installment_plan"]`: homestead, senior, veteran and disability
+   exemptions, deferrals and payment plans the registry cites for the place, each with its filing
+   window. Say whether the owner's bill already shows each one only if the owner tells you; an
+   exemption that is not on the bill is a separate filing with its own deadline.
+
+## 3. Insurance part (free)
+
+7. `locus_homeowners_insurance_context` for the address: the Census survey's median
+   homeowners-insurance cost band for the ZIP, county and state, with vintage. It is an estimate
+   for the area, never a quote and never this policy's price. Use it only to say whether the
+   owner's premium sits inside or outside the area's published band.
+   - `fioZip`: Treasury Federal Insurance Office (FIO) figures for the ZIP, by year, labeled
+     **2018-2022 historical area context**: `premiumsPerPolicyUsd`, `nonrenewalRate`,
+     cancellation rates, `claimFrequency`, `claimSeverityUsd` and `paidLossRatio`. They describe
+     the ZIP's market then, not this policy, today's premium or a forecast. Read `fioZip.status`:
+     `reported` gives the figures; `suppressed` means some cells are blank (null is not zero);
+     `not_in_source` means the ZIP is absent, which may be suppression or a coverage gap;
+     `source_unavailable` means the figures could not be read here (the read failed or the
+     snapshot is not enabled). Report it as a gap, not as zero.
+     Use `premiumsPerPolicyUsd` only to show how the ZIP's average premium moved over those
+     years, never to judge whether this owner's increase is fair.
+8. `locus_flood_premium_context` when the letter lists flood insurance, or the home is in a
+   mapped flood zone: the NFIP policy-cost spread for the ZIP, with policy counts.
+9. `locus_mitigation_incentives` for the address (add `hazard: "wind"`, `"wildfire"` or `"flood"`
+   when it fits): cited insurance-discount rules and mitigation grants, with their windows.
+10. Say plainly that Locus cannot quote, compare or shop insurance policies. The next step for
+    the premium is a coverage review with the owner's insurance agent, with the cited discount
+    rules in hand.
+
+## 4. Servicer side (free)
+
+11. `locus_owner_mortgage_calendar` with `{ "escrowComputationYearEnd": "<date from letter>" }`.
+    Read `computedDates.escrowAnnualStatement` for the date the annual statement is due, and the
+    `statuteFactCards` entry whose `action` is about the annual escrow statement and shortages.
+    Quote that card's `window` text and `source` as written: it states the rules for statement
+    timing, the cushion, spreading a shortage and refunding a surplus. Never add a rule the card
+    does not state, and never apply a rule to this loan as a finding; the servicer's documents
+    control.
+12. If the letter's dates, cushion or shortage spread look different from the card's text, give
+    the owner the question to ask the servicer in writing, with the card's citation. Do not call
+    it an error.
+
+## 5. End with choices and dates
+
+13. Close with the choices that apply, each with its date or window and the tool or office that
+    supports it:
+    - appeal the assessment (deadline from step 5);
+    - apply for an exemption or relief program (windows from step 6);
+    - review coverage and discounts with an insurance agent (step 10, with the renewal month);
+    - ask the servicer how a shortage can be repaid, as a lump sum or spread over months
+      (step 11).
+    Offer choices, never a verdict on which one to take.
+14. If the owner says they cannot make the new payment, hand off to the `locus-payment-hardship`
+    skill without shame: payment trouble is common, and HUD-approved housing counselors give free
+    or low-cost help with servicer conversations. `locus_housing_counselors` lists agencies in
+    HUD's housing counseling directory near the address; confirm the agency's HUD approval, fees
+    and availability with the agency. Do not assess their finances or predict what the servicer
+    will do.
+15. Offer to set up the `locus-home-watch` skill so the next tax bill, appeal window and
+    exemption deadline surface early. Where the events catalog lists it, its section 9
+    `locus.real_estate.escrow_analysis_approaching` reminder (with the month of the servicer's
+    usual analysis) surfaces the next escrow analysis 30 days ahead.
+
+## Never
+
+- Advise keeping, dropping or waiving escrow.
+- Give a lender or servicer verdict ("they overcharged you", "this is illegal").
+- Predict next year's payment, tax bill or premium.
+- Quote, rank or recommend an insurer or policy.
+
+## Completion
+
+The owner has: the change split into tax, insurance and shortage parts from their own letter;
+the cited tax context, appeal deadline and exemption windows; the area insurance cost band and
+cited discount rules; the escrow fact card's text and the statement date; and a short list of
+choices, each with a date and the office to contact. Every number traces to the owner's letter
+or a Locus citation.

package/skill/locus-home-watch/SKILL.md

@@ -0,0 +1,202 @@
+---
+name: locus-home-watch
+preamble-tier: 1
+version: 1.2.1
+description: Use when an owner who is keeping a property, or their agent, wants a standing watch on one address or a saved pool so money deadlines and nearby public-record changes surface on their own, each with a plain next step.
+triggers:
+  - watch my house
+  - keep an eye on my property
+  - remind me of property tax deadlines
+  - tell me when something changes near my home
+  - homestead exemption renewal reminder
+  - set up alerts for my address
+  - monitor my rental properties
+  - standing watch on my home
+allowed-tools: Bash Read AskUserQuestion
+license: MIT
+---
+# Locus home watch workflow
+
+Locus supplies dated deadlines and cited public-record changes for an address. The agent turns
+each event into one plain next step. The owner decides what to act on and what to pay for.
+Never present an event as "you must", "you are at risk", "this lowers your value" or "you
+should appeal". State the fact, its date and its source, then the question the owner can ask
+next.
+
+**How to speak:** follow "How to speak with owners, sellers and buyers" in the `locus-agent-tools`
+skill (https://api.locus.report/.well-known/skill.md), including its 988 crisis guard.
+
+Inputs you need from the owner: the street address (or up to 10 addresses), and whether they want
+you to poll on their behalf or receive signed webhooks. Do not collect account numbers, names,
+phone numbers or email addresses for the watch. Calendar reminders may also take the owner's renewal or escrow-analysis month, as a number from 1 to 12. Do not collect policy or loan numbers.
+
+## 1. Choose the watch target
+
+1. **One to ten addresses, no sign-in.** Inline `addresses` work on
+   `https://mcp.locus.report/mcp` with `events/poll` (or the model tool `poll_events`). This is
+   free and needs no account.
+2. **A saved pool (2 to 25 addresses), signed in.** Connect to
+   `https://mcp.locus.report/muse/mcp` (OAuth, scopes `pools events:subscribe`, or
+   `Authorization: Bearer lmc_...`). Create the pool with `create_pool` and use its `poolId`. Pool
+   events and webhooks need this sign-in; an unsigned call returns an authentication error, not
+   an empty result.
+3. Read the live schema before the first call: `events/list`, the model tool `list_event_types`,
+   or free `locus_mcp_events_catalog` with `{}`. The schema wins over this skill if they differ.
+
+## 2. Set up the two standing events
+
+4. **Money deadlines:** `locus.real_estate.deadline_approaching` with
+   `{ "addresses": [...], "horizonDays": 60 }` (or `{ "poolId": "..." }`). The default lanes are
+   `locus_tax_calendar`, `locus_appeal_window`, `locus_program_windows`, `locus_owner_programs`,
+   `locus_tax_sale_calendar` and `locus_open_disaster_assistance`. Add
+   `"basis": ["as filed", "statutory"]` to drop published-schedule dates if the owner wants fewer
+   alerts.
+5. **Changes around the home:** `locus.real_estate.changes_detected` with
+   `{ "addresses": [...], "lanes": [...], "includeUpcomingDays": 60 }`. Pick up to six free lanes
+   that fit the owner's question, for example `locus_flood_map_change_notices`,
+   `locus_metro_permits`, `locus_development_cases`, `locus_parcel_code_cases` and
+   `locus_boil_water_notices` (state-published boil-water orders for the serving system). A lane outside
+   the address's coverage returns `out_of_coverage` when called directly; check with
+   `locus_lane_availability` first rather than promising coverage.
+6. **Delivery.** Pick one:
+   - **Poll.** Omit `cursor` on the first call. Store the returned `cursor` only after you have
+     processed the response, and pass it on the next poll.
+   - **Signed webhook (signed in only).** `events/subscribe` or `subscribe_event` with a public
+     HTTPS URL and a `whsec_...` secret. Your receiver must answer the verification challenge
+     within 5 seconds. Verify `webhook-signature` and `webhook-timestamp` on every delivery and
+     deduplicate by `eventId`. Deliveries go out when a signed-in session calls `poll_events` with
+     `"deliverWebhooks": true`, so schedule that call at your cadence; a subscription alone does
+     not push. Renew before `refreshBefore`.
+
+## 3. Cadence guide
+
+| Event | Suggested cadence | Why |
+|---|---|---|
+| `deadline_approaching` | Weekly, with `horizonDays` of 30 to 60 | Deadlines move slowly; a wider horizon gives the owner time to gather papers. |
+| `changes_detected` | Daily, and never slower than every 24 hours | A poll cursor expires after 24 hours. A late poll starts a new baseline and reports nothing for the gap. |
+| `changes_detected` with `locus_boil_water_notices` | At least every 12 hours, or `subscribe_event` when signed in | Boil-water notices are time-critical, and the lane lists active orders only: a notice issued during a re-baseline after a late poll joins the baseline silently and never emits. Locus is not an emergency alert; the utility's own alerts come first. |
+| Any event | Not faster than `nextPollMs` (one hour) | Faster polls add load and find nothing new. |
+
+If you poll `deadline_approaching` weekly, omit the old cursor: a fresh poll lists every dated
+event inside the horizon, and you deduplicate by `eventId` yourself. For `changes_detected`, if
+a cursor has expired, tell the owner the watch restarted on that date and that changes before it
+were not compared.
+
+## 4. Read each poll honestly
+
+7. **Empty poll.** It means "nothing new was seen in the lanes checked", not "nothing happened".
+   Say exactly that, and name the lanes.
+8. **`truncated: true`.** The result is incomplete: a lane or address was unavailable, the
+   cursor was stale, or more events are waiting (`hasMore: true`). Poll again with the new cursor
+   for `hasMore`. For an unavailable lane, say which lane could not be read; do not report it as
+   clear.
+9. **`source_unavailable` or `unavailable` on a lane.** That source failed. It is not zero
+   records and not good news. Report it as a gap and check again on the next poll.
+10. **The first poll of `changes_detected`** sets a baseline and normally reports no changes.
+    Say "the watch is set; changes after today will show", not "no changes found".
+
+## 5. Triage each event into one next step
+
+11. **`deadline_approaching`.** Report `event`, `date`, `daysRemaining`, `basis` and the source
+    (`sourceName`, `sourceUrl`, `fetchedAt`). Then:
+    - **Appeal or assessment deadline** (tool `locus_appeal_window`, or a `locus_tax_calendar`
+      event about revaluation, review, protest, listing or equalization): hand off to the
+      `locus-property-tax-protest` skill with the address, the deadline and the notice date if the
+      owner has it. That skill owns the clock, the evidence and the filing.
+    - **Exemption, relief or program window** (`locus_program_windows`, `locus_owner_programs`):
+      call the same free tool for the address and list what the owner must file and by when. If a
+      homestead or relief exemption is not on the owner's bill, say it is a separate filing with
+      its own deadline.
+    - **Tax due or tax-sale date** (`locus_tax_calendar`, `locus_tax_sale_calendar`): report the
+      date and the county's official source. Do not estimate penalties.
+    - **Disaster assistance** (`locus_open_disaster_assistance`): report the program and its
+      closing date from the source.
+    - A `basis` of `"published schedule"` is the authority's own calendar; `"statutory"` is the
+      date the law sets; `"as filed"` comes from a record. Say which one it is.
+12. **`changes_detected`.** Report `summary`, then each item in `newRecords` with its
+    `sourceName`, `sourceUrl` and `fetchedAt`, and each item in `newUpcoming` with its date. Then:
+    - **A flood-map change notice** (`locus_flood_map_change_notices`): say a map revision that
+      names the county is proposed or final, give its comment deadline or effective date from the
+      notice, and say a county notice is not a change to this parcel's zone. Suggest the owner ask
+      their insurer how the revision would apply once it is effective.
+    - **A permit, development case or code case near or at the address**: give the record
+      number, the status and the date, then the next question (for example, "when is the hearing,
+      and how do I comment?"). For a code case at the owner's own address, give the case status
+      and the issuing office; do not interpret it.
+    - **A boil-water notice** (`locus_boil_water_notices`): give the notice status, issue date,
+      affected water system and source URL, and point to the utility's own instructions. Say it
+      is system context, not confirmed impact at this address. Give no health or safety verdict.
+      State-issued boil orders only; a precautionary advisory from the utility may not appear.
+      Check the utility's alerts.
+      A notice that drops off the list was not necessarily lifted; check the utility. If the
+      owner asks what their own service line is made of, call `locus_service_line_material`
+      (California, address level); for a break or leak, hand off to `locus-water-incident`.
+    - **New dated events** in `newUpcoming` are handled as in step 11.
+
+## 6. Paid next steps: offer, never auto-pay
+
+13. Deadline and change events carry `nextActions`: a pre-filled paid call with `tool`, `priceUsdc`, `adds`
+    and `charge: "charge_free_unless_substantive"`. Typical tools are `locus-assessment-position`,
+    `locus-owner-action-brief`, `locus-property-tax`, `locus-permit-closeout-check` and
+    `locus-property-update`.
+14. Offer it in one line: what it adds (quote `adds`) and its price (quote `priceUsdc`). Ask the
+    owner. Only after a clear yes, call it through `locus_execute` with the x402 payment in
+    `_meta["x402/payment"]`, or the REST path in `call.rest`. Never pay because an event arrived,
+    and never pay twice for the same `eventId`.
+15. `charged: false` in the paid result means the data was too thin to charge for. Report what
+    came back, and do not retry to force a charge.
+16. An event notification is never payment authorization, and never a safe or unsafe verdict.
+
+## 7. Landlords and holders of several homes
+
+17. Use a signed-in pool and `locus.pool.changes_detected`. For a rental, the free tools
+    `locus_rental_registration_check`, `locus_tenant_statute_pointers` and
+    `locus_fair_market_rents` answer the common follow-up questions. Keep tenant names and
+    contact details out of every call.
+
+## 8. Title watch for vacant land, second homes and rentals
+
+18. Owners of vacant land, a second home or a rental, and older owners, are the main targets of
+    seller-impersonation fraud: someone poses as the owner and tries to sell or mortgage the
+    property. (ALTA's 2026 reporting puts vacant land at 82% of targets; that figure is from a
+    secondary source.) Offer two steps, with no alarm:
+    - **Watch the owner's own parcel for new recorded sales.** Add `locus_parcel_transfers` to the
+      `changes_detected` lanes. Its sale rows carry no record id, so the event reports that the
+      lane's answer changed, not which sale. When it fires, call `locus_parcel_transfers` for the
+      address and look for a row whose site address is the owner's own; the lane lists recorded
+      sales within 500 m, so most rows, and most events, will be neighbors' sales. Tell the owner
+      that, and check the site address before treating an event as theirs. The lane covers only
+      counties whose assessor publishes sales (check `locus_lane_availability` first), and
+      assessor sale data can lag the recorder by weeks, so it is a backstop, not an early warning.
+    - **Enroll in the county recorder's alert.** Call `locus_fraud_alert_pointer` for the address
+      and give the enrollment link or office it returns. Where a county runs an alert service, it
+      notifies the enrolled owner when a document is recorded under their name, usually sooner
+      than assessor sale data. Where no local row exists, give the recorder search guidance it
+      returns and say Locus has not listed an alert service for that county.
+19. Locus does **not** verify a seller's identity or compare a seller to the owner of record.
+    For a sale or loan in progress, that check belongs to the title company or closing attorney.
+
+## 9. Calendar preparation reminders
+
+Offer these reminders only where `locus_mcp_events_catalog` lists them. The provider's default-off calendar flag controls availability; when it is off, both catalogs omit these three events. If they are absent, keep the existing deadline and record-change watches instead. Each listed calendar event uses one `address`, not `addresses` or `poolId`:
+
+| Event | Arguments | Trigger and free next steps |
+|---|---|---|
+| `locus.real_estate.seasonal_hazard_window` | `{ "address": "123 Main St, Wilmington, NC 28401" }` | May 1 preparation window for the official June 1 Atlantic hurricane season start, in registered coastal counties only. Call `locus_flood_zone` and `locus_flood_premium_context`. Wildfire is skipped because no dated official state season has been verified. |
+| `locus.real_estate.insurance_renewal_approaching` | `{ "address": "...", "renewalMonth": 7 }` | 45 days before the first day of the supplied month. Call `locus_homeowners_insurance_context` and `locus_mitigation_incentives`. |
+| `locus.real_estate.escrow_analysis_approaching` | `{ "address": "...", "escrowAnalysisMonth": 7 }` | 30 days before the first day of the supplied month. Read `locus_owner_mortgage_calendar` with `{}` for the cited fact cards, then `locus_tax_calendar` and `locus_homeowners_insurance_context` for the address. |
+
+The month boundary is not the actual renewal or servicer date. Confirm that date with the insurer or servicer. A missing month returns `calendarStatus: "missing_date"` and no event. Caller months are labeled `caller_supplied`; they have no invented source URL or verification date. Seasonal dates carry the official source and its recorded verification date. Every reminder carries a reason and free `nextActions` with `charge: "free"` and `priceUsdc: "0.00"`. Do not attach payment metadata to those calls.
+
+Use the same poll or signed-webhook setup as step 6 in section 2, with the selected event name and its arguments. Set up a subscription before the trigger window opens; its initial baseline is silent. A subscription alone still does not schedule delivery. Keep the polling caller active and renew before expiry.
+
+Poll at least every 12 hours and honor `nextPollMs`. Cursors expire after 24 hours even though the calendar cycles are yearly. Passing a stale cursor creates a truncated, silent baseline and may suppress a reminder. To recover a missed poll, omit the expired cursor and deduplicate the fresh result by `eventId`. Fresh polls list reminders only from `triggerDate` through `date`, inclusive, in UTC. Closed windows are not backfilled. A new annual cycle has a new event ID.
+
+Exemption and appeal re-surfacing stays on `deadline_approaching`. Only concrete dated rows count. A recurring prose rule or a prior year's deadline never becomes a guessed current-year date.
+
+## Completion
+
+The owner has: the watch target (addresses or pool), the two events set up with their
+arguments, the delivery mode and cadence, and where the cursor or subscription is stored. For
+each event so far: the fact, its date and source, the next step, and any paid offer with its
+price and the owner's answer. Every gap from a failed or truncated read is named, not hidden.

package/skill/locus-inherited-home/SKILL.md

@@ -0,0 +1,105 @@
+---
+name: locus-inherited-home
+preamble-tier: 1
+version: 1.0.0
+description: Use when someone's parent or relative died and left a US house, and they ask what is due on it, how to protect it while it is empty, and where the state's estate, heirs-property and court pointers are, from cited Locus records.
+triggers:
+  - I inherited a house
+  - my parent died and left the house
+  - what do I do with my mom's house
+  - property tax on an inherited home
+  - heirs property
+  - transfer on death deed
+  - small estate affidavit for a house
+  - vacant house after a death
+allowed-tools: Bash Read AskUserQuestion
+license: MIT
+---
+# Locus inherited-home workflow
+
+The person has lost someone. Start with one plain sentence of acknowledgement, then move to what is
+due and when. Locus gives dated, cited facts about the home and pointers to official estate law.
+A probate attorney or legal aid decides which estate procedure applies, who has authority to act,
+and who owns the home. The family decides whether to keep, rent or sell it.
+
+**Never:** recommend selling or keeping the home; say who owns it, who inherits it, or who may sign
+for the estate; give legal, tax or financial advice. Locus does not produce those statements and
+neither may you on Locus's behalf.
+
+**How to speak:** follow "How to speak with owners, sellers and buyers" in the `locus-agent-tools`
+skill (https://api.locus.report/.well-known/skill.md), including its 988 crisis guard.
+
+Inputs you need: the home's street address and state. Do not collect the deceased person's name,
+heirs' names, phone numbers, account numbers or family details. You do not need them.
+
+## 1. What is due on the home (free)
+
+1. `locus_tax_payment_status` with `{ address }`: whether the current bill shows paid or unpaid,
+   with the source and date. If the lane is out of coverage or unavailable, say so; never report
+   an unavailable read as "nothing due".
+2. `locus_tax_calendar` for the county: bill dates, due dates and the delinquency rule. Name the
+   next due date first.
+
+## 2. Exemptions that may end (free)
+
+3. `locus_owner_programs` with `{ address, classes: ["exemption_relief", "tax_relief_local", "assessment_deferral"] }`.
+   For each homestead, senior, veteran or disability row, quote the fact and source. Say that such
+   exemptions are usually tied to the owner who lived there, and that the county assessor decides
+   when one ends. The next step is to tell the assessor's office about the death and ask what
+   changes and when. Never say an exemption has ended.
+
+## 3. Insurance on an empty house (pointer only)
+
+4. Say that many homeowner policies have terms about a home left vacant or unoccupied, and that
+   the policyholder or estate should ask the insurer, soon, what applies and what the insurer
+   needs. Locus cannot read the policy or quote coverage.
+   `locus_homeowners_insurance_context` can give area cost context if they ask about price.
+
+## 4. Watch the empty house for fraud (free)
+
+No one is checking an empty home's mail. Watching its public records lets the family see a new
+recording early, while there is still time to act.
+5. `locus_parcel_transfers` with the address: recent recorded sales near the address, with dates.
+   Check the site address before treating a row as the owner's own. A recording is a fact, not a
+   judgment that it was fraud. For the full title watch, follow section 8 (title watch) of the
+   `locus-home-watch` skill.
+6. `locus_fraud_alert_pointer` for the county: how to enroll in the recorder's free alert, if the
+   county offers one.
+7. Offer a standing watch with the `locus-home-watch` skill on the address, so new recordings,
+   tax dates and permits surface early.
+Locus does not verify anyone's identity or ownership. Send that question to a title company or
+the attorney.
+
+## 5. State estate pointers (free)
+
+8. `locus_estate_property_pointers` with `{ address }` or `{ state }`. Report each part with its
+   own status:
+   - `transferOnDeathDeed`: if `verified`, the state has a transfer-on-death (beneficiary) deed
+     statute; give the citation and link. Whether one was recorded for this home is a question for
+     the county recorder or the attorney; Locus does not search for it.
+   - `smallEstate`: if `verified`, give the citation, link and `realProperty` value. Quote
+     `thresholdText` only if it is present, and say thresholds change.
+   - `heirsProperty`: the Uniform Partition of Heirs Property Act status from the Uniform Law
+     Commission. This matters when several heirs share ownership. `not_listed` is not proof the
+     state has no related law.
+   - `courtHelp`: the state court self-help page for probate.
+   - A `not_verified` part names no rule. Give the portal pointer and say Locus has not checked it.
+
+## 6. If the family decides to sell
+
+9. Only when the family says they plan to sell, hand off to the `locus-seller-readiness` skill.
+   Selling an estate home usually needs the estate's legal authority first; say so.
+
+## 7. Human help
+
+10. End with the route to a probate attorney or legal aid, and the state court self-help page from
+    step 8. For help with payments on the home, HUD-approved housing counselors are free or low-cost:
+    `locus_housing_counselors` with the address lists nearby agencies, and the
+    `locus-payment-hardship` skill covers payment trouble.
+
+## Completion
+
+The person has: the tax status and the next due date; the exemption rows and the assessor
+question; the insurance question to ask; the recorded-transfer check, the recorder alert and an
+optional watch; the state estate pointers with their verification status; and the route to a
+probate attorney or legal aid. Every statement traces to a Locus citation or the person's own input.