Update to Hfield

{
  "description": "Use for requests to view HField carrier trucks or load reports, get move suggestions, or change truck settings through the HField MCP tools.",
  "included_files": [],
  "name": "hfield-operations",
  "skill_md_contents": "---\nname: hfield-operations\ndescription: Use for requests to view HField carrier trucks or load reports, get move suggestions, or change truck settings through the HField MCP tools.\n---\n\n# HField operations\n\nWhen the user's intent is clear and the HField tool is available, call it directly. Do not run tool discovery or a roster check before every request. Respect any discovery or approval step the host requires.\n\n- \"My trucks\" or a fleet status request: call `list_trucks`.\n- \"Last week loads\" or a load, revenue, or payment report: call `get_loads_report`. The default period runs from seven days ago through today in New York time. Omit dates for that period; supply explicit dates for a different requested period.\n- Truck status, pickup radius, or distance limits: call `update_truck_params`.\n- Truck ZIP, availability, or next-day offers: call `update_truck_location`.\n- State restrictions: call `update_truck_states`; use `enable_all_states` to remove every restriction.\n- Move suggestions: call `where_to_move` with a known truck or an explicit ZIP and equipment type.\n\nFor a truck write, use its ID from a fresh `list_trucks` result. Reuse a fresh result already in the conversation; otherwise list once to identify the truck. Ask only when the truck or a required value is ambiguous. A ZIP update requires an explicit availability time with UTC offset. Apply only the requested changes.\n\nInspect each write result before confirming success. If the result is unverified, say so and do not automatically retry the write. Keep routine replies brief and report only values returned by the tools.\n"
}