fft-farm-ops
- Repo stars 3
- Author updated Live
- Author repo FFT_nano
- Domain
- Other
- Compatible agents
-
- Claude Code
- Cursor
- Cline
- Codex
- Windsurf
- Gemini CLI
- +20
- Trust score
- 88 / 100 · community maintained
- 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 special requirements
- Permissions
-
- Read-only
- Write / modify
- Shell exec
- Network behavior
- Local-only
- Install commands
- 26 variants
Profile is derived at build time from SKILL.md and install vectors. Subject to drift from author intent.
Heads up: 未限定 allowed-tools，默认拥有全部工具权限。
---
name: fft-farm-ops
description: Operate the farm bridge through ledger reads and IPC action requests, using main-chat-only contr…
category: other
runtime: no special runtime
---
# fft-farm-ops output preview
## PART A: Task fit
- Use case: Operate the farm bridge through ledger reads and IPC action requests, using main-chat-only control flows and safety guardrails. Use when main/admin chat requests operational farm actions. runs entirely locally. Works with Claude Code, Cursor, Cline and 23 more..
- Inputs: target material, constraints, expected output, and acceptance criteria.
- Evidence boundary: follow “When to use this skill / When not to use this skill / Guardrails” and do not present inference as author intent.
## PART B: Execution result
- **01** The card summarizes the use case; runtime output centers on “Operate the farm bridge through ledger reads and IPC action requests, using main-chat-only control flows and safety guardrails. Use when main/admin chat requests operational farm actions. runs entirely locally. Works with Claude Code, Cursor, Cline and 23 more.”.
- **02** When the source has headings, the agent prioritizes “When to use this skill / When not to use this skill / Guardrails” so the result follows the author’s structure.
- **03** Typical output includes task judgment, concrete steps, required commands or file edits, validation, and follow-up options.
- **04** Risk context follows the fingerprint: read files, write/modify files, run shell commands; mostly runs locally; usually needs no extra API key.
## Running Rules
- read files, write/modify files, run shell commands; mostly runs locally; usually needs no extra API key.
- Validate with a small sample before expanding scope.
- Return the result, validation criteria, and next iteration options. Choose the trigger
The source mentions slash commands such as `/workspace`; use them first when your agent supports command triggers.
Provide inputs and boundaries
Name target files or source material, expected output, forbidden changes, and whether network or shell access is allowed. Permission fingerprint: read files, write/modify files, run shell commands.
Validate with a small run
Start with a small task and check whether the result follows “When to use this skill / When not to use this skill / Guardrails”. Inspect diffs, logs, previews, or tests before expanding scope.
Review before delivery
Confirm the final output includes a concrete result, evidence, and next action. If it stays generic, tighten inputs, boundaries, and acceptance criteria.
---
name: fft-farm-ops
description: Operate the farm bridge through ledger reads and IPC action requests, using main-chat-only contr…
category: other
source: 0-CYBERDYNE-SYSTEMS-0/FFT_nano
---
# fft-farm-ops
## When to use
- Operate the farm bridge through ledger reads and IPC action requests, using main-chat-only control flows and safety gu…
- Use it when the task has clear inputs, repeatable steps, and validation criteria.
## What to provide
- Target material, scope, expected result, and forbidden changes.
- Whether network, commands, file writes, or external services are allowed.
## Execution rules
- Organize steps around “When to use this skill / When not to use this skill / Guardrails” and keep inference separate from source facts.
- read files, write/modify files, run shell commands; mostly runs locally; usually needs no extra API key.
- Validate with a small sample before expanding the task.
## Output requirements
- Return the deliverable, key evidence, validation method, and next action.
- Mark missing information as unknown; do not invent commands, platforms, or dependencies. Evidence boundary and execution chain
The author source anchors workflow facts; repository files anchor sources and commands; Fluxly only adds fit, limitations, and quality judgment.
skill "fft-farm-ops" {
input -> user goal + target files + boundaries + acceptance criteria
context -> When to use this skill / When not to use this skill / Guardrails
rules -> SKILL.md triggers / order / output contract
runtime -> no special runtime | read files, write/modify files, run shell commands | mostly runs locally
guardrails -> usually needs no extra API key + small-sample validation + diff/log review
output -> copyable result + checklist + next iteration
}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_statusha_call_serviceha_set_entityha_restartha_apply_dashboardha_capture_screenshotha_dashboard_getha_dashboard_patchha_dashboard_validateha_canvas_get_specha_canvas_set_specha_canvas_patch_specfarm_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.
Decide Fit First
Design Intent
How To Use It
Boundaries And Review