← 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 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.",
"included_files": [],
"name": "work-order-note",
"skill_md_contents": "---\nname: work-order-note\ndescription: 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.\n---\n\n# Format a fixRAgent result as a work-order note\n\n## Get the profile\n\n- 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.\n- If there is only a photo, run the `triage-maintenance-photo` skill first.\n- 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.\n\n## The note\n\nPlain 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:\n\n```\nPRIORITY: <core.tier>\nASSET: <core.asset_type> (<core.asset_category>)\nTRADE: <core.trade_required>\nFAULT SEEN: <yes/no from core.fault_detected> - <core.fault_summary>\nSAFETY: <core.hazard_detail, only if core.safety_hazard is true>\nREPORTED AS: <problem text in the reporter's words, if given>\nTELL RESIDENT: <core.resident_explanation>\nTRIAGE PROFILE: <share_url>\nFIXRAGENT ID: <diagnosis_id>\nREADS AGREED: <agreement.k> of <agreement.n>, if agreement is present\n```\n\nRules:\n\n- 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.\n- Add a unit, property or resident name only if the person gives it. Never invent one.\n- Do not add costs, parts, schedules or a vendor the profile did not name.\n- If `core.fault_visible_in_photo` is false, keep \"FAULT SEEN: no\" and do not soften or strengthen it.\n- End with the line: `Triage from one photo by fixRAgent. Not an on-site inspection.`\n\nIf 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.\n"
}SHA-256 of public snapshot: 5c9d1571f5834532e8f6f89e28d4d094f6c4e6b53038d335b356bac83105ae49