← fixRAgentCONTENT HISTORY
WHAT CHANGED
Update to fixRAgent
Snapshot Oct 26, 2026 · 18:06 UTC · version 1.0.3
Collection source: downloaded plugin package.
First saved snapshot
No earlier snapshot is available to establish a change.
Save fixRAgent 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 when a property manager or landlord wants a short text or email to send a tenant or resident about a maintenance problem that fixRAgent has triaged. Turns a fixRAgent Triage Profile (from assess_property_photo, get_triage_profile or a fixragent.com/c/ link) into a plain, calm message using only what the profile says.",
"included_files": [],
"name": "resident-reply",
"skill_md_contents": "---\nname: resident-reply\ndescription: Use when a property manager or landlord wants a short text or email to send a tenant or resident about a maintenance problem that fixRAgent has triaged. Turns a fixRAgent Triage Profile (from assess_property_photo, get_triage_profile or a fixragent.com/c/ link) into a plain, calm message using only what the profile says.\n---\n\n# Write a resident reply from a fixRAgent Triage Profile\n\n## Get the profile\n\n- If a fixRAgent result is already in this conversation, use it.\n- If the person gives a `fixragent.com/c/<id>` link or a diagnosis id, call `get_triage_profile` with the id. That read needs a fixRAgent key; if it returns an error saying no key was sent, ask the person to paste what the link shows instead.\n- If there is only a photo, run the `triage-maintenance-photo` skill first.\n- If the result has `sample: true`, stop: it is a sample, not an assessment of this resident's problem. Say so and do not write a reply from it.\n\n## Write the message\n\nBuild it from these fields only:\n\n- `core.resident_explanation`: the core of the message. Keep its meaning; you may smooth the wording.\n- `core.tier` (EMERGENCY, TODAY, THIS WEEK or WHENEVER): sets how the message opens. Do not promise a visit time; the manager decides that. Leave a clear placeholder such as `[visit time]` for them to fill in.\n- `core.trade_required`: if the manager is sending someone, you may say which trade (for example \"a plumber\"). If it is null, do not name one.\n- `core.safety_hazard` / `core.hazard_detail`: if true, put the safety instruction first and in plain words.\n- `share_url`: include it only if the manager wants the resident to see the Triage Profile.\n\nRules:\n\n- For EMERGENCY, or anything involving fire, smoke, a gas smell, someone hurt or water on electrics, the first line tells the resident to get clear and call 911 (or the local emergency number) if there is immediate danger.\n- Keep a text under about 320 characters unless the manager asks for more. An email can be longer but stays short.\n- No blame, no legal language, no costs, no repair instructions the profile did not give, and nothing about who pays.\n- Sign with the manager's name or company if given; otherwise leave `[your name]`.\n\nOffer the draft once, then ask whether they want it shorter, warmer or more formal.\n"
}SHA-256 of public snapshot: 78f99af41793c5fdf4d7f786156ba8f55e0a845bb84b0449681a0e46d51268b2