739건 · 관련도순
Create slides for safety reviews, risk discussions, incident retrospectives, or security exercises. Warning stripes, three-level cards, status alerts, policy code blocks, checklists, and stacked bar charts provide a visual structure for the presentation.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Use gog to inspect Google AdSense accounts, ad units, sites, payments, alerts, and policy issues. Generate AdSense reports and retrieve details about ad clients and channels to review advertising operations.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Integrate Birdeye API data to track token prices, charts, holders, trades, and wallet portfolios. Supports profit and loss analysis, token risk checks, and live price or large-trade streams, with access depending on the service plan.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Build failure handling into n8n workflows with separate error paths, retries, alerts, and clear API responses. Use it for webhooks and unattended jobs to make failures visible and return status codes that explain what went wrong.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Generate PNG or SVG charts from data for reports, monitoring alerts, and dashboards. Choose from line, bar, pie, candlestick, and heatmap charts, then adjust labels, colors, and annotations using Node.js without a browser or external API calls.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Deploy and operate DOCA Argus Service on BlueField to monitor suspicious activity. This skill guides detection settings, forwarding findings to a security monitoring system, and troubleshooting missing alerts, excessive noise, or performance impact.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Automate Datadog monitoring through Rube MCP, a connection for agent tools. Query metrics and logs, manage alert monitors and dashboards, record events, and schedule periods when maintenance notifications are suppressed.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Golang everyday observability — the always-on signals in production. Covers structured logging with slog, Prometheus metrics, OpenTelemetry distributed tracing, continuous profiling with pprof/Pyroscope, server-side RUM event tracking, alerting, and Grafana dashboards. Apply when instrumenting Go services for production monitoring, setting up metrics or alerting, adding OpenTelemetry tracing, correlating logs with traces, migrating legacy loggers (zap/logrus/zerolog) to slog, adding observability to new features, or implementing GDPR/CCPA-compliant tracking with Customer Data Platforms (CDP). Not for temporary deep-dive performance investigation (→ See `samber/cc-skills-golang@golang-benchmark` and `samber/cc-skills-golang@golang-performance` skills).
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Govern Azure costs with budgets, alerts, tags, and policy restrictions. WHEN: "Azure budget health", "configured budget overrun", "list Azure budgets", "create Azure budget", "budget alerts", "budget coverage", "missing CostCenter tags", "allowed VM SKUs", "allowed Azure regions", "would this SKU be denied", "cost guardrails". DO NOT USE FOR: planning-target forecasts, bill investigations, pricing, rightsizing, or commitments.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use when the user asks to "track rankings" or "查排名"; measures keyword and SERP-position deltas over time from provided exports or connected tools, including AI-response checks. Not for multi-metric stakeholder reports or setting alerts — use performance-monitor (report or alert mode). 排名追踪/SERP监控
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use when the user asks to "generate an SEO report", "出月报", "set SEO alerts", or "排名掉了提醒我"; two modes — report builds multi-metric traffic/ranking/authority/content dashboards, and alert configures threshold notifications for future ranking, traffic, technical, backlink, competitor, and AI-visibility changes. Not for raw position-by-position deltas — use rank-tracker. SEO报告/绩效仪表盘/SEO预警/排名监控
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Sets up CloudWatch observability for the first time - Omni (CloudWatch Application Observability) and classic CloudWatch. Omni: creating a Space or Domain; access grants (who has access, at what level) and access profiles bounding async alerts, integrations, or agents; instrumenting an app or AI agent with the plain ADOT SDK so traces reach Omni (Python/Node/Java/.NET on EC2/ECS/EKS/Lambda), incl. no-image-rebuild and .NET CoreCLR vars; ingesting Azure telemetry via the CloudWatch agent on an Azure VM or AKS; connecting Slack to a Space; whether GitHub or a custom MCP tool server (HTTP/stdio; API key, bearer, OAuth2) can be connected. CloudWatch: onboarding a service to Application Signals - ADOT auto-instrumentation, the amazon-cloudwatch-observability add-on, monitored service, reporting telemetry, ServiceEvents, CI/CD git/deployment metadata, Terraform/manifest edits. For using what is set up - queries, dashboards, alarms, Omni alerts, X-Ray, synthetics, Dynamic Instrumentation - use aws-observability.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Set up Apollo.io monitoring and observability. Use when implementing logging, metrics, tracing, and alerting for Apollo integrations. Trigger with phrases like "apollo monitoring", "apollo metrics", "apollo observability", "apollo logging", "apollo alerts".
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Fixed-format templates for Slack alerts, supplier emails, and escalations. Load this whenever the task is "notify", "alert", "email", or "tell ops".
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Makes systems debuggable and reliably operable — instrumentation, alerting that is worth waking for, service objectives, and learning from failure. Use this to instrument a service, fix alerting that is ignored, set error budgets or reliability targets, prepare for on-call, or run a blameless post-incident review.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Builds the capability to notice an attack in progress — deciding what to log and retain, centralizing it somewhere tamper-resistant, writing detections that fire on attacker behavior rather than on individual events, tuning out the noise that trains people to ignore alerts, and defining what happens when something fires. Use this to design or assess monitoring coverage, work out why an incident went unnoticed, cut alert volume without losing signal, or decide what a detection capability should cost.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Run a Google Alerts-style keyword coverage tracker. Uses news-search for recent keyword queries, lets the LLM dedupe and classify real features versus junk, stores decisions in SQLite, and alerts only on new real coverage.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Govern Azure costs with budgets, alerts, tags, and policy restrictions. WHEN: "Azure budget health", "configured budget overrun", "list Azure budgets", "create Azure budget", "budget alerts", "budget coverage", "missing CostCenter tags", "allowed VM SKUs", "allowed Azure regions", "would this SKU be denied", "cost guardrails". DO NOT USE FOR: planning-target forecasts, bill investigations, pricing, rightsizing, or commitments.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Designs and audits macOS launchd watchdogs: LaunchAgent/LaunchDaemon setup, plist edits, scheduled self-healing, repeated notifications, apps reopening after quit, crash/repair loops, Script Editor alerts, stop/disable/restart, cooldown/backoff, notification throttling, alert decisions, schedule readback, WatchPaths/FSEvents event triggers. Supports periodic observers. launchd 守护进程、常驻任务、开机自启、后台监控、定时自愈、通知来源排查、事件驱动监控。
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Set up and send technical status notifications through WeCom (Enterprise WeChat) webhooks. Use this skill whenever the user needs to send notifications, alerts, backup completion reports, or status updates via WeCom; when they mention 企业微信, 企微机器人, webhook, or alerting; or when a message needs to be clear, unambiguous, and technically precise rather than vague or condescending.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Specify the tracing, metrics, and alerting for an AI agent or LLM feature in production. Use when asked what to log for an LLM app, design agent tracing or spans, define quality and cost monitors, or answer 'how do we know if the agent is misbehaving?'. Produces an observability spec with a trace schema, metric definitions with owners and alert thresholds, sampling and retention policy, and a privacy note for logged content.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Fetch WeatherKit current, minute, hourly, and daily forecasts; weather alerts; iOS 18+ changes, historical comparisons, summaries, and statistics; and required Apple Weather attribution. Use when integrating weather data, showing forecasts or alerts, caching WeatherKit responses, displaying attribution, or reviewing WeatherKit query limits in iOS apps.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Compare this period's reliability against the prior period using Agent Monitor data — error rate (APIError/total) and tool-failure rate (PreToolUse→PostToolUse gap) — flag any regression where reliability got worse, and optionally wire a persistent alert rule so the dashboard catches the next regression automatically. Use when checking whether reliability degraded.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Define a spend budget for Claude Code and, optionally, create a cost alert rule that fires when usage crosses the limit, via POST /api/alerts/rules on the Agent Monitor dashboard. Reads current spend from /api/pricing/cost to size the budget sensibly and explains every rule field before writing. Use when setting a spend limit or wiring up a budget guardrail.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.