Update to GearGenius FlatRate Pro

{
  "description": "Use when a FlatRate Pro technician asks to view their toolbox inventory, record an owned tool, or update a specific tool's condition, status, location, or purchase details.",
  "included_files": [
    {
      "relative_path": "agents/openai.yaml",
      "size_in_bytes": 253
    }
  ],
  "name": "toolbox-records",
  "skill_md_contents": "---\r\nname: toolbox-records\r\ndescription: \"Use when a FlatRate Pro technician asks to view their toolbox inventory, record an owned tool, or update a specific tool's condition, status, location, or purchase details.\"\r\n---\r\n\r\n# Toolbox records\r\n\r\nUse the connected technician's inventory only. This is recordkeeping, not\r\npurchasing, payments, loan enforcement, or proof that equipment is safe to use.\r\nExplicit user instructions control which records and fields may change.\r\n\r\n1. Call `listMyTools` for inventory questions or to identify a requested item.\r\n   Report stored properties only; do not invent serial numbers, condition,\r\n   calibration records, assignments, or checkout history.\r\n2. Before an update, resolve the actual tool ID. Ask the user to distinguish\r\n   duplicate names. Viewing inventory does not authorize a change.\r\n3. For an explicitly requested new record, call `logTool` with the tool name\r\n   and only supplied brand, cost/price, category, purchase date, or notes.\r\n   Do not infer price or execute a purchase.\r\n4. For an explicitly requested edit, call `updateTool` with that ID and only\r\n   the supplied fields. `status` supports `available`, `checked_out`,\r\n   `maintenance`, `retired`; `condition` supports `excellent`, `good`, `fair`,\r\n   `needs_service`. \"Needs service\" is a condition, not a status.\r\n5. Respect client write confirmations. State the server-confirmed changed\r\n   fields and leave other properties untouched. Surface errors; do not retry\r\n   non-idempotent `logTool` after an uncertain response without checking inventory.\r\n6. Decline other-account inventory requests. If sign-in is needed, direct the\r\n   user to client OAuth, never to credential sharing in chat.\r\n\r\nExamples: \"What's in my toolbox?\" is read-only; \"Move my wrench to Bay 2\"\r\nrequires a unique item; \"Buy a new scan tool\" is outside this workflow.\r\n"
}