l3digital-net
52 verified skills214 total stars
up-notion
Update Notion pages with strategic and organizational context from the current session by dispatching the up-docs-propagate-notion sub-agent. This skill should be used when the user runs /up-docs:notion.
documentation5
qdev-grounding
Use when you're stuck or missing current information mid-task - the same command/API/approach failed twice, an error looks like a changed or deprecated API, or you need the current version of something, a fact from after your training cutoff, or to verify something you cannot confirm from the code in context. Starts with a cheap inline lookup and only escalates to a full research sweep if that fails. Do not use for routine pre-emptive checks before ordinary library work - for deliberate research, use /qdev:research.
development5
up-wiki
Update Outline wiki documentation with implementation-level details from the current session by dispatching the up-docs-propagate-wiki sub-agent. This skill should be used when the user runs /up-docs:wiki.
documentation5
up-all
Update all three documentation layers (repo, wiki, Notion) via parallel sub-agent propagation, then run drift audit. This skill should be used when the user runs /up-docs:all.
testing5
up-repo
Update repository documentation (README.md, docs/, CLAUDE.md) based on session changes by dispatching the up-docs-propagate-repo sub-agent. This skill should be used when the user runs /up-docs:repo.
documentation5
up-drift
Comprehensive documentation drift analysis across infrastructure and wiki by dispatching the up-docs-audit-drift sub-agent. This skill should be used when the user runs /up-docs:drift.
testing5
ha-config-migration
Config entry version migration in Home Assistant. Use when incrementing VERSION or MINOR_VERSION, implementing async_migrate_entry, or migrating stored entry data between schema versions.
data-ai4
ha-debugging
Debug and troubleshoot Home Assistant integration issues. Use when mentioning error, debug, not working, unavailable, traceback, exception, logs, failing, ConfigEntryNotReady, UpdateFailed, or needing help diagnosing HA integration problems.
development4
ha-device-conditions-actions
Device conditions and actions for Home Assistant automation. Use when implementing device_condition.py, device_action.py, condition state checks, or device-level automation actions.
tools4
ha-device-triggers
Device triggers for Home Assistant automation. Use when implementing device_trigger.py, allowing automations to fire on hardware events like button presses or motion detection.
tools4
ha-diagnostics
Implement diagnostics for a Home Assistant integration. Required for Gold tier on the Integration Quality Scale. Use when asked about diagnostics.py, debug information, troubleshooting data, or redacting sensitive info.
development4
ha-documentation
Generate documentation for Home Assistant integrations. Creates README.md, Home Assistant docs pages, and HACS info pages. Use when asked about documentation, README, docs, or making documentation for an integration.
documentation4
ha-entity-lifecycle
Entity lifecycle and device/entity registries in Home Assistant. Use when asking about entity registration, async_added_to_hass, async_will_remove_from_hass, device_info, identifiers, or restoring previous state.
development4
ha-hacs-publishing
Publish a Home Assistant integration to HACS — GitHub Actions validation, release workflow, brand submission, and adding to the HACS default repository.
tools4
ha-integration-scaffold
Scaffold a new Home Assistant integration with correct file structure, manifest, and boilerplate. Use when creating a new custom component, custom integration, or when asked to scaffold, create, or start a Home Assistant integration.
tools4
ha-options-flow
Home Assistant options flow for post-setup user preferences. Use when adding or fixing an options flow, allowing users to change integration settings after initial setup, or implementing reauth when credentials expire.
tools4
ha-repairs
Implement repair issues for Home Assistant integrations. Gold tier IQS requirement. Use when asked about repair issues, issue registry, user notifications, fixable issues, or actionable alerts.
development4
ha-quality-review
Review a Home Assistant integration against the Integration Quality Scale (IQS). Covers all 52 official rules across Bronze, Silver, Gold, and Platinum tiers. Use when asked to review, quality check, assess for core PR, HACS submission, or IQS compliance.
development4
ha-scripts
Home Assistant YAML scripts — callable, reusable action sequences with optional parameters. Use when creating a script, defining a reusable sequence, or adding parameterized fields to a script.
data-ai4
ha-service-actions
Generate and explain Home Assistant service actions for controlling entities (lights, switches, climate, media, covers) in Python and YAML. Use when asking about calling services, controlling devices, hass.services.async_call, entity actions, turn_on, turn_off, or invoking HA actions.
tools4
ha-websocket-api
Implement WebSocket API commands for Home Assistant integrations. Use when asked about WebSocket API, custom API endpoints, frontend integration, custom panels, or real-time data to frontend.
development4
ha-yaml-automations
Home Assistant YAML automations — triggers, conditions, and actions. Use when writing or fixing an automation, choosing a trigger type, or structuring automation logic.
tools4
project-entry
Triggers freshness scan when entering a new project directory. Use when the working directory changes, the user mentions "working on X project", "switch to X", "open X", or when a new project path first appears in the conversation.
tools4
python-anti-patterns
Python anti-pattern checklist. MUST consult before finalizing any Python implementation, during Python code review, or when a Python bug traces to mutable defaults, bare except, circular imports, or other known traps.
development4
python-background-jobs
Python background job patterns — Celery, RQ, dramatiq, task queues, workers. MUST consult when adding background tasks, job queues, long-running operations, worker processes, or decoupling work from request/response cycles in Python.
development4
python-design-patterns
Python design patterns — KISS, SoC, SRP, composition over inheritance, dependency injection. MUST consult when refactoring Python classes, choosing between inheritance and composition, implementing dependency injection, extracting abstractions, or restructuring Python modules.
development4
python-resilience
Python resilience — tenacity, retries, exponential backoff, circuit breakers, timeouts. MUST consult when adding retry logic, implementing timeouts, wrapping external API calls with fault tolerance, or handling transient failures in Python.
development4
python-resource-management
Python resource management — context managers, __enter__/__exit__, contextlib, cleanup patterns. MUST consult when writing context managers, managing connections/file handles, implementing cleanup logic, or building streaming responses in Python.
development4
python-testing-patterns
Python test patterns — pytest fixtures, parametrize, mocking, conftest, coverage. MUST consult as a reference when writing pytest fixtures, parametrized tests, mock strategies, or structuring Python test suites. Complements superpowers:test-driven-development (which drives the workflow).
development4
save
Save a task handoff file to the shared network drive. This skill should be used when the user runs /handoff:save.
tools4
session-boundary
Reminds about queued documentation items at session boundaries. Use when the user says "wrap up", "I'm done", "let's commit", "end of session", "push and close", or otherwise signals they are finishing work for the day.
documentation4
sysadmin
Linux system administration knowledge base: 163 per-service guides covering daemons, CLI tools, filesystems, containers, networking, security, databases, monitoring, backup, and self-hosted applications. MUST consult when installing, configuring, troubleshooting, or administering any Linux service or tool.
tools4
python-code-style
Python code style — ruff, black, isort, naming conventions, docstrings. MUST consult when configuring Python linters/formatters, establishing project style standards, or when style questions arise during Python code review.
development4
python-configuration
Python configuration management — pydantic-settings, environment variables, .env files, secrets. MUST consult when externalizing config, adding settings classes, managing secrets, or implementing environment-specific behavior in Python.
development4
testing-mindset
Always-on testing awareness driver. MUST consult during any implementation task to evaluate whether testing is needed at this point. Applies to every task involving code changes. Governs: when to suggest gap analysis, how to assess test coverage needs, delegation to framework-specific testing plugins, and non-intrusive suggestion cadence. Triggers on: test, implement, feature, fix, bug, refactor, build, create, modify, change, add, update, debug, complete, finish, deploy, merge, PR, commit.
tools4
ha-testing
Write tests for Home Assistant integrations using pytest and the hass fixture. Use when mentioning test, pytest, testing, test coverage, mock, fixture, or preparing an integration for core submission.
testing4
ha-coordinator
Implement or fix a Home Assistant DataUpdateCoordinator for centralized data fetching. Use when mentioning coordinator, DataUpdateCoordinator, polling, data fetching, _async_update_data, _async_setup, UpdateFailed, or setting up efficient data polling for a Home Assistant integration.
testing4
ha-architecture
Home Assistant core internals — event bus, state machine, service registry, and integration loading. Use when asking about the hass object, event propagation, state management, service registration, or how integrations load.
tools4
ha-deprecation-fixes
Fix Home Assistant deprecation warnings and upgrade integrations to newer HA versions. Use when encountering deprecated imports, type annotations, or patterns that need updating for HA 2024.x/2025.x compatibility.
tools4
ha-hacs
HACS metadata requirements for a Home Assistant integration — hacs.json, manifest.json fields, and repository structure. Use when preparing or validating HACS metadata files.
data-ai4
ha-migration
Home Assistant integration upgrade guide — config entry version migration and deprecation fixes. Use when upgrading an integration to a newer HA version or handling migration warnings.
documentation4
deep-context
1M context window rules. Injected into AI context at every SessionStart. Invoke manually to reload mid-session if the rules drop out of working attention.
data-ai4
ha-recorder
Work with the Home Assistant recorder and statistics. Use when asked about history, statistics, long-term stats, database, recorder exclusion, or historical data.
data-ai4
python-observability
Python observability — structlog, logging, OpenTelemetry, Prometheus, tracing. MUST consult when adding logging to Python code, implementing metrics/counters, setting up distributed tracing, or instrumenting Python services.
development4
python-type-safety
Python type safety — type hints, generics, Protocol, TypeVar, mypy, pyright. MUST consult when adding type annotations, implementing generic classes, defining structural interfaces (Protocol), or configuring mypy/pyright in Python projects.
development4
load
Load the most recent task handoff file from the shared network drive. This skill should be used when the user runs /handoff:load.
tools4
async-python-patterns
Python asyncio and async/await patterns — asyncio.gather, semaphores, async context managers, event loop, coroutines, tasks. MUST consult when writing async Python code, building concurrent systems, using async frameworks (FastAPI, aiohttp, asyncpg), or managing I/O-bound operations with non-blocking patterns.
development4
doc-creation
Suggests using /docs new when creating markdown files in managed locations. Use before any Write or Edit tool call that would create a new .md file — especially when the target path is under a known docs/ or documentation/ directory.
tools4
ha-config-flow
Home Assistant config flow for initial integration setup. Use when creating or debugging config_flow.py, the user-facing setup wizard, unique_id handling, or strings.json for the setup steps.
development4
ha-entity-platforms
Create Home Assistant entity platforms (sensor, binary_sensor, switch, light, cover, climate, button, number, select, etc.). Use when creating entities, adding platforms, implementing switches or sensors, or working with any HA entity type.
tools4
ha-async-patterns
Write correct async Python code for Home Assistant integrations. Use when mentioning async, await, event loop, blocking, executor, async_add_executor_job, coroutine, or asking about performance and non-blocking code in Home Assistant.
development4
ha-blueprints
Home Assistant YAML blueprints — reusable automation templates with configurable inputs. Use when building a blueprint, defining blueprint inputs, or creating a shareable automation template.
tools4