ha-mcp-dev 8.0.0.dev2222__tar.gz → 8.0.0.dev2225__tar.gz

{ha_mcp_dev-8.0.0.dev2222/src/ha_mcp_dev.egg-info → ha_mcp_dev-8.0.0.dev2225}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: ha-mcp-dev
-Version: 8.0.0.dev2222
+Version: 8.0.0.dev2225
 Summary: Home Assistant MCP Server - Complete control of Home Assistant through MCP
 Author-email: Julien <github@qc-h.net>
 License: MIT

{ha_mcp_dev-8.0.0.dev2222 → ha_mcp_dev-8.0.0.dev2225}/pyproject.toml

@@ -4,7 +4,7 @@ build-backend = "setuptools.build_meta"
 
 [project]
 name = "ha-mcp-dev"
-version = "8.0.0.dev2222"
+version = "8.0.0.dev2225"
 description = "Home Assistant MCP Server - Complete control of Home Assistant through MCP"
 readme = "README.md"
 # Upper bound widened to <3.15 so the package installs on Home Assistant's

ha_mcp_dev-8.0.0.dev2225/src/ha_mcp/resources/skills-vendor/AGENTS.md

@@ -0,0 +1,40 @@
+# CLAUDE.md
+
+This file provides guidance to Claude Code (claude.ai/code) when working with code in this repository.
+
+## Skill Format
+
+Every skill is a `SKILL.md` file with YAML frontmatter:
+
+```yaml
+---
+name: skill-name-here
+description: >
+  When to activate this skill and what symptoms it addresses.
+---
+```
+
+Full authoring constraints: `CONTRIBUTING.md`. The one CI cannot catch:
+- `metadata.version` must be `0` on new skills — do not edit manually; CI assigns the real version on merge
+
+## Skill Authoring Principles
+
+- **Context window conservation** — only include domain-specific knowledge that agents lack; omit general programming advice
+- **Conciseness** — provide patterns and quick-reference tables, not tutorials
+- **Consistent terminology** — one term per concept throughout a skill
+- **Symptom-based triggering** — the `description` frontmatter should describe observable agent behaviors that signal the skill is needed
+- **No tool names** — reference HA REST APIs and concepts, never specific MCP tool names (e.g. `ha_rename_entity`); tool names vary by agent setup
+
+## Validation
+
+To validate locally:
+
+```bash
+uvx skills-ref validate skills/<skill-name>
+```
+
+## Reviewing Skill PRs
+
+- Judge prose as agent-consumed context, not human docs — the Skill Authoring Principles above are the review bar (e.g. an operator→result lookup table beats narrative bullets, because agents land here holding one case to resolve)
+- Skills make version-pinned claims about HA behavior — verify against source at the release tag: `gh api repos/home-assistant/core/contents/<path>?ref=2026.7.4 --jq .content | base64 -d`
+- Community PRs come from forks: base-repo `?ref=<pr-branch>` 404s; get the fork with `gh pr view <pr> --json headRepository` and fetch files from there

ha_mcp_dev-8.0.0.dev2225/src/ha_mcp/resources/skills-vendor/CLAUDE.md

@@ -0,0 +1,40 @@
+# CLAUDE.md
+
+This file provides guidance to Claude Code (claude.ai/code) when working with code in this repository.
+
+## Skill Format
+
+Every skill is a `SKILL.md` file with YAML frontmatter:
+
+```yaml
+---
+name: skill-name-here
+description: >
+  When to activate this skill and what symptoms it addresses.
+---
+```
+
+Full authoring constraints: `CONTRIBUTING.md`. The one CI cannot catch:
+- `metadata.version` must be `0` on new skills — do not edit manually; CI assigns the real version on merge
+
+## Skill Authoring Principles
+
+- **Context window conservation** — only include domain-specific knowledge that agents lack; omit general programming advice
+- **Conciseness** — provide patterns and quick-reference tables, not tutorials
+- **Consistent terminology** — one term per concept throughout a skill
+- **Symptom-based triggering** — the `description` frontmatter should describe observable agent behaviors that signal the skill is needed
+- **No tool names** — reference HA REST APIs and concepts, never specific MCP tool names (e.g. `ha_rename_entity`); tool names vary by agent setup
+
+## Validation
+
+To validate locally:
+
+```bash
+uvx skills-ref validate skills/<skill-name>
+```
+
+## Reviewing Skill PRs
+
+- Judge prose as agent-consumed context, not human docs — the Skill Authoring Principles above are the review bar (e.g. an operator→result lookup table beats narrative bullets, because agents land here holding one case to resolve)
+- Skills make version-pinned claims about HA behavior — verify against source at the release tag: `gh api repos/home-assistant/core/contents/<path>?ref=2026.7.4 --jq .content | base64 -d`
+- Community PRs come from forks: base-repo `?ref=<pr-branch>` 404s; get the fork with `gh pr view <pr> --json headRepository` and fetch files from there

{ha_mcp_dev-8.0.0.dev2222 → ha_mcp_dev-8.0.0.dev2225/src/ha_mcp_dev.egg-info}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: ha-mcp-dev
-Version: 8.0.0.dev2222
+Version: 8.0.0.dev2225
 Summary: Home Assistant MCP Server - Complete control of Home Assistant through MCP
 Author-email: Julien <github@qc-h.net>
 License: MIT

ha_mcp_dev-8.0.0.dev2222/src/ha_mcp/resources/skills-vendor/AGENTS.md

@@ -1,63 +0,0 @@
-# CLAUDE.md
-
-This file provides guidance to Claude Code (claude.ai/code) when working with code in this repository.
-
-## Project Overview
-
-This is a community-contributed collection of **Agent Skills** for Home Assistant, following the open [Agent Skills standard](https://agentskills.io/specification). Skills teach AI agents domain expertise for configuring and controlling Home Assistant. The repository doubles as a Claude Code plugin (see `.claude-plugin/plugin.json`).
-
-## Repository Structure
-
-- `skills/<skill-name>/SKILL.md` — each skill lives in its own folder with a `SKILL.md` file
-- `CONTRIBUTING.md` — skill authoring guidelines and submission workflow
-- `.claude-plugin/plugin.json` — Claude Code plugin metadata
-- `.claude-plugin/marketplace.json` — marketplace metadata for plugin discovery
-- `AGENTS.md` — symlink to `CLAUDE.md` (for agents that use `AGENTS.md` convention)
-- `.github/ISSUE_TEMPLATE/skill-rca.md` — "Report Bad Skill Advice" issue template
-
-## Skill Format
-
-Every skill is a `SKILL.md` file with YAML frontmatter:
-
-```yaml
----
-name: skill-name-here
-description: >
-  When to activate this skill and what symptoms it addresses.
----
-```
-
-Constraints from CONTRIBUTING.md:
-- Max **500 lines** per SKILL.md
-- `metadata.version` must be `0` on new skills (do not edit manually)
-- `name` must match `[a-z0-9-]+` and be ≤64 characters
-- `description` frontmatter must be **≤1024 characters** (CI enforces this via `skills-ref validate`)
-- Reference files must be **one level deep** only (e.g. `references/example.yaml`)
-- Use **forward slashes** in all file paths
-- Optional subdirectories: `references/` (additional docs), `scripts/` (utility scripts), `assets/` (static resources)
-
-## Skill Authoring Principles
-
-- **Context window conservation** — only include domain-specific knowledge that agents lack; omit general programming advice
-- **Conciseness** — provide patterns and quick-reference tables, not tutorials
-- **Consistent terminology** — one term per concept throughout a skill
-- **Symptom-based triggering** — the `description` frontmatter should describe observable agent behaviors that signal the skill is needed
-- **No tool names** — reference HA REST APIs and concepts, never specific MCP tool names (e.g. `ha_rename_entity`); tool names vary by agent setup
-
-## Validation
-
-CI runs two workflows on PRs and pushes to `main`:
-- **validate-skills** — runs `skills-ref validate` on every skill when `skills/**` changes
-- **validate-plugin** — validates `.claude-plugin/` metadata
-
-To validate locally:
-
-```bash
-uvx skills-ref validate skills/<skill-name>
-```
-
-## Reviewing Skill PRs
-
-- Judge prose as agent-consumed context, not human docs — the Skill Authoring Principles above are the review bar (e.g. an operator→result lookup table beats narrative bullets, because agents land here holding one case to resolve)
-- Skills make version-pinned claims about HA behavior — verify against source at the release tag: `gh api repos/home-assistant/core/contents/<path>?ref=2026.7.4 --jq .content | base64 -d`
-- Community PRs come from forks: base-repo `?ref=<pr-branch>` 404s; get the fork with `gh pr view <pr> --json headRepository` and fetch files from there

ha_mcp_dev-8.0.0.dev2222/src/ha_mcp/resources/skills-vendor/CLAUDE.md

@@ -1,63 +0,0 @@
-# CLAUDE.md
-
-This file provides guidance to Claude Code (claude.ai/code) when working with code in this repository.
-
-## Project Overview
-
-This is a community-contributed collection of **Agent Skills** for Home Assistant, following the open [Agent Skills standard](https://agentskills.io/specification). Skills teach AI agents domain expertise for configuring and controlling Home Assistant. The repository doubles as a Claude Code plugin (see `.claude-plugin/plugin.json`).
-
-## Repository Structure
-
-- `skills/<skill-name>/SKILL.md` — each skill lives in its own folder with a `SKILL.md` file
-- `CONTRIBUTING.md` — skill authoring guidelines and submission workflow
-- `.claude-plugin/plugin.json` — Claude Code plugin metadata
-- `.claude-plugin/marketplace.json` — marketplace metadata for plugin discovery
-- `AGENTS.md` — symlink to `CLAUDE.md` (for agents that use `AGENTS.md` convention)
-- `.github/ISSUE_TEMPLATE/skill-rca.md` — "Report Bad Skill Advice" issue template
-
-## Skill Format
-
-Every skill is a `SKILL.md` file with YAML frontmatter:
-
-```yaml
----
-name: skill-name-here
-description: >
-  When to activate this skill and what symptoms it addresses.
----
-```
-
-Constraints from CONTRIBUTING.md:
-- Max **500 lines** per SKILL.md
-- `metadata.version` must be `0` on new skills (do not edit manually)
-- `name` must match `[a-z0-9-]+` and be ≤64 characters
-- `description` frontmatter must be **≤1024 characters** (CI enforces this via `skills-ref validate`)
-- Reference files must be **one level deep** only (e.g. `references/example.yaml`)
-- Use **forward slashes** in all file paths
-- Optional subdirectories: `references/` (additional docs), `scripts/` (utility scripts), `assets/` (static resources)
-
-## Skill Authoring Principles
-
-- **Context window conservation** — only include domain-specific knowledge that agents lack; omit general programming advice
-- **Conciseness** — provide patterns and quick-reference tables, not tutorials
-- **Consistent terminology** — one term per concept throughout a skill
-- **Symptom-based triggering** — the `description` frontmatter should describe observable agent behaviors that signal the skill is needed
-- **No tool names** — reference HA REST APIs and concepts, never specific MCP tool names (e.g. `ha_rename_entity`); tool names vary by agent setup
-
-## Validation
-
-CI runs two workflows on PRs and pushes to `main`:
-- **validate-skills** — runs `skills-ref validate` on every skill when `skills/**` changes
-- **validate-plugin** — validates `.claude-plugin/` metadata
-
-To validate locally:
-
-```bash
-uvx skills-ref validate skills/<skill-name>
-```
-
-## Reviewing Skill PRs
-
-- Judge prose as agent-consumed context, not human docs — the Skill Authoring Principles above are the review bar (e.g. an operator→result lookup table beats narrative bullets, because agents land here holding one case to resolve)
-- Skills make version-pinned claims about HA behavior — verify against source at the release tag: `gh api repos/home-assistant/core/contents/<path>?ref=2026.7.4 --jq .content | base64 -d`
-- Community PRs come from forks: base-repo `?ref=<pr-branch>` 404s; get the fork with `gh pr view <pr> --json headRepository` and fetch files from there