「alerts」の検索結果

Conviction-trigger surveillance via Quartr keyword alerts — parse every active thesis's Conviction Triggers for named observables, propose keyword alerts scoped to the Vault Active watchlist (or market-wide for macro observables), create them ONLY on explicit user confirmation, and reconcile the alert set against the book as theses open/close. Use when user says "monitor", "set up alerts", "keyword alerts", "watch for X", or "reconcile alerts".

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

OpenClawのGitHub Secret Scanningアラートを調べ、IssueやPRなどに残る秘密情報の伏せ字化、コメントの削除・再作成、通知とアラート処理を進めるスキル。

• 認証情報の漏えい箇所を調べたいとき
• IssueやPR本文の秘密情報の伏せ字化
• 秘密情報を含むコメントの削除・再作成

動画・音声をVideoDBに取り込み、発話や映像から場面を検索して切り抜きを作成。字幕や音声の追加、画面比率の変換、ライブ映像の通知設定も支援します。

• 発話や映像から場面を探して切り抜きたいとき
• 字幕・BGM・吹き替えの追加
• 動画の解像度や画面比率の変更

GitHubやLinear、ローカルの通知を棚卸しし、重要度と担当者に応じた届け先を設計します。重複や不要な通知を整理し、次の対応が分かる運用にまとめるスキル。

• 複数ツールの通知をまとめたいとき
• CI失敗の重複通知を減らしたいとき
• 緊急通知とまとめ通知の振り分け

Review the configured cost alert rules and the alerts currently fired on the Agent Monitor dashboard, then explain exactly what tripped and why. Uses /api/alerts (fired feed) and /api/alerts/rules (definitions). Use when checking spend alerts or asking why a cost alarm went off.

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

Author useful, low-noise log alerts on services in a PostHog project. Use when the user asks to set up alerts for their logs, suggest alerts they should add, or evaluate whether a service is worth monitoring. Covers service triage, baseline characterisation, threshold drafting, back-testing via simulate, and shipping with a notification destination.

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

Configures best-practice alerting policies for AI agents using OpenTelemetry (OTel) metrics, generating output as Terraform (.tf) configuration files. Use when analyzing, writing, or deploying alerting policies to monitor agent latency, error rates, token usage, and quality metrics. Don't use for standard infrastructure monitoring unrelated to AI agents, or when the agent is not instrumented with OpenTelemetry (for Reliability, Cost, Safety, Security alerts). NOTE: Reliability, Cost, Safety, and Security alerts use generic OTel metrics and work across runtimes (such as Cloud Run, Vertex AI). Quality alerts rely on Vertex AI Online Monitors and are strictly bound to Vertex AI deployments.

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

Read the user's local TradingView desktop app through opencli: quotes, options chains with greeks and per-strike IV, options expiries, screener results across stocks, crypto, forex, futures, and bonds, gainers and losers, news headlines and full stories, alerts (active, fired, offline fires), watchlists including colored flag lists, symbol search, chart state, and chart screenshots. Use this skill whenever the user asks for any of these from TradingView ("TV") — for example an options chain, puts, or IV skew for a ticker, an oversold-stock screen, their red flag list, which alerts fired, or a screenshot of their chart. For plain quotes, TA readouts, scans, or futures without the desktop app, prefer tradingview-mcp. Read-only: it never places trades or edits watchlists, alerts, or layouts.

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

Configure competitor alerts: change thresholds per competitor, urgency routing, digests. "set up competitor alerts"

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

Investigate an alert, page, or production symptom in an incident channel or a team's oncall / monitoring channel, and report findings a human can verify. Ordinary conversation and chatter are not alerts; leave those alone. Use when an alert or page lands, when error rate, latency or saturation is up, when someone asks "why is X broken", "investigate", "what changed", "root cause this", pastes a monitor, dashboard, trace or error-tracker link, or reports production trouble; also by default when an alert lands in a covered channel unasked. Feed-level asks land here too ("which alerts matter", "triage today's alerts"), plus the scheduled alert-review routine and the ticket path ("customer X can't check out"). Runs a fast first pass posted as a short interim update with a TL;DR, every finding carrying the query or link to verify it, then proposes the fix and — with connector access and confirmation — carries it out, never unattended. Afterwards `incident-postmortem` writes it up.

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

Medicinal chemistry filters for compound triage. Apply drug-likeness rules (Lipinski rule of five, Veber, Oprea, CNS, lead-like, rule of three), structural alert catalogs (PAINS a/b/c, NIBR screening-deck severity, Brenk, BMS, Glaxo, Dundee, ChEMBL common alerts), ZINC-15 percentile complexity metrics (Bertz, SAscore, QED, Whitlock, Barone), chemical-group detection, Lilly demerits, and the medchem query language (MATCHRULE, HASALERT, HASPROP, HASGROUP) for filtering a library at scale. Also trigger on medchem, `import medchem as mc`, RuleFilters, NIBRFilters, CommonAlertsFilters, NamedCatalogs, QueryFilter, PAINS filtering, or structural alerts.

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

Configures best-practice alerting policies for AI agents using OpenTelemetry (OTel) metrics, generating output as Terraform (.tf) configuration files. Use when analyzing, writing, or deploying alerting policies to monitor agent latency, error rates, token usage, and quality metrics. Don't use for standard infrastructure monitoring unrelated to AI agents, or when the agent is not instrumented with OpenTelemetry (for Reliability, Cost, Safety, Security alerts). NOTE: Reliability, Cost, Safety, and Security alerts use generic OTel metrics and work across runtimes (such as Cloud Run, Vertex AI). Quality alerts rely on Vertex AI Online Monitors and are strictly bound to Vertex AI deployments.

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

Use when designing, reviewing, or troubleshooting Salesforce email templates, email alerts, and declarative notification design. Triggers: 'Lightning Email Template', 'email alert', 'merge field', 'org-wide email', 'too many emails', 'mass email limit'. NOT for migrating Classic templates to Lightning — use admin/classic-email-template-migration. NOT for sending email from Apex — use apex/apex-outbound-email-patterns.

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

Custom Notification Types for desktop/mobile push alerts from Flow or Apex: type creation, target channels, Messaging.CustomNotification invocation, recipient limits, bulk notification patterns. NOT for choosing channels, consent, or notification-fatigue policy — use admin/custom-notification-type-design. NOT for email alerts — use admin/email-templates-and-alerts. Trigger keywords: notiftype, notificationtypes directory, customNotifTypeName, customNotificationAction, setNotificationTypeId, targetPageRef, NotificationTypeConfig.

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

Proactive monitoring of Aave V3 borrow positions with liquidation alerts. Queries user collateral, debt, and health factor across chains (Ethereum, Polygon, Arbitrum, etc.). Sends urgent alerts to Telegram/Discord/Slack when health factor drops below configurable thresholds (critical at 1.05, warning at 1.2). Use when you need continuous monitoring of Aave positions, want alerts before liquidation risk occurs, or need periodic summaries of your borrowing health.

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

Operational guide for the NV oOS Dependabot alert triage-and-remediation loop: querying open alerts via gh api, separating stale from genuinely vulnerable lockfile entries (default-branch forensics), deciding between safe in-major override bumps, scoped overrides, or deferred major migrations (npm pack signature diffing), regenerating the 13-lockfile tree, dismissing alerts with the right reason, GitHub issue housekeeping, and triaging the known CI failure modes. Use when asked to fix dependabot alerts, close out dependabot issues, bump vulnerable npm packages, or resume a dependabot session.

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

Proactive monitoring of Aave V3 borrow positions with liquidation alerts. Queries user collateral, debt, and health factor across chains (Ethereum, Polygon, Arbitrum, etc.). Sends urgent alerts to Telegram/Discord/Slack when health factor drops below configurable thresholds (critical at 1.05, warning at 1.2). Use when you need continuous monitoring of Aave positions, want alerts before liquidation risk occurs, or need periodic summaries of your borrowing health.

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

GitHubのIssue分類やPRの確認、CI失敗の調査、変更履歴を含むリリース準備、セキュリティ警告の確認を、gh CLIで進める運用スキル。

• Issueの分類と重複確認
• PRのレビュー状況とマージ可否確認
• CIワークフローの失敗調査

電子カルテに組み込む臨床判断支援を設計し、薬の相互作用や用量の検証、臨床スコアの計算、警告の重要度に応じた画面制御とテストを実装するスキル。

• 薬の相互作用とアレルギー確認の実装
• 患者情報に応じた用量検証
• NEWS2などの臨床スコアの実装

電子カルテの診療記録、処方、検査結果画面を設計するスキル。薬の相互作用警告や変更履歴、医療現場で入力しやすい画面の設計方針を整理します。

• 診療フローを設計したいとき
• 薬の相互作用警告を実装したいとき
• 検査結果の異常値を表示したいとき

Retrieve disease outbreak alerts and PM2.5 air-quality health warnings. Use when the user asks about current public-health risks in a country, city, or region.

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

Triage Monte Carlo alerts interactively or build an automated workflow. Fetch, score, and troubleshoot alerts using MCP tools now, or design a reusable workflow that runs on a schedule.

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

Expert guidance for security alert triage in Google SecOps. Use when investigating and triaging security alerts, determining false positives vs. true positives, assessing entity risk, adjusting alert severity or priority, and closing or escalating alerts and cases. Don't use for deep multi-hop incident investigations across host timelines (use secops-investigate), proactive threat hunting or retroactive IoC sweeps (use secops-hunt), or authoring new detection rules (use secops-detection-engineering).

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

Track and visualize ML training experiments with Trackio. Use when logging metrics during training (Python API), firing alerts for training diagnostics, or retrieving/analyzing logged metrics (CLI). Supports real-time dashboard visualization, alerts with webhooks, HF Space syncing, and JSON output for automation.

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