723건 · 관련도순
Define service reliability targets, choose measurements that reflect user experience, and calculate error budgets—the failures a target allows. Generate alert thresholds and review existing definitions for unrealistic targets, unclear metrics, and missing response policies.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Manages security incident cases in Google SecOps, from reviewing queues and related alerts to updating priorities, assignments, and investigation notes. It supports closing cases with documented causes, with available actions depending on the connected MCP tools.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Record and query iii engine logs, traces that show how calls flow, and operational metrics. Set up reactions to incoming errors, inspect alerts, and review metrics aggregated over time windows.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Set up application monitoring with structured logs, performance metrics, and traces that follow requests across services. Build dashboards and alerts, run load tests, investigate CPU and memory bottlenecks, and estimate future infrastructure capacity.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Set up Slack alerts for a colony, a group of AI agents, so users can reply when work stalls. The skill prepares the Slack app, stores sending and receiving tokens, connects a channel, and tests notifications.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Set up Telegram alerts for a colony, a group of AI agents, so users can respond when work stalls. The skill creates or reuses a bot, stores its token, connects the destination chat, and tests notifications.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Build a single-page operations guide for engineers on call, the people assigned to respond to service issues. Organize service dependencies, alert thresholds, dashboard links, copyable commands, duty rotations, and an incident response checklist.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Process SARIF files, a standard format for static analysis results, to filter alerts, remove duplicates, combine findings from multiple tools, and produce reports. It also supports comparing runs and integrating result checks into CI/CD pipelines.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Design notification routing that sends agent messages to channels by topic, such as security, releases, or daily digests. Use shared configuration and message tags to keep important alerts visible among routine updates.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
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.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Design observability strategies: SLI/SLO frameworks, alerting, and dashboards. Use when instrumenting a production service, tuning alert rules, designing Grafana dashboards, defining SLOs and error budgets, or reducing alert fatigue.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Configure competitor alerts: change thresholds per competitor, urgency routing, digests. "set up competitor alerts"
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Adjudicates whether a hit generated by sanctions, PEP, or adverse-media screening is a true positive, false positive, or requires human escalation. Use whenever a user presents a screening alert, a name match against a watchlist (OFAC SDN, EU consolidated list, UK OFSI, UN list, PEP list, adverse media hit, etc.), or asks to clear a screening hit / reduce false positives / determine whether a flagged name is actually the listed party. Use even when the user describes the task casually — "is this person actually on the sanctions list", "did we get a real match", "clear this alert", "I have a hit on X" — these are all screening-adjudication tasks. Produces a deterministic determination with full audit trail (structured JSON + human-readable narrative). Designed for use by compliance analysts and screening systems.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Send Telegram messages, files, and alerts via bot API; read replies; ask questions with inline buttons and wait for the answer (approve-from-phone). Supports multiple bots and named chat targets. Use when the user wants to send a Telegram message or alert, get notified on Telegram when a task finishes or needs input, ask for approval via Telegram, or wire Telegram notifications into hooks, cron jobs, or CI. Triggers: 'telegram', 'send me a telegram', 'alert me on telegram', 'ask me on telegram', 'notify me when done'.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Alert Logic integration. Manage data, records, and automate workflows. Use when the user wants to interact with Alert Logic data.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
AlertOps integration. Manage data, records, and automate workflows. Use when the user wants to interact with AlertOps data.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Fix "Requested backend named 'X' does not exist" or TLS alert errors in Fastly Compute@Edge. Use when: (1) Backend works locally but fails in production with "backend does not exist", (2) TLS alert received (alert_id=0) errors when calling external APIs from Fastly, (3) Backends defined in fastly.toml aren't available after deployment. The fastly.toml [[backends]] section only applies during initial service creation - existing services require backends to be added via CLI or API with proper SSL/SNI configuration.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Site reliability specialist for Prometheus metrics, distributed tracing, alerting strategies, and SLO designUse when "observability, monitoring, prometheus, grafana, alerting, slo, sli, metrics, tracing, logging, on-call, incident, observability, prometheus, grafana, tracing, jaeger, alerting, slo, sli, metrics, logging, sre, ml-memory" mentioned.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Automatic init the first time Claude acts in an incident or alerts channel — one named like #inc-…, #incident-…, #sev0-…/#sev1-…, or whose recent messages are pages or alerts from PagerDuty, Opsgenie, incident.io, Datadog, Sentry or Grafana, or relayed by people (talk about being paged is not an alert) — that isn't already a team's oncall / monitoring channel. Run once per channel, on first contact (just invited, first @-mention, channel just created), before doing what was asked: load the oncall memory oncall setup wrote to shared workspace memory, pick the owning team's section, work out which monitoring / paging / code tools Claude can reach and which are missing, post one short zero-context message, note findings in this channel's memory, then hand off to `incident-investigate` if something was asked — or immediately, unasked, when the channel was plainly opened for a live outage. Works with no oncall memory (offers setup once). Also on "load the oncall setup here" / "init this incident".
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
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".
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
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.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
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.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
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.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.