fft-farm-onboarding
Skill4 starsChanged 8 months agoMITView on GitHub
Discover Home Assistant entities, auto-suggest farm mappings with confidence, confirm ambiguous mappings, and write farm-profile.json.
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-bootstrapSkill
- 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
7 rules. About 0 are common, 6 are distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈6
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 for production setup after HA is running and token is available.
- Distinctive: line 12
Use after Home Assistant is up and authenticated for production setup.
- Very specific: line 13
Use when generating or refining farm-profile.json entity mappings.
- Distinctive: line 14
Use before production validation gate checks.
- Distinctive: line 18
Do not use before HA connectivity/token setup is complete.
- Distinctive: line 19
Do not use for live farm control actions.
- Distinctive: line 20
Do not use when only read-only status checks are requested.
≈ “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 Onboarding
Use this skill for production setup after HA is running and token is available.
When to use this skill
- Use after Home Assistant is up and authenticated for production setup.
- Use when generating or refining
farm-profile.jsonentity mappings. - Use before production validation gate checks.
When not to use this skill
- Do not use before HA connectivity/token setup is complete.
- Do not use for live farm control actions.
- Do not use when only read-only status checks are requested.
Workflow
- Run:
./scripts/farm-onboarding.sh
- Review suggested entity mappings.
- Confirm or override medium/low-confidence mappings.
- Persist profile to
FARM_PROFILE_PATH. - Run validation next:
./scripts/farm-validate.sh
Output
- Writes
data/farm-profile.jsonby default. - Sets
validation.statustopendingwhen mappings are complete but not validated.
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.

