fft-farm-bootstrap
Skill4 starsChanged 8 months agoMITView on GitHub
Bootstrap farm mode in demo or production, including Home Assistant startup, token onboarding, env wiring, and handoff to onboarding/validation.
- Reads credentials
In this repository23 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- add-telegramSkill
- add-telegram-swarmSkill
- agent-browserSkill
- agent-harness-engineerSkill
- autoresearch-createSkill
- autoresearch-finalizeSkill
- fft-coder-opsSkill
- fft-dashboard-opsSkill
- fft-debugSkill
- fft-farm-onboardingSkill
- fft-farm-opsSkill
- fft-host-ipcSkill
- fft-setupSkill
- fft-telegram-opsSkill
- loopsSkill
- rapid-researchSkill
- skill-mechanicSkill
- web-searchSkill
- customizeSkill
- debugSkill
- setupSkill
The file
We split this skill into the rules it gives an agent
10 rules. About 0 are common, 9 are distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈9
Distinctive · estimate
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 8
Use this skill when a user wants first-time farm setup to be frictionless.
- Distinctive: line 12
Use for first-time farm environment bootstrap in demo or production mode.
- Very specific: line 13
Use when .env farm variables and Home Assistant startup need guided setup.
- Distinctive: line 14
Use before onboarding and validation are run for the first time.
- Distinctive: line 18
Do not use for day-2 operations after bootstrap is already complete.
- Distinctive: line 19
Do not use for production control actions.
- Distinctive: line 20
Do not use when required secrets/tokens are unavailable.
- Distinctive: line 24
Never run destructive git commands unless explicitly requested.
- Distinctive: line 26
Do not expose tokens in logs or chat responses.
- Distinctive: line 33
If mode is production, bootstrap will hand off to onboarding + validation scripts.
≈ “Common” is an estimate: at least 1 in 5 of the 372,429 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
FFT Farm Bootstrap
Use this skill when a user wants first-time farm setup to be frictionless.
When to use this skill
- Use for first-time farm environment bootstrap in demo or production mode.
- Use when
.envfarm variables and Home Assistant startup need guided setup. - Use before onboarding and validation are run for the first time.
When not to use this skill
- Do not use for day-2 operations after bootstrap is already complete.
- Do not use for production control actions; use farm ops/validation skills instead.
- Do not use when required secrets/tokens are unavailable.
Guardrails
- Never run destructive git commands unless explicitly requested.
- Preserve unrelated worktree changes.
- Do not expose tokens in logs or chat responses.
Workflow
- Run:
./scripts/farm-bootstrap.sh --mode demo- or
./scripts/farm-bootstrap.sh --mode production
- If mode is production, bootstrap will hand off to onboarding + validation scripts.
- Confirm
.envhas:FARM_MODEFARM_PROFILE_PATHFARM_STATE_ENABLED=trueHA_URL,HA_TOKEN,FFT_DASHBOARD_REPO_PATH
Notes
- Home Assistant stack is Docker/Compose-based.
- FFT_nano agent runtime defaults to Docker (optional explicit host runtime).
- Browser-assisted token generation is expected.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

