Ha Api
ListedProvides API guidance and assistance for agent workflows.
Install on your platform
Showing Claude Code. One command installs this skill into any of the agents below.
- 1
Run this in your project
terminal$ npx skills add nodnarbnitram/claude-code-extensions --skill ha-api -a claude-code Uses the open-source
skillsCLI and needs Node.js. Add-gto install it for your user instead of this project.
What we know about this skill
Publisher
nodnarbnitram
Taken from the source listing. We haven't verified who controls this account.
Install target
Live repository
Not pinned. Installing fetches whatever the repository holds at the time you run the command.
Automated safety checks
This skill failed 1 of 6 checks. A failure is not proof of bad intent; it means something in the code needs a human to look at it before you run it.
No undeclared network calls: failed
Contacts 1 host that is neither well-known infrastructure nor declared in the skill's frontmatter: 192.168.1.100.
Every host the skill dials — from its scripts, its config endpoints or the commands it tells the agent to run — is either well-known package and API infrastructure or declared in its own frontmatter. Links in documentation are not counted.
Hosts contacted
192.168.1.100undeclaredWhat it found (3 of 4)
- .claude/skills/ha-api/README.md:100contacts 192.168.1.100
export HA_URL="http://192.168.1.100:8123" - .claude/skills/ha-api/SKILL.md:38contacts 192.168.1.100
export HA_URL="http://192.168.1.100:8123" - plugins/cce-homeassistant/skills/ha-api/README.md:100contacts 192.168.1.100
export HA_URL="http://192.168.1.100:8123"
Declares what it does: passed
SKILL.md parses and declares a name and a description.
SKILL.md exists, its frontmatter parses, and it declares a name and a description.
No obfuscated payloads: passed
No encoded or obfuscated payloads.
No base64, hex or compressed blob is decoded and then executed, and no encoded shell commands.
No credential access: passed
Reads no keys, tokens, keychains or credential files.
Neither the code nor the SKILL.md instructions read SSH keys, cloud credentials, keychains, token stores, browser cookie databases or dotfiles that hold secrets.
No pipe-to-shell installers: passed
No pipe-to-shell or download-and-run installers.
No `curl … | sh` pattern, in the code or in the instructions, that runs code fetched at run time.
Pinned to a commit: passed
Scanned nodnarbnitram/claude-code-extensions at 35e7f7deae.
The exact upstream commit SHA that was scanned is recorded, so the result refers to specific bytes.
- Commit
- 35e7f7deae
- Manifest
- .claude/skills/ha-api/SKILL.md
- Scanned
- 4 files, 1,954 lines
- Copies in repo
- 2 — all of them scanned
About this skill
What it does
This skill provides guidance and assistance for integrating with the Home Assistant REST and WebSocket APIs. It helps prevent common errors encountered during API integration, such as authentication issues, incorrect state formatting, and improper error handling. By leveraging this skill, users can save time and reduce token usage compared to manual API discovery and implementation.
When to use it
- When building external integrations with your Home Assistant instance.
- When needing to manage the state of devices within Home Assistant programmatically.
- For real-time communication and event subscriptions via the WebSocket API.
- To troubleshoot issues related to authentication, data formatting or service calls in Home Assistant.
- When aiming for efficient token usage when interacting with the Home Assistant API.
Key capabilities
- Prevents 5+ common Home Assistant API integration errors (authentication, WebSocket lifecycle, state format, error handling, service call domain/service mismatch).
- Reduces token overhead by approximately 30% compared to manual discovery.
- Speeds up setup time from 15-20 minutes (manual) to 2-5 minutes.
- Provides guidance on authentication using Long-Lived Access Tokens.
- Offers a quick start guide for testing REST API connectivity.
Example prompts
- "How do I authenticate with the Home Assistant API?"
- "What is the correct format for state data when making an API request?"
- "Explain how to handle WebSocket lifecycle management in Home Assistant."
- “What are common errors when calling a service via the REST API?”
Tips & gotchas
- You'll need to create a Long-Lived Access Token within your Home Assistant UI and securely store it.
- Ensure you prefix Bearer tokens with "Bearer " in the Authorization header.
- Understand the difference between using the REST API (for one-time requests) versus the WebSocket API (for real-time events).