Loading...
Loading...
Found 571 Skills
Implements conditional visibility for Home Assistant dashboard cards using state, numeric_state, screen, user, time, and/or conditions via Conditional Card wrapper and per-card visibility property. Use when asked to "hide card when", "show only if", "user-specific dashboard", "mobile vs desktop cards", "conditional visibility", or "show card based on state/time/user".
Debugs and validates Home Assistant dashboards by checking system logs, verifying entity IDs, validating HACS card installations, and analyzing configuration errors via WebSocket API. Use when troubleshooting dashboard errors, validating entity IDs, checking HACS card installations, investigating lovelace/frontend issues, or debugging "ApexCharts span error", "entity not found", "custom card not loading", or "dashboard not appearing in sidebar".
Provides 3-tier validation approach for Home Assistant dashboards including pre-publish validation (entity checks, config structure), post-publish verification (log analysis), and visual validation (browser console, rendering). Use when validating HA dashboards, checking dashboard configs, verifying entity IDs, debugging rendering issues, or before deploying dashboard changes. Triggers on "validate dashboard", "check HA config", "dashboard errors", "entity not found", or "test dashboard". Works with Home Assistant WebSocket/REST APIs, Chrome extension MCP tools, Python dashboard builders, and YAML dashboard configurations.
Create FilamentPHP v4 dashboard widgets - stats overviews, charts, and custom components
Build custom backends and widgets for OpenBB Workspace. Use when user wants to create an OpenBB app, convert Streamlit/Gradio apps, or build dashboards. Handles the full pipeline from requirements to deployment.
Marketing analytics specialist covering tracking setup, dashboards, reporting, attribution modeling, A/B testing and experiment design, conversion optimization, and data-driven decision making. Use when the user wants to set up analytics tracking, create dashboards, build reports, implement conversion tracking, design or set up A/B tests, calculate sample sizes, write test hypotheses, analyze campaign performance, set up attribution models, audit existing analytics, or make data-driven marketing decisions. Also triggers for GA4, Google Tag Manager, UTM parameters, conversion rates, marketing ROI, funnel analysis, cohort analysis, sample size calculation, ICE scoring, experiment roadmap, or any marketing measurement question.
Implement AI chatbot analytics and conversation monitoring. Use when adding conversation metrics, tracking AI usage, measuring user engagement with chat, or building conversation dashboards. Activates for AI analytics, token tracking, conversation categorization, and chat performance.
Design KPI dashboards for executive monitoring. Use for performance tracking, strategic initiatives, and management reporting.
Use when writing SQL queries, building analytics dashboards, tracking metrics, designing data pipelines, or analyzing user behavior and product usage
Grafana-to-Perses dashboard migration: export Grafana dashboards, convert with percli migrate, validate converted output, fix incompatibilities, deploy to Perses. Handles bulk migration with parallel processing. Use for "migrate grafana", "grafana to perses", "perses migrate", "convert grafana". Do NOT use for creating new dashboards from scratch (use perses-dashboard-create).
Validate Perses resources: run percli lint locally or with --online against a server. Check dashboard definitions, datasource configs, variable schemas. Report errors with actionable fixes. Use for "perses lint", "validate perses", "check dashboard", "perses validate". Do NOT use for plugin schema testing (use perses-plugin-test).
Perses-aware code review: check Go backend against Perses patterns, React components against Perses UI conventions, CUE schemas against plugin spec, and dashboard definitions against best practices. Dispatches appropriate sub-reviewers. Use for "review perses", "perses pr", "perses code review". Do NOT use for general Go/React review without Perses context.