Ensures Home Assistant custom integrations are ready for HACS by checking manifest metadata and code quality.
Install
mkdir -p .claude/skills/verify-nishithdev && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/17414" && unzip -o skill.zip -d .claude/skills/verify-nishithdev && rm skill.zipInstalls to .claude/skills/verify-nishithdev
Activation
This is the description your AI agent reads to decide when to run this skill — the better it matches your request, the more reliably it fires.
Validate the timesince integration for HA compatibility and HACS readiness before pushing. Checks deprecated APIs, metadata consistency, and translation files.Key capabilities
- →Scan for deprecated API usage in `__init__.py`
- →Check `hacs.json` and `manifest.json` for metadata consistency
- →Verify translation file completeness and absence of orphaned keys
- →Sanity check `manifest.json` for `iot_class`, `requirements`, and minimum `homeassistant` version
- →Confirm `config_flow.py` `VERSION` consistency with migration logic
How it works
The skill runs through a checklist to validate the `timesince` Home Assistant integration. It checks for deprecated APIs, metadata consistency, translation file integrity, manifest sanity, and config flow versioning.
Inputs & outputs
When to use verify
- →Validate HA integration before publishing
- →Check manifest for deprecations
- →Verify HACS metadata readiness
About this skill
Run through this checklist for the timesince Home Assistant integration and report findings:
1. Deprecated API Check
Scan custom_components/timesince/__init__.py for async_forward_entry_setup (singular). If found, note that it should be replaced with async_forward_entry_setups (plural, takes a list of platforms). Example fix:
# Old (deprecated):
await hass.config_entries.async_forward_entry_setup(entry, "sensor")
# New:
await hass.config_entries.async_forward_entry_setups(entry, ["sensor"])
Do the same for async_unload_platforms if applicable.
2. HACS Metadata Consistency
Read hacs.json and custom_components/timesince/manifest.json. Check:
hacs.json"domains"matches the"domain"field inmanifest.jsonhacs.json"name"is a clean, human-readable name (not a dev placeholder)manifest.json"version"follows semver (e.g.,1.0.0)
3. Translation File Check
Read custom_components/timesince/translations/en.json. Verify:
- All keys referenced in
config_flow.py(viaerrors,stepschemas) are present in the translation file - No orphaned keys in the translation file that are no longer used
4. Manifest Sanity
Read custom_components/timesince/manifest.json. Verify:
"iot_class"is set (e.g.,"local_push"or"calculated")"requirements"is accurate (should be[]since all deps are bundled with HA)"homeassistant"minimum version is set
5. Config Flow Version
Check that config_flow.py VERSION is consistent with any migration logic in __init__.py. If the VERSION was bumped, confirm a async_migrate_entry function exists.
Report
Summarize findings as:
- PASS — no issues found
- WARN — non-blocking issue worth noting
- FAIL — must fix before HACS submission or HA reload
List each check with its status and a one-line explanation.
When not to use it
- →Validating integrations other than `timesince`
Limitations
- →Specific to the `timesince` Home Assistant integration
- →Checks only for `async_forward_entry_setup` and `async_unload_platforms` deprecations
- →Requires `hacs.json`, `manifest.json`, and `en.json` files
How it compares
This skill provides a specific checklist for validating the `timesince` Home Assistant integration for HACS readiness and HA compatibility, offering a targeted verification process beyond general code review.
Compared to similar skills
verify side by side with the closest alternatives in the catalog.
| Skill | Installs | Updated | Safety | Difficulty |
|---|---|---|---|---|
| verify (this skill) | 0 | 1mo | No flags | Intermediate |
| dependency-updater | 1 | 6mo | Review | Beginner |
| code-change-verification | 4 | 4mo | Review | Beginner |
| dependency-auditor | 1 | 9mo | Review | Beginner |
Try saying
Example prompts that trigger this skill in your AI assistant.
You might also like
dependency-updater
davila7
Smart dependency management for any language. Auto-detects project type, applies safe updates automatically, prompts for major versions, diagnoses and fixes dependency issues.
code-change-verification
openai
Run the mandatory verification stack when changes affect runtime code, tests, or build/test behavior in the OpenAI Agents Python repository.
dependency-auditor
alirezarezvani
Check dependencies for known vulnerabilities using npm audit, pip-audit, etc. Use when package.json or requirements.txt changes, or before deployments. Alerts on vulnerable dependencies. Triggers on dependency file changes, deployment prep, security mentions.
dependency-update
dotnet
Guides dependency version updates by checking nuget.org for latest versions, triggering the dotnet-migrate-package Azure DevOps pipeline, and monitoring runs. Use this when asked to update external NuGet dependencies.
pre_commit
pums974
Standardized pre-commit workflow for linting, formatting, and local quality gates.
update-major-deps
makeup
Perform major dependency updates one logical group at a time, assessing breakage risk, then build, test, and create a signed commit per group