629 件 ・ 関連度順
概要と使いどころ
Monitor product availability and get restock alerts for Shopify stores. This skill should be used when checking if a product is in stock, watching for restocks, setting up back-in-stock alerts, or tracking product availability. Supports SMS, Slack, and terminal notifications on status transitions. Keywords: out of stock, sold out, back in stock, restock alert, notify when available, watch product.
日本語の概要は準備中です。原文の説明を表示しています。
Watchlist Manager — build, maintain, and score a dynamic watchlist with Quick Scores (0-100), alert system (breakouts, breakdowns, earnings approaching, volume spikes), and ranked display. Triggered by "trade watchlist", "trade watchlist add/remove/rescore/alerts/top".
日本語の概要は準備中です。原文の説明を表示しています。
Tunes noisy detections by analyzing historical alert data to quantify false-positive sources, recommend allow-list filters and threshold adjustments, and measure precision impact. Activates for requests to tune a detection, reduce false positives, or analyze alert noise and recommend filters.
日本語の概要は準備中です。原文の説明を表示しています。
Comprehensive social media operations for B2B SaaS brand building and engagement. Use this skill to develop LinkedIn strategy, decide whether to run a LinkedIn newsletter and how to scope it, capture consented registrations from LinkedIn Events, check LinkedIn Live eligibility, manage Twitter/X presence, create YouTube content, engage on Reddit communities, decide whether and how to answer on Quora, build community, develop influencer and creator partnerships, vet a creator before paying them, start or fix a B2B podcast, book podcast guests and guest appearances, judge whether a podcast is worth appearing on when you cannot audit its numbers, write show notes and transcripts, run social listening (what are people saying about us, share of voice, brand monitoring, validated sentiment, alert thresholds, routing signals to the right owner), and execute organic social campaigns. Also triggers on: LinkedIn, LinkedIn newsletter, LinkedIn Events, LinkedIn Live, event registration form, subscribe to our newsletter on LinkedIn, marketing consent checkbox, Notify Employees, Twitter/X, YouTube, Reddit, community, influencer, creator partnerships, influencer vetting, engagement rate, fake followers, engagement pods, FTC disclosure, sponsored post disclosure, media kit, social media strategy, organic social, employee advocacy, podcast, podcast strategy, podcast guesting, how do I know if this podcast has real listeners, the host says they get 50k downloads, is this podcast worth going on, podcast RSS feed research, IAB podcast measurement certification, Listen Score, Apple Podcasts reviews, show notes, audiogram, episode transcript, social media account access, who has admin on our LinkedIn page, the person who ran our social accounts left, locked out of our company account, social media offboarding, YouTube channel owner, Slack primary owner, social account MFA, social media approval workflow, pause all scheduled posts, social listening, what are people saying about us, brand monitoring, brand mentions, share of voice, social share of voice vs competitors, sentiment analysis, is our sentiment dashboard accurate, listening query, boolean query, mention alerts, spike alert, CrowdTangle replacement, Reddit API access, which platforms can our listening tool see, someone on Reddit asked for a tool like ours, comment mining, voice of customer from social.
日本語の概要は準備中です。原文の説明を表示しています。
Configures PromQL-based Service Level Objective (SLO) alerting policies for Google Cloud resources registered in App Hub or individually specified. Generates Terraform output. Use when the user asks to configure an SLO or Service Level Objective. Don't use for standard alerting policies.
日本語の概要は準備中です。原文の説明を表示しています。
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.
日本語の概要は準備中です。原文の説明を表示しています。
Analyzes SIEM alert pipelines for rule optimization, alert fatigue reduction, criticality scoring, asset-based prioritization, and correlation rule design using NIST CSF and detection engineering principles..
日本語の概要は準備中です。原文の説明を表示しています。
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.
日本語の概要は準備中です。原文の説明を表示しています。
Use when working with Coralogix — coralogix observability platform for log analytics, metrics, tracing, security, and alerting. Covers log querying with DataPrime, metric exploration, alert management, parsing rules, and data usage insights. Use when searching Coralogix logs, investigating application errors, managing alert rules, or analyzing log ingestion patterns.
日本語の概要は準備中です。原文の説明を表示しています。
Métricas, logs, traces, dashboards, alertas e SLO — Prometheus, Grafana, Loki, Tempo, Mimir, Zabbix, Alertmanager. Use quando o usuário disser "dashboard", "alerta", "métrica", "PromQL", "Grafana", "SLO", "golden signals", "não temos visibilidade", "monitoramento".
日本語の概要は準備中です。原文の説明を表示しています。
Cryptocurrency market data and price alert monitoring tool based on CCXT. Supports multiple exchanges, real-time price tracking, and configurable price/volatility alerts. Use when the user needs to monitor crypto prices or set up trading alerts. Default exchange is Binance.
日本語の概要は準備中です。原文の説明を表示しています。
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.
日本語の概要は準備中です。原文の説明を表示しています。
Defines database performance monitoring strategy with slow query detection, resource usage alerts, query execution thresholds, and automated alerting. Use for "database monitoring", "performance alerts", "slow queries", or "DB metrics".
日本語の概要は準備中です。原文の説明を表示しています。
Complete observability & reliability engineering system. Use when designing monitoring, implementing structured logging, setting up distributed tracing, building alerting systems, creating SLO/SLI frameworks, running incident response, conducting post-mortems, or auditing system reliability. Covers all three pillars (logs/metrics/traces), alert design, dashboard architecture, on-call operations, chaos engineering, and cost optimization.
日本語の概要は準備中です。原文の説明を表示しています。
電子カルテの診療記録、処方、検査結果画面を設計するスキル。薬の相互作用警告や変更履歴、医療現場で入力しやすい画面の設計方針を整理します。
GitHubのIssue分類やPRの確認、CI失敗の調査、変更履歴を含むリリース準備、セキュリティ警告の確認を、gh CLIで進める運用スキル。
A hospital data-governance briefing: patient-data risk, the control framework, accountability, and the approval the board must give. Built as a decision-grade policy briefing deck for health-system board, regulators.
日本語の概要は準備中です。原文の説明を表示しています。
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.
日本語の概要は準備中です。原文の説明を表示しています。
Set up alerting rules, configure on-call rotations, and manage incident response workflows.
日本語の概要は準備中です。原文の説明を表示しています。
Deploy cloud-native deception across AWS, Azure, and GCP using decoy (honey) resources whose only purpose is to generate a high-fidelity alert the instant an attacker touches them: canary IAM access keys, permission-less decoy users/roles/service principals, honey object-storage buckets, and decoy secrets in Secrets Manager / Key Vault / Secret Manager. Wires detection through CloudTrail + EventBridge, Azure Sentinel honeytoken watchlists + Defender, and GCP Cloud Audit Logs, so any use of a decoy is routed to the SOC with near-zero false positives. Use when protecting cloud accounts and data stores, when an org has only on-prem honeypots and needs cloud coverage, when seeding fake AWS keys to catch credential theft and code-leak exposure, or when detecting cloud reconnaissance and lateral movement. Keywords: cloud deception, canary token AWS, honey S3 bucket, decoy IAM credentials, CloudTrail alert, GuardDuty, Sentinel honeytoken, decoy secret, honey service account, cloud honeypot, breach detection.
日本語の概要は準備中です。原文の説明を表示しています。
Installs, configures, and tunes Snort 3 to monitor network traffic for malicious activity using custom and community rulesets, preprocessors, and alert output plugins. Use when deploying network-based intrusion detection at key boundaries, writing custom Snort rules, tuning rulesets to reduce false positives, or integrating Snort alerts with a SIEM.
日本語の概要は準備中です。原文の説明を表示しています。
Monitors Certificate Transparency (CT) logs to detect unauthorized certificate issuance, discover subdomains via CT data, and alert on suspicious certificate activity for owned domains. Uses the crt.sh API and direct CT log querying based on RFC 6962 to build continuous monitoring pipelines that catch rogue certificates, track CA behavior, and map the external attack surface. Activates for requests involving certificate transparency monitoring, CT log auditing, subdomain discovery via certificates, or certificate issuance alerting.
日本語の概要は準備中です。原文の説明を表示しています。
Before fixing a slow/stale/timeout alert, measure the step yourself. Kill the theory with a stopwatch, not a code change. Measure-first ops triage for temporal alerts (stale, timeout, freshness, wedged, N hours behind) from gbrain doctor, autopilot, sync, and cron monitors — runs BEFORE any timeout raise, threshold change, or pipeline rewrite.
日本語の概要は準備中です。原文の説明を表示しています。