farmos-observations

What This Skill Does

The farmos-observations skill acts as an intelligent field scout for agricultural operations using the farmOS platform. It bridges the gap between raw field activity—such as spotting pests, noticing crop distress, or identifying environmental damage—and the structured digital records required for farm management. The skill provides an AI-powered interface that translates informal voice notes, text messages, or photo-based scouting reports into structured database observations. By acting as a central hub for field intelligence, it allows users to perform quick data entry while on the move, ensuring that field issues are logged, categorized, and linked to specific locations without needing to navigate complex web forms.

Installation

To add this skill to your OpenClaw environment, execute the following command in your terminal:

clawhub install openclaw/skills/skills/brianppetty/farmos-observations

Ensure that your local authentication script (~/clawd/scripts/farmos-auth.sh) is configured correctly, as this skill requires valid JWT tokens to interface with your farmOS backend. The skill automatically manages token rotation; however, if you encounter 401 Unauthorized errors, ensure your environment variables are correctly populated.

Use Cases

This skill is designed for daily field operations. Common use cases include:

• Pest & Disease Monitoring: Rapidly logging reports of blight, fungal outbreaks, or insect damage while physically traversing fields.
• Crop Condition Reporting: Documenting growth milestones, nutrient deficiencies, or signs of environmental stress like heat or water damage.
• Incident Logging: Recording broken fencing, leaking irrigation lines, or other infrastructure issues that require immediate follow-up.
• Activity Review: Querying the status of field conditions over a specific timeframe to identify recurring issues in specific plots.

Example Prompts

1. "I found some signs of spider mites in field 4, can you create an observation and flag it as urgent?"
2. "What has been reported in field 12 over the last week?"
3. "The beans in the north block look really yellow, can you log a crop condition observation?"

Tips & Limitations

• Data Integrity: Always use the /api/observations endpoint for listing items. Do not rely on summary dashboards for granular data as they are designed for high-level statistics only.
• Service Stability: The backend service at http://100.102.77.110:8008 is known to occasionally experience restart loops. If the bot reports that it cannot reach the server, wait a few moments before retrying.
• Communication Clarity: While the AI is trained to handle natural language, providing specific field identifiers ensures the data is accurately mapped in farmOS. If you report an issue, the bot will typically follow up by asking if you would like to generate a work order task based on your observation.