fft-farm-ops

Other Community

Repo stars 3
Author repo FFT_nano

Interpretation is structured for decision-making; original keeps the upstream SKILL.md unchanged.

Decide Fit First

Core job: Operate the farm bridge through ledger reads and IPC action requests, using main-chat-only control flows and safety guardrails.…
Best fit: Use it when the task has reusable inputs, steps, and validation criteria rather than a one-off answer.
Avoid forcing it: If the source lacks commands, platform support, or external-service evidence, keep those fields unknown instead of guessing.

Design Intent

Structure: The skill is organized around “When to use this skill”, “When not to use this skill”, “Guardrails”, “Read Farm State”, showing how the author expects the agent to judge fit, collect context, and produce verifiable output.
Trigger evidence: Prioritize the author’s wording around when to use it, what context to collect, and what output shape to produce.
Evidence boundary: Author text states facts, repository files prove commands and paths, and Fluxly only adds fit, limits, and usage judgment.

How To Use It

Inputs: Provide target material, scope, expected result, forbidden changes, and validation method.
Invocation: Name fft-farm-ops directly; if the source includes slash commands, start with the command and then add task context.
Validation: Start small and check whether the result follows “When to use this skill / When not to use this skill / Guardrails” before expanding.

Boundaries And Review

Dependencies: It usually needs no extra API key, so start with a small validation task.
Permissions: Declared permissions include read / write / shell-exec; ask the agent to state file, command, and rollback boundaries before acting.
Quality bar: A useful result names the deliverable, evidence, and next action. Generic prose means the task needs tighter context.

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:

{
  "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:

{
  "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

{
  "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"
}

{
  "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.

Fluxly profile Author and license come from source; runtime, permissions, and network are Fluxly detections or estimates

Fluxly category: 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
Author / version / license: @0-CYBERDYNE-SYSTEMS-0 · no license declared
Fluxly token estimate: Lean
Fluxly setup estimate: Guided setup
External API key: No requirement detected
Detected OS requirements: Unspecified
Runtime requirements: Unspecified
Detected file/system behavior: Read-only
Write / modify
Shell exec
Detected network behavior: Local-only
Install commands: None (reference only)

Profile is derived at build time from SKILL.md and install vectors. Subject to drift from author intent.

Heads up: 未限定 allowed-tools，默认拥有全部工具权限。

Output preview fft-farm-ops.preview

# Poll Action Results

{
  "requestId": "act_1707830400_abc",
  "status": "success",
  "result": {},
  "executedAt": "2026-02-13T10:30:01Z"
}

SKILL.md SKILL.md

# 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",

…

Evidence boundary and execution chain

Author text anchors workflow facts; Fluxly only indexes current sections, terms, files, and commands.

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