agentleFS
0-CYBERDYNE-SYSTEMS-00-CYBERDYNE-SYSTEMS-0/FFT_nano/skills/runtime/fft-farm-onboarding/SKILL.md

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.

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
  1. Distinctive:

    Use this skill for production setup after HA is running and token is available.

    line 8
  2. Distinctive:

    Use after Home Assistant is up and authenticated for production setup.

    line 12
  3. Very specific:

    Use when generating or refining farm-profile.json entity mappings.

    line 13
  4. Distinctive:

    Use before production validation gate checks.

    line 14
  5. Distinctive:

    Do not use before HA connectivity/token setup is complete.

    line 18
  6. Distinctive:

    Do not use for live farm control actions.

    line 19
  7. Distinctive:

    Do not use when only read-only status checks are requested.

    line 20

≈ “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.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

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.json entity 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

  1. Run:
    • ./scripts/farm-onboarding.sh
  2. Review suggested entity mappings.
  3. Confirm or override medium/low-confidence mappings.
  4. Persist profile to FARM_PROFILE_PATH.
  5. Run validation next:
    • ./scripts/farm-validate.sh

Output

  • Writes data/farm-profile.json by default.
  • Sets validation.status to pending when mappings are complete but not validated.

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.