Install
openclaw skills install property-tax-assessment-review-kitOrganize a property tax assessment notice, deadline, evidence checklist, assessor questions, and appeal packet outline before the review window closes.
openclaw skills install property-tax-assessment-review-kitThis skill helps organize facts and paperwork for reviewing a property tax assessment or reassessment notice. It does not provide legal, tax, appraisal, real estate, or jurisdiction-specific advice. It does not estimate official property value, determine whether an appeal should be filed, complete official forms, contact government offices, or guarantee savings.
The user must verify local rules, deadlines, filing requirements, evidence standards, hearing procedures, and official forms with the relevant assessor, tax office, assessment review board, county, city, or qualified professional.
Do not ask for full parcel account credentials, payment details, Social Security numbers, national ID numbers, tax portal passwords, bank information, or copies of private identity documents. Use placeholders for sensitive identifiers.
Use this skill when the user needs to:
Do not use this skill to:
Ask for user-provided details only:
If the appeal deadline is missing or unclear, make deadline verification the first action item.
Follow this sequence:
Start with this table:
| Item | User-provided details |
|---|---|
| Jurisdiction | [city/county/state/province/country] |
| Notice date | [date] |
| Appeal or review deadline | [date or unknown] |
| Property type | [home/condo/rental/land/commercial/other] |
| Current assessed value | [amount] |
| Prior assessed value | [amount or unknown] |
| Change amount or percentage | [amount/percent if user provides enough information] |
| Main concern | [too high / record error / exemption issue / condition issue / comparable sales / other] |
| Contact already made | [none or summary] |
Do not calculate official tax impact unless the user provides all numbers and asks for simple arithmetic. Label any arithmetic as user-provided estimate, not advice.
Create a checklist for the user to compare against the notice and public record:
Mark each as "verified," "possible error," "unknown," or "not applicable."
Group evidence by type:
Suggest a simple folder structure:
Property Tax Assessment Review - [Property Short Name]
01 Notice and Deadlines
02 Property Record Verification
03 Comparable Sales
04 Condition Photos and Repair Evidence
05 Exemptions and Prior Assessments
06 Assessor Questions and Call Log
07 Appeal Draft and Submission Receipts
Use consistent filenames:
YYYY-MM-DD_notice_[jurisdiction].pdf
YYYY-MM-DD_photo_[issue].jpg
YYYY-MM-DD_comparable_[address-or-short-label].pdf
YYYY-MM-DD_call-log_assessor-office.txt
Do not require the user to upload or expose sensitive documents inside the chat.
Draft neutral questions such as:
Do not argue with the office in the script. The goal is to learn the rules and next steps.
Use this table:
| Date/time | Office or person contacted | Method | Question asked | Answer received | Reference number | Next action | Follow-up date |
|---|---|---|---|---|---|---|---|
| YYYY-MM-DD HH:MM | Assessor office | Phone/email/portal/in person |
Keep the tone factual and neutral.
Create an outline, not a final legal filing:
Assessment Review Narrative Outline
1. Notice being reviewed
- Jurisdiction: [jurisdiction]
- Notice date: [date]
- Property: [short property description]
- Assessed value: [amount]
- Deadline: [date]
2. Requested review issue
- I am requesting review of [specific issue: assessed value / property record detail / exemption / classification / condition].
3. Factual basis
- Fact 1: [record error, comparable evidence, condition issue, or exemption fact]
- Fact 2: [supporting fact]
- Fact 3: [supporting fact]
4. Supporting evidence attached or planned
- [document/photo/comparable]
- [document/photo/comparable]
5. Questions or requested correction
- [question or correction request]
Use plain language. Avoid statements the user cannot support with documents.
Build a tracker with conservative reminders:
| Date | Deadline or task | Owner | Status | Notes |
|---|---|---|---|---|
| [date] | Verify appeal deadline and filing method | User | Not started | Official source needed |
| [date] | Gather notice and prior assessment | User | ||
| [date] | Check property record details | User | ||
| [date] | Gather comparable or condition evidence | User | ||
| [date] | Ask assessor office questions | User | ||
| [date] | Decide informal review, formal appeal, professional help, or no action | User | ||
| [date] | Submit or confirm no submission | User | ||
| [date] | Save confirmation receipt | User |
If a deadline is close, advise the user to verify the official deadline and filing method immediately.
Summarize options without choosing for the user:
Copy and paste one of these into your AI assistant with your details filled in:
Assessment notice seems too high: "I just received my county property tax assessment notice dated May 5. The assessed value jumped from $320,000 to $405,000 with no change to the house. The appeal deadline is June 30. I have three recent comparable sales from my neighborhood showing lower values. Help me organize an appeal packet."
Unsure where to start: "My property tax reassessment arrived and I don't know if it's worth appealing. The building value went up $50K but the land value stayed the same. Deadline is in 3 weeks. I have last year's notice and some photos of needed repairs. Walk me through what to verify and what evidence to gather."
Preparing for assessor call: "I want to call the assessor's office about my notice but I'm nervous. The square footage they listed is wrong (they show 2,400 but it's 1,850 per my appraisal). Draft neutral questions I can ask and help me organize my comparable sales before the deadline."
Return the result in this order:
Keep the output practical, neutral, and evidence-focused. The goal is to help the user organize a review packet before the deadline, not to provide legal or tax advice.