fft farm ops
- Repo stars 3
- Author repo FFT_nano
- Domain
- Other
- Author-declared agents
- No explicit declaration found; this is not inferred or tested compatibility
- Static check
- 88 / 100 · heuristic scan, not runtime safety proof
- Runtime evidence
- Not run; no isolated runtime test evidence is currently recorded
- Author / version / license
- @0-CYBERDYNE-SYSTEMS-0 · no license declared
- Token usage
- Lean
- Setup complexity
- Guided setup
- External API key
- Not required
- Operating systems
- Unspecified (assume cross-platform)
- Runtime requirements
- No explicit requirements detected
- Detected file/system behavior
-
- Read-only
- Write / modify
- Shell exec
- Network behavior
- Local-only
- Install commands
- None (reference only)
Heads up: Tool permissions are not declared; actual access depends on the runtime.
# Poll Action Results
{
"requestId": "act_1707830400_abc",
"status": "success",
"result": {},
"executedAt": "2026-02-13T10:30:01Z"
}
# FFT Farm Ops
Use this skill for farm state awareness and operational actions routed through the FFT_nano farm bridge.
## When to use this skill
- Use for reading farm ledger state and alerts.
- Use for submitting allowlisted farm control actions through IPC.
- Use when main/admin chat requests operational farm actions.
## When not to use this skill
- Do not use for onboarding/bootstrap tasks.
- Do not use outside main/admin chat for write/control actions.
- Do not use for actions outside the defined farm action allowlist.
## Guardrails
- Never run destructive git commands unless explicitly requested.
- Preserve unrelated worktree changes.
- Keep write operations main-chat-only.
- Use main/admin chat only for any operational control action.
- Never run destructive shell commands against hosts, containers, or Home Assistant.
## Read Farm State
- Primary status file: `/workspace/farm-state/current.json`
- Alert snapshot: `/workspace/farm-state/alerts.json`
- Device inventory: `/workspace/farm-state/devices.json`
- Calendar snapshot: `/workspace/farm-state/calendar.json`
- Time series: `/workspace/farm-state/telemetry.ndjson`
Read `current.json` first. Treat `stale: true` as degraded connectivity and avoid risky recommendations.
## Submit Actions
Write request files into `/workspace/ipc/actions/` with unique names like:
- `act_<unix_ts>_<rand>.json`
Request format:
```json
{
"type": "farm_action",
"action": "ha_call_service",
"params": {
"domain": "switch",
"service": "turn_on",
"data": { "entity_id": "switch.irrigation_north" }
},
"requestId": "act_1707830400_abc"
}
```
## Poll Action Results
Read `/workspace/ipc/action_results/<requestId>.json` until available.
Result format:
```json
{
"requestId": "act_1707830400_abc",
"status": "success",
"result": {},
"executedAt": "2026-02-13T10:30:01Z"
}
```
If `status` is `error`, surface the exact error and propose the safest next step.
## Action Allowlist
Only use allowlisted actions:
- `ha_get_status`
- `ha_call_service`
- `ha_set_entity`
- `ha_restart`
- `ha_apply_dashboard`
- `ha_capture_screenshot`
- `ha_dashboard_get`
- `ha_dashboard_patch`
- `ha_dashboard_validate`
- `ha_canvas_get_spec`
- `ha_canvas_set_spec`
- `ha_canvas_patch_spec`
- `farm_state_refresh`
## Minimal Examples
```json
{
"type": "farm_action",
"action": "ha_dashboard_patch",
"params": {
"dashboardFile": "/workspace/dashboard/ui-lovelace-staging.yaml",
"operations": [
{ "op": "set_theme", "theme": "storm" }
]
},
"requestId": "act_1707830400_dash"
}
```
```json
{
"type": "farm_action",
"action": "ha_canvas_patch_spec",
"params": {
"operations": [
{ "op": "set_title", "title": "Agent Canvas" }
]
},
"requestId": "act_1707830400_canvas"
}
```
## Alert Interpretation
- Critical alerts: prioritize immediate stabilization actions and ask for confirmation before control changes.
- Warning alerts: recommend monitored corrective actions.
- Normal state: suggest optimization and preventative maintenance.
- Always include context from `timeOfDay`, `season`, and weather-related states.
Sections and files
Listed in source order.
sections -> When to use this skill → When not to use this skill → Guardrails → Read Farm State → Submit Actions → Poll Action Results
terms -> Use this skill for farm state awareness and operational actions routed through the FFTnano farm bridge. · - Use for reading farm ledger state and alerts. · - Do not use for onboarding/bootstrap tasks. · - Never run destructive git commands unless explicitly requested. · Read current.json first. · Read /workspace/ipc/actionresults/<requestId>.json until available. · If status is error, surface the exact error and propose the safest next step. · - Critical alerts: prioritize immediate stabilization actions and ask for confirmation before control changes.
files/cmd -> /workspace/farm-state/current.json · /workspace/farm-state/alerts.json · /workspace/farm-state/devices.json · /workspace/farm-state/calendar.json · /workspace/farm-state/telemetry.ndjson · current.json · stale: true · /workspace/ipc/actions/
body sha256 -> c20e9821fef6
When to use this skill
Use for reading farm ledger state and alerts. Use for submitting allowlisted farm control actions through IPC. Use when main/admin chat requests operational farm actions.
When not to use this skill
Do not use for onboarding/bootstrap tasks. Do not use outside main/admin chat for write/control actions. Do not use for actions outside the defined farm action allowlist.
Guardrails
Never run destructive git commands unless explicitly requested. Preserve unrelated worktree changes. Keep write operations main-chat-only. Use main/admin chat only for any operational control action. Never run destructive shell commands against hosts, containers, or Home Assistant.
Read Farm State
Primary status file:
/workspace/farm-state/current.jsonAlert snapshot:/workspace/farm-state/alerts.jsonDevice inventory:/workspace/farm-state/devices.jsonCalendar snapshot:/workspace/farm-state/calendar.jsonTime series:/workspace/farm-state/telemetry.ndjsonSubmit Actions
Write request files into
/workspace/ipc/actions/with unique names like:act_<unix_ts>_<rand>.jsonRequest format: