← SwiftProbateCONTENT HISTORY
WHAT CHANGED
Update to SwiftProbate
Snapshot Oct 27, 2026 · 06:07 UTC · version 1.0.5
Collection source: downloaded plugin package.
First saved snapshot
No earlier snapshot is available to establish a change.
Save SwiftProbate and check future changes in Following.
Up to 10 plugins free · no card required.
Compare saved observations
Download comparison JSONFull technical diff · 0 changed fields
Full snapshot data
{
"description": "Use SwiftProbate's tools to answer probate questions with verified county, institution, state, and forms data, and to help a signed-in user organize their estate. Trigger for questions about a probate court, filing fees, publication requirements, notifying a bank/brokerage/insurer about a death, state probate rules or timelines, which court forms are needed, or managing an estate's tasks, assets, ledger, or heirs.",
"included_files": [],
"name": "probate-reference",
"skill_md_contents": "---\nname: probate-reference\ndescription: Use SwiftProbate's tools to answer probate questions with verified county, institution, state, and forms data, and to help a signed-in user organize their estate. Trigger for questions about a probate court, filing fees, publication requirements, notifying a bank/brokerage/insurer about a death, state probate rules or timelines, which court forms are needed, or managing an estate's tasks, assets, ledger, or heirs.\n---\n\n# SwiftProbate probate reference\n\nSwiftProbate is probate task-management **software**. It is **not a law firm and does not provide legal advice.** Probate rules vary by state and county and change over time — present SwiftProbate's data as reference to confirm, not as a legal conclusion, and pass along the disclaimer that rides in each tool response.\n\n## When to use which tool\n\nReference (no sign-in required):\n- **search / fetch** — start here for open-ended probate reference questions. `search(query)` returns result items with ids; `fetch(id)` returns the full record.\n- **lookup_county_guide** — a specific county's probate court: courthouse address/phone/site, filing fee, publication newspapers, e-filing, county forms.\n- **lookup_institution_guide** — how to notify a bank, brokerage, insurer, or credit union about a death: estate-department contact, addresses, required documents, which accounts need probate.\n- **get_state_overview** — a state's small-estate threshold, filing deadline, creditor-claim period, timeline, fees, and procedure type.\n- **find_probate_forms** — the court forms for a state/county, with official links.\n\nEstate management (requires SwiftProbate sign-in — the first estate tool call prompts an OAuth sign-in):\n- **list_my_estates** — call first; every estate tool needs an estate_id from here.\n- **complete_onboarding** — set up a new estate and generate a personalized task checklist.\n- **get_*** — read the estate's summary, tasks, assets, heirs, transactions, documents.\n- **create_* / update_* tools** — add or update tasks, assets, ledger entries, and heirs.\n\n## How to work\n\n1. For a reference question, prefer `search` then `fetch`, or the specific `lookup_*` tool when the user named a county/institution/state. Always confirm county-level details from the tool rather than model memory.\n2. If a person wants a personalized checklist or to manage their estate, offer to connect a SwiftProbate account (the reference responses include a sign-up pointer). After they sign in, call `list_my_estates`, then help them read or update their estate.\n3. For a summary of an estate, call `get_estate_summary` with the estate_id — not `list_my_estates`, which only lists estates. Use `list_my_estates` solely to discover the estate_id, then call the specific `get_*` tool for what the user asked.\n4. Never tell the user SwiftProbate can \"complete probate\" or replace an attorney. Frame it as help understanding and organizing the process, and suggest confirming legal questions with a licensed attorney in their state when appropriate.\n"
}SHA-256 of public snapshot: 1de96b26eb549d7b66629203b0708d4482c59e2e4a6eaa839f52781ce785fbde