{"id":14336,"plugin_id":"plugin_asdk_app_6a5ba688d8008191acfb8cab7164cab5","kind":"skill","collection_source":null,"comparison_source":null,"observed_at":"2026-09-30T23:09:17.825Z","digest":"22429da88394e28662dccf2684d36f4baa64f514f4939248b3352238916012af","against":null,"payload":{"description":"Use Farmbit to locate a real orchard, run a free 30-day Sentinel-2 check, reopen a preview, or inspect temporal evidence for fields in a linked Farmbit account. Trigger for orchard satellite checks, vegetation or moisture change questions, field monitoring status, and ground-check prioritization.","included_files":[{"relative_path":"agents/openai.yaml","size_in_bytes":217}],"name":"farmbit-orchard-scouting","skill_md_contents":"---\nname: farmbit-orchard-scouting\ndescription: Use Farmbit to locate a real orchard, run a free 30-day Sentinel-2 check, reopen a preview, or inspect temporal evidence for fields in a linked Farmbit account. Trigger for orchard satellite checks, vegetation or moisture change questions, field monitoring status, and ground-check prioritization.\n---\n\n# Farmbit Orchard Scouting\n\nUse Farmbit evidence to decide where a grower should inspect first. Keep location identity, agricultural eligibility, temporal processing state, and satellite limitations explicit.\n\n## Choose The Workflow\n\n### Check An Address Or Orchard\n\n1. Call `farmbit_search_orchard_locations` with the user's address, orchard name, parcel, or locality.\n2. If results are ambiguous, show the specific candidates and ask the user to choose. Do not guess from a locality-only match.\n3. Call `farmbit_create_free_satellite_preview` with the selected `candidate_id`.\n4. Interpret `eligibility` before discussing imagery:\n   - `accepted`: continue with the returned preview and 30-day temporal state.\n   - `needs_confirmation`: explain that the boundary must be reviewed or drawn in Farmbit. Do not claim that a Farmbit preview or temporal analysis exists yet.\n   - `rejected`: state the returned reason and offer a new search. Do not call the place an orchard or estimate orchard acreage.\n5. If a preview has `temporal.status: pending`, retain its `preview_id` and use `farmbit_get_free_satellite_preview` to check it again when the user asks for an update.\n\nUse only one location mode per creation request:\n\n- A selected search result: `location_mode: \"candidate\"` with `candidate_id`.\n- A plain search when no candidate is available: `location_mode: \"address\"` with `address_query`.\n- A prepared Farmbit location: `location_mode: \"prepared_location\"` with `location_id`; add `boundary_id` only when it belongs to that location.\n- A point: `location_mode: \"point\"` with both `lon` and `lat`.\n- A known block polygon: `location_mode: \"geometry\"` with `geometry` and its truthful `geometry_source`. Use `field_boundary` only when the user has explicitly reviewed or drawn that boundary.\n\n### Inspect A Linked Field\n\n1. If the user did not identify a field unambiguously, call `farmbit_list_fields`.\n2. Match by the returned `field_id` and `field_label`; ask the user when more than one field is plausible.\n3. Call `farmbit_get_field_temporal_evidence` with the selected `field_id`.\n4. Use a 30-day lookback for current scouting. Use 60, 90, 180, or 365 days only when the user asks for a longer comparison.\n5. Request only supported indices: `ndvi`, `ndwi`, `ndmi`, `ndre`, and `evi`.\n\n## Report Evidence\n\nTreat the temporal status as authoritative:\n\n- `pending`: processing has not produced evidence yet.\n- `partial`: report only available observations and explain what is still incomplete.\n- `ready`: summarize the observed window, strongest supported change, confidence, limitations, and recommended next action.\n- `no_scenes`: say that no qualifying Sentinel-2 scenes were available in the requested window.\n- `failed`: state that processing failed and do not infer a field condition.\n\nFor `ready` or `partial` evidence:\n\n1. Name the observation window and scene or observation count.\n2. Describe where the strongest supported change occurred when the evidence provides a location or affected-area value.\n3. Describe the signal as a satellite-observed pattern, such as vegetation increase, vegetation decrease, or moisture-related change. Do not diagnose a cause.\n4. Include the returned confidence, quality, unavailable indices, and limitations.\n5. End with the returned ground-check recommendation or a cautious first inspection step.\n\n## Guardrails\n\n- Never turn missing observations into a successful result.\n- Never let agricultural appearance override a location mismatch.\n- Never describe satellite evidence as proof of disease, irrigation failure, nutrient deficiency, or another diagnosis.\n- Never invent values, dates, causes, boundaries, scenes, or recommendations.\n- Distinguish a free public check from private linked-field evidence.\n- Keep Farmbit links returned by the tools available for map review and follow-up.\n"},"changes":[],"summary":"First saved snapshot. No earlier version is available for comparison.","summary_kind":"deterministic","summary_metadata":{}}