「alerts」の検索結果

Implements OpenTelemetry logs/metrics/traces, SLI/SLO gates, burn-rate alerts, and APM integrations. Use when adding or validating observability.

日本語の概要は準備中です。原文の説明を表示しています。

Orchestrate incident response — triage, root cause, remediate, prevent recurrence. USE WHEN active alerts, data broken, stale, pipeline failure, or investigate and fix a data incident.

日本語の概要は準備中です。原文の説明を表示しています。

Troubleshoots Monte Carlo AI agent alerts and traces — eval score drops, latency/token spikes, trajectory and validation breaches. Not for data incidents (monte-carlo-analyze-root-cause) or monitor creation (monte-carlo-monitoring-advisor).

日本語の概要は準備中です。原文の説明を表示しています。

Investigate data incidents and find root causes using Monte Carlo's observability data. Guides the agent through systematic investigation: alert lookup, lineage tracing, ETL checks, query analysis, and data profiling. Activates when a user asks about data issues, incidents, alerts, or why data looks wrong.

日本語の概要は準備中です。原文の説明を表示しています。

Investigate and remediate data quality alerts using Monte Carlo MCP tools. Runs root cause analysis, assesses blast radius, discovers available tools (MCP/CLI/API), proposes and executes fixes, or escalates with full context when uncertain.

日本語の概要は準備中です。原文の説明を表示しています。

Route data-related requests to the right Monte Carlo skill or workflow. USE WHEN alerts, incidents, data broken, stale, coverage gaps, data quality, or any ambiguous data observability request.

日本語の概要は準備中です。原文の説明を表示しています。

Remediating known failure patterns automatically from Triage diagnoses and Beacon alerts: runbooks with safety-tier classification, staged verification, rollback. Use for automated remediation.

日本語の概要は準備中です。原文の説明を表示しています。

Optimizing FinOps and cloud cost: IaC-based estimation, right-sizing, RI/SP recommendations, anomaly detection, budget alerts, AI/GPU workload economics. Use to forecast or cut cloud spend.

日本語の概要は準備中です。原文の説明を表示しています。

Query Amazon product historical time-series data, including price trends, BSR (Best Sellers Rank) trends, rating changes, seller counts, and monthly sales, supporting any ASIN across multiple Amazon marketplaces. Triggered when users mention price history, price tracking, BSR history, BSR trends, historical pricing, price fluctuations, Nexscope data, rank history, price drop alerts, lightning deal historical prices, Buy Box price trends, coupon prices, FBA/FBM price comparison, seller count changes, rating trends, sales history. Even if users do not explicitly mention "Nexscope" or "time-series data", this skill should be triggered whenever the task involves analyzing Amazon product-level historical data (such as price, rank, or sales trends over time).

日本語の概要は準備中です。原文の説明を表示しています。

Query Amazon is latest policy, regulation, and compliance feed. Supports paginated browsing by marketplace and time range (with AI-generated Chinese summaries), and fetching full article body by record ID. Trigger when users mention Amazon policies & regulations, seller compliance announcements, platform rule changes, policy alerts, FBA/fee policy updates, multi-marketplace policy tracking, policy original text, news details, or similar terms. Even if the user does not explicitly mention "policy feed," trigger this skill whenever the request involves Amazon is officially published policies, regulations, and news for sellers, including their full text.

日本語の概要は準備中です。原文の説明を表示しています。

Manage Apple Reminders on macOS via remindctl — list, add, edit, complete, delete to-dos that sync to iPhone/iPad. Trigger on "reminder", "Reminders app", "提醒我" with phone sync, or adding personal todos with due dates. macOS only. Skip when the user wants agent-internal alerts (use memory_store or external scheduling) or calendar events.

日本語の概要は準備中です。原文の説明を表示しています。

Debug validator checkpoint inconsistencies where some validators are behind others. Use when alerts mention "checkpoint inconsistency", "validators behind", or "inconsistent latest checkpoints", or when asked to debug validator sets, investigate validator delays, or troubleshoot metadata fetch failures for a chain. Defaults to default_ism app context if not specified.

日本語の概要は準備中です。原文の説明を表示しています。

Investigate stuck messages in relayer queue. Use when alerts mention "queue length greater than 0", to diagnose why messages are stuck, or to get message IDs for denylisting.

日本語の概要は準備中です。原文の説明を表示しています。

Debug RPC provider health issues for a chain. Use when alerts mention RPC failures, high latency, stale blocks, or provider errors. Diagnoses the issue and recommends fixes.

日本語の概要は準備中です。原文の説明を表示しています。

RxMemberSim generates realistic synthetic pharmacy data for testing PBM systems, claims adjudication, and drug utilization review. Use when user requests: (1) pharmacy claims or prescription data, (2) DUR alerts or drug interactions, (3) formulary or tier cohorts, (4) pharmacy prior authorization, (5) NCPDP formatted output.

日本語の概要は準備中です。原文の説明を表示しています。

Audit existing ML monitoring — find gaps in drift coverage and missing alerts. Use when asked to "audit our ML monitoring", "are our models monitored", or "find drift coverage gaps".

日本語の概要は準備中です。原文の説明を表示しています。

Design drift alerts and escalation — thresholds, runbooks, and retrain triggers. Use when asked to "alert on model drift", "when should we retrain", or "write a drift escalation runbook".

日本語の概要は準備中です。原文の説明を表示しています。

Few semantic colours, each meaning one thing, and errors with a way forward. Use when designing status indicators, validation, alerts or error states.

日本語の概要は準備中です。原文の説明を表示しています。

OpenStack monitoring operations skill for deploying, configuring, and operating the cloud health monitoring stack. Covers Prometheus metric collection and scrape targets, Grafana dashboard provisioning and visualization, Alertmanager notification channels and routing, alerting rules for service health and resource exhaustion, service endpoint health checks, log aggregation strategies, SLA tracking with availability and response time percentiles, and capacity trend analysis from historical metrics. Use when deploying monitoring via Kolla-Ansible, configuring alert thresholds, troubleshooting blank dashboards, tuning noisy alerts, or analyzing cloud performance trends.

日本語の概要は準備中です。原文の説明を表示しています。

See, Understand, Act on video and audio. See- ingest from local files, URLs, RTSP/live feeds, or live record desktop; return realtime context and playable stream links. Understand- extract frames, build visual/semantic/temporal indexes, and search moments with timestamps and auto-clips. Act- transcode and normalize (codec, fps, resolution, aspect ratio), perform timeline edits (subtitles, text/image overlays, branding, audio overlays, dubbing, translation), generate media assets (image, audio, video), and create real time alerts for events from live streams or desktop capture.

日本語の概要は準備中です。原文の説明を表示しています。

Watchlist group management (list/create/rename/delete/add/remove symbols), price alerts (list/add/delete), and community stock lists (sharelist: list/detail/create/delete/manage) via Longbridge. Mutating operations require explicit user confirmation (dry-run protocol). Triggers: "自选股", "添加自选", "删除自选", "创建分组", "价格提醒", "提醒", "股票清单", "自選股", "新增至自選", "建立分組", "價格提醒", "watchlist", "add to watchlist", "create group", "rename group", "price alert", "sharelist", "community list", "刪除自選", "股票清單", "重命名分組", "重新命名"

日本語の概要は準備中です。原文の説明を表示しています。

Set up Claude Tag for oncall for a team, from that team's standing (public) oncall / monitoring channel. Two things: it sets the channel up for monitoring, so alerts and incident posts here (from a person or another Slack bot) get triaged and acted on automatically, and it finds and sets up the connectors, plugins and skills Claude uses for oncall. A workspace can have several such channels; run once in each, by anyone, and every run adds or updates that team's section in the one oncall memory in shared workspace memory. Use on "set up oncall", "init oncall", "configure Claude for on-call". Surveys the agent connectors an admin configured for Claude, proves one with a read-only pull so access is verified, explores tools, Slack, repos and docs to learn how oncall works here, then recommends what's missing and walks the team through setup. The result goes into the indexed oncall memory every channel reuses; the other skills (incident init, investigation, handoff) pick it up automatically.

日本語の概要は準備中です。原文の説明を表示しています。

Triages AWS CloudWatch alarms using the CloudWatch DescribeAlarms API, GetMetricData for historical analysis, and CloudTrail LookupEvents for root cause correlation. Prioritizes alerts by blast radius and provides remediation playbooks.

日本語の概要は準備中です。原文の説明を表示しています。

Triages AWS CloudWatch alarms by correlating alarm state changes with CloudTrail events and EC2 instance health using boto3. Classifies alarms by severity, identifies root cause candidates, and updates OpsGenie alerts.

日本語の概要は準備中です。原文の説明を表示しています。