fixRAgent

View saved version →

---
name: resident-reply
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.
---

# Write a resident reply from a fixRAgent Triage Profile

## Get the profile

- If a fixRAgent result is already in this conversation, use it.
- 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.
- If there is only a photo, run the `triage-maintenance-photo` skill first.
- 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.

## Write the message

Build it from these fields only:

- `core.resident_explanation`: the core of the message. Keep its meaning; you may smooth the wording.
- `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.
- `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.
- `core.safety_hazard` / `core.hazard_detail`: if true, put the safety instruction first and in plain words.
- `share_url`: include it only if the manager wants the resident to see the Triage Profile.

Rules:

- 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.
- Keep a text under about 320 characters unless the manager asks for more. An email can be longer but stays short.
- No blame, no legal language, no costs, no repair instructions the profile did not give, and nothing about who pays.
- Sign with the manager's name or company if given; otherwise leave `[your name]`.

Offer the draft once, then ask whether they want it shorter, warmer or more formal.

View saved version →

---
name: triage-maintenance-photo
description: Use when someone shares or points to a photo of something in a building (a leak, a water heater, a boiler, an electrical panel, an appliance, damage) and wants to know what it is, how urgent it is, and who to call. Also use when a property manager, landlord or maintenance team mentions a maintenance request, a resident's complaint or something broken, leaking or not working, even with no photo yet; when they ask what fixRAgent does; or when they have just added fixRAgent and want to try it. Calls the fixRAgent tools (try_sample with no photo or key, assess_property_photo with a photo) and presents the result in plain words.
---

# Triage a maintenance photo with fixRAgent

You have the fixRAgent MCP server (`fixragent`) with three tools: `try_sample`, `assess_property_photo` and `get_triage_profile`. Use them; do not guess a triage yourself and present it as fixRAgent's.

## 1. Danger first

If the person describes something happening right now that needs emergency services (fire, smoke, a gas smell, someone hurt, sparking, water on live electrics), tell them to call 911 (or their local emergency number) and get people clear first. A tool call is not a substitute for that. You may still run the assessment afterwards if they want a record.

## 2. No photo yet, or "what does this do?"

Call `try_sample`. It needs no key and no input. Say plainly that the result is a SAMPLE: a stored fixRAgent assessment of a sample photo from fixRAgent's test set, not a read of any photo of theirs.

## 3. Assess their photo

Call `assess_property_photo` with:

- `image_base64`: the photo's bytes, base64-encoded. JPEG, PNG or WebP, at least 1 KB and at most 3 MB once decoded. If the photo is a file on disk you can read, encode it (for example `base64 -w0 photo.jpg` on Linux, `base64 -i photo.jpg` on macOS). If you can see the image but cannot get its bytes, say so and ask for the file; do not describe the image in words and pass that off as the photo.
- `mime_type`: `image/jpeg`, `image/png` or `image/webp`, matching the bytes.
- `problem_text` (optional): the problem in the reporter's own words, if you have them. Do not add your own diagnosis to it.

Before sending, tell the person the photo will be sent to fixragent.com for assessment. Location metadata is stripped on fixRAgent's server, not before the photo leaves their machine.

## 4. Present the result

Read the fields from the tool's result. Lead with the four things a manager acts on, in plain words:

1. **What it is**: `core.asset_type` (and `core.photo_subject` if it helps).
2. **How urgent**: `core.tier`, exactly one of EMERGENCY, TODAY, THIS WEEK, WHENEVER. Quote the word as returned. If `core.safety_hazard` is true, say so and give `core.hazard_detail`.
3. **Who to call**: `core.trade_required`. If it is null, say no trade was named (for example because no fault was visible); do not invent one.
4. **What to tell the resident**: `core.resident_explanation`, quoted.

Then:

- Whether a fault was seen: `core.fault_detected` and `core.fault_summary`. If `core.fault_visible_in_photo` is false, say the photo did not show a fault, which is not the same as "nothing is wrong".
- How many reads agreed, if `agreement` is present (for example "3 of 3 reads agreed").
- The **Triage Profile link**: `share_url`. It is a page the resident or contractor can open.
- Pass on any `warnings` the tool returned, in plain words.

## 5. Limits to state honestly

- If the result has `sample: true`, it is the stored SAMPLE, **not** an assessment of their photo. This happens when no key was sent and the keyless allowance (3 per caller in a rolling 24 hours, within a daily ceiling shared by all keyless callers) is used up. Say so, and point them to a free key at https://fixragent.com/docs#key, and send as the x-triage-key header, an Authorization: Bearer header, or ?k= on the server URL.
- The result is a triage from one photo, not an inspection. It does not replace a qualified tradesperson on site.
- Do not add costs, repair steps, part numbers or timelines the tool did not return.

## Reading one back

If someone pastes a `fixragent.com/c/<id>` link or a diagnosis id, call `get_triage_profile` with that id. It reads the saved assessment, does not re-read the photo and spends nothing from the daily allowance, but it needs a fixRAgent key: without one it returns an error saying no key was sent. In that case, ask the person to open the link and paste what it shows, or to add a free key from https://fixragent.com/docs#key.

View saved version →

---
name: work-order-note
description: Use when a property manager or maintenance coordinator wants to log a fixRAgent triage as a work order, ticket or maintenance request note. Formats a fixRAgent Triage Profile as a plain-text note that can be pasted into any property-management or maintenance software, using only what the profile says.
---

# Format a fixRAgent result as a work-order note

## Get the profile

- Use a fixRAgent result already in the conversation, or call `get_triage_profile` with a diagnosis id or the id at the end of a `fixragent.com/c/<id>` link. 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.
- If there is only a photo, run the `triage-maintenance-photo` skill first.
- If the result has `sample: true`, do not log it as a work order: it is a sample, not this property's problem. Say so.

## The note

Plain text, no Markdown tables, so it pastes cleanly into any system. Use this layout and leave out any line whose field is empty or null:

```
PRIORITY: <core.tier>
ASSET: <core.asset_type> (<core.asset_category>)
TRADE: <core.trade_required>
FAULT SEEN: <yes/no from core.fault_detected> - <core.fault_summary>
SAFETY: <core.hazard_detail, only if core.safety_hazard is true>
REPORTED AS: <problem text in the reporter's words, if given>
TELL RESIDENT: <core.resident_explanation>
TRIAGE PROFILE: <share_url>
FIXRAGENT ID: <diagnosis_id>
READS AGREED: <agreement.k> of <agreement.n>, if agreement is present
```

Rules:

- Copy `core.tier` exactly as returned (EMERGENCY, TODAY, THIS WEEK or WHENEVER). If the person's system uses its own priority names, ask how they map; do not guess.
- Add a unit, property or resident name only if the person gives it. Never invent one.
- Do not add costs, parts, schedules or a vendor the profile did not name.
- If `core.fault_visible_in_photo` is false, keep "FAULT SEEN: no" and do not soften or strengthen it.
- End with the line: `Triage from one photo by fixRAgent. Not an on-site inspection.`

If the person names their software, you may adjust the field labels to match what they tell you it uses, but keep every value as returned.