Loading...
Loading...
Found 437 Skills
This skill should be used when the user asks to forecast aggregate sentiment and opinion dynamics over time—sentiment indices from text streams; temporal rollups; leading/lagging KPI links; time-series and sequence models (ARIMA, Prophet, state-space, ML); nowcasting; spikes, bots, and bias; walk-forward backtests; intervals and scenarios; volume/velocity/topic features; BI or brand dashboards. Triggers: sentiment forecasting, forecast sentiment, sentiment index, opinion trend forecast, social sentiment time series, brand sentiment trajectory, nowcast sentiment, sentiment leading indicator, aggregate polarity forecast, sentiment backtest, walk-forward sentiment, sentiment spike prediction. Not for per-text labeling (sentiment-analysis-engineer), demand forecasting without sentiment (predictive-logistics-developer, data-scientist), trade advice (methodology only), marketing copy (content-creator), macro without text sentiment (financial-analyst partial).
Queries Huawei Cloud monitoring and enterprise project resources (CES/EPS). Covers alarm rules, alarm histories, alarm templates, dashboards, notification masks, resource groups, one-click alarms, and enterprise projects (list/detail/quotas/bound resources/migration records). No write operations. Use this skill when the user needs to check alarm status, view monitoring dashboards, query alarm rules, or manage enterprise project info. Triggers: 云监控, 告警, 告警规则, 告警历史, 仪表盘, 企业项目, CES, EPS, 告警模板, 资源分组, alarm, monitoring, alert.
Use this skill when users need to create, generate, or validate Salesforce Custom Report Type metadata. Trigger when users mention custom report types, report types, CRTs, reporting frameworks, cross-object reports, report builder data sources, or ask to expose fields for reporting across related objects. Also use when users mention primary and related objects for reports, inner vs outer joins in reports, report type categories, or encounter deployment errors for .reportType-meta.xml files. Do NOT trigger for: running, editing, or filtering existing reports; creating report folders, dashboards, or list views; or general reporting questions that don't involve authoring a .reportType-meta.xml file.
Home Assistant Lovelace dashboards and cards. Use when the user asks about dashboard structure, views/sections, card types, resources, or HACS cards, and when mapping those needs to ha-mcp dashboard tools.
Creates and configures Home Assistant graph visualizations using history-graph, statistics-graph, mini-graph-card, and apexcharts-card with time ranges, aggregations, and multi-sensor support. Use when displaying sensor data over time, creating trend charts, comparing historical data, or building energy/climate/air quality dashboards.
OpenTelemetry, structured logging, distributed tracing, alerting, and dashboards
Create advanced Excel pivot tables with calculated fields and slicers. Use when building data summaries or creating interactive dashboards. Trigger with phrases like 'excel pivot', 'create pivot table', 'data summary'.
MDV — Markdown superset for documents, dashboards, and slides with embedded charts, KPI stats, and data visualizations exported to HTML or PDF.
Use this skill when users ask about data visualisation, charts, graphs, or dashboards in an SGDS application. Covers ECharts setup and applying the SGDS colour palette to charts.
Specifies requirements for an analytics dashboard including metrics, visualizations, filters, and data sources. Use when requesting dashboards from data teams, defining KPI tracking, or documenting reporting needs.
Audit the health of a PostHog project's data warehouse — find every broken or degraded pipeline item across sources, sync schemas, materialized views, batch exports, and transformations. Use when the user asks "what's broken in my warehouse?", "give me a health check", "audit my data pipeline", "why are some dashboards stale?", or wants a one-shot triage summary before deciding where to spend time. Produces a prioritized report of issues grouped by severity and type, with recommended next steps.
Laws of UX critique skill. Use when evaluating mockups, screenshots, design specs, prototypes, flows, onboarding, checkout, dashboards, forms, or design-review requests, even when the user does not say UX or name a law. Output the 2-4 most relevant laws with specific application and law-grounded recommendations. Do not use for pure frontend implementation code review, WCAG/accessibility audits, or brand/visual-identity critique unless interaction usability is also in scope.