agentleFS
tonylofgrentonylofgren/aurora-smart-home/api-catalog/SKILL.md

API Catalog

Skill109 starsChanged 10 months agoMITView on GitHub

Reference guide for connecting popular APIs to Home Assistant via Node-RED, YAML, or custom integrations. Covers authentication, endpoints, and complete working examples for: energy APIs (Tibber, Nordpool), weather (SMHI, OpenWeatherMap, yr.no), transport (SL, Trafikverket, Resrobot), smart home clouds (Shelly, Tuya, Philips Hue, IKEA), and global APIs (OpenAI, Spotify, Google Calendar, Telegram, GitHub). Use this skill whenever the user mentions a specific external service, API, or data source they want to connect to Home Assistant - even if they don't say "API".

  • Reads credentials

The file

We split this skill into the rules it gives an agent

3 rules. About 0 are common, 2 are distinctive, and 1 is very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈2

    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:

    Never paste real tokens into chat, flows that get exported, or YAML committed to git.

    line 34
  2. Distinctive:

    Read the relevant reference file for auth setup and endpoints

    line 39
  3. Very specific:

    Full integration: Use ha-integration skill with the polling-integration template

    line 70

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 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

API Catalog for Home Assistant

Reference skill for connecting external APIs and services to Home Assistant.

Overview

This skill covers authentication patterns and working code examples for connecting popular APIs to Home Assistant via three methods:

  • Node-RED - HTTP request node flows (fastest to get running)
  • HA YAML - rest sensor and rest_command (good for simple polling)
  • Custom integration - Full HACS-publishable Python component (use ha-integration skill)

The Iron Law

CREDENTIALS IN SECRETS - NEVER HARDCODED IN FLOWS OR YAML

API keys belong in Node-RED credentials, ESPHome secrets.yaml, or HA secrets.yaml. Never paste real tokens into chat, flows that get exported, or YAML committed to git.

How to Use This Skill

  1. User mentions an API or service by name
  2. Read the relevant reference file for auth setup and endpoints
  3. Generate working code for the user's chosen method (Node-RED / YAML / integration)
  4. Include credential setup instructions

Reference Files

CategoryFileAPIs Covered
Energy & electricityreferences/energy-apis.mdTibber, Nordpool, Energi Data Service
Weatherreferences/weather-apis.mdSMHI, OpenWeatherMap, yr.no, Tomorrow.io
Transportreferences/transport-apis.mdSL, Trafikverket, Resrobot, Entur (NO)
Smart home cloudsreferences/smarthome-apis.mdShelly Cloud, Tuya IoT, Philips Hue, IKEA Dirigera
Global / otherreferences/global-apis.mdOpenAI, Spotify, Google Calendar, Telegram, GitHub

Authentication Patterns at a Glance

PatternHow it worksExamples
API key in headerAuthorization: Bearer {key} or X-API-Key: {key}Tibber, OpenAI
API key in URL?appid={key} appended to URLOpenWeatherMap
OAuth2Get access token first, refresh periodicallySpotify, Google
Local tokenOne-time press-button auth on devicePhilips Hue
No authPublic API, no credentials neededSMHI, yr.no, Nordpool
Basic authUsername + password Base64-encodedSome local devices

Output Methods

For each API, generate code for the method the user needs:

Node-RED: http request node + function node to parse + api-call-service to push to HA HA YAML: rest sensor platform or rest_command under configuration.yaml Full integration: Use ha-integration skill with the polling-integration template

Common Patterns

Node-RED: API key in header

{
  "type": "http request",
  "method": "GET",
  "url": "https://api.example.com/data",
  "headers": {"Authorization": "Bearer {{env.API_KEY}}"},
  "ret": "obj"
}

Node-RED: GraphQL (Tibber-style)

{
  "type": "http request",
  "method": "POST",
  "url": "https://api.tibber.com/v1-beta/gql",
  "headers": {
    "Authorization": "Bearer {{env.TIBBER_TOKEN}}",
    "Content-Type": "application/json"
  },
  "payload": "{\"query\": \"{ viewer { homes { currentSubscription { priceInfo { current { total } } } } } }\"}",
  "ret": "obj"
}

HA YAML: REST sensor

rest:
  - scan_interval: 300
    resource: https://api.example.com/current
    headers:
      Authorization: !secret example_api_key
    sensor:
      - name: "Example Value"
        value_template: "{{ value_json.data.value }}"
        unit_of_measurement: "°C"

Pre-Output Checklist

  • Credentials use !secret (YAML), Node-RED credentials, or env vars - never hardcoded
  • Rate limits respected (include scan_interval or flow timer accordingly)
  • Error handling included (Node-RED catch node or YAML timeout)
  • For OAuth2: refresh token flow explained
  • Attribution: which API endpoint, what data it returns

Integration

Pairs with:

  • node-red skill - for flow JSON implementation
  • ha-yaml skill - for YAML sensor and automation using the fetched data
  • ha-integration skill - for building a full HACS-publishable Python integration

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.