Rental Owner Statement Repair Linker
Check your monthly statement and repair invoices for missing supporting records.
Short-term rental operations
Put the events in your complaint messages and host responses into date order.
A downloadable skill for your AI agent.
Dated response record.
Source references, missing information, and questions to review stay with the findings.
Open your download and follow the start guide. Use an AI agent that can load skill files and run the included tools.
Complaint messages and host responses. Confirm the case and period you want to check.
Copy the request below into your agent. Add the files and any task details it needs.
Check the findings against the original records. Choose where to save the report and follow up on open questions.
Use the Noise Complaint Evidence Timeline skill. Review the attached records: complaint messages and host responses. Prepare this result: dated response record. Include a source reference for each finding. List missing information and questions that need my review. Ask me to confirm the scope and where to save the report before you start.
It checks the supplied dates and time zones before ordering events. Unclear dates remain marked for review.
Complaint messages and host responses.
For this task, keep one review row for each property + complaint. Record complaint time, issue, host response, and unresolved action. Keep the source location beside each value.
Separate guest promises from completed service. Join booking dates to the correct property and turnover. Retain exact image hashes when checking reuse.
Account for local time zones, laundry turnaround, access windows, and same-day occupancy. Do not infer cleaning quality from file presence.
The helper does not infer causation, missing events, elapsed business days, or clock offsets. Equal timestamps do not establish event order.
This synthetic example shows the included check in use. Your agent uses its findings to complete your task report.
Synthetic example records
| Sample record | at: 2026-10-31T09:00:00; event: complaint time recorded |
|---|---|
| Sample record | at: 2026-10-31T10:00:00+02:00; event: Earlier UTC event |
More information is needed
This result comes from the checking tool in your download.
These are synthetic records from the bundled example.
{"at": "2026-10-31T09:00:00", "event": "complaint time recorded", "id": "r1", "key": "property + complaint / SYNTHETIC-001"}{"at": "2026-10-31T10:00:00+02:00", "event": "Earlier UTC event", "id": "r2", "key": "property + complaint / SYNTHETIC-001"}After purchase, extract the ZIP. Run these commands from the skill folder. Use a new output folder.
python3 scripts/checks.py
python3 scripts/audit.py assets/example.json \
--files-root assets/sample-files --output-dir example-result
Expected exit code: 2. Code 0 means no helper finding. Code 1 means a finding or review item. Code 2 means incomplete or invalid input.
The check uses the records you supply. Review each finding against the original documents.
Ask your agent to save the completed task report in a folder you choose. The report template includes the result, source references, missing information, and next actions.
Tonotes does not receive your work documents through this website. Documents you share with an AI service follow that service's storage settings.
US$11 includes one skill in a ZIP with 18 files. You receive the instructions and tools to run the task with your own records.
Use an agent that supports SKILL.md instructions and Python 3.10 or later with SQLite. Your AI-agent service is separate.
Start with complaint messages and host responses. Confirm the case, period, and source versions before the review.
Use property, stay, turnover, room or task to keep records distinct. The agent records the original value, an exact quote, and the source location.
Check date precision and time zones, then order valid events. Run the Python helper on the structured records. Check each finding against its source.
Prepare the task result: dated response record. Include missing evidence, unresolved questions, and the next action for each open item.
Eight synthetic cases check the tool locally. Live-agent accuracy on real documents has not been tested.