「incident」の検索結果

Use during or right after an incident — frames severity, sets comms cadence, drafts the post-mortem skeleton — even when the user just says 'production is down' or 'wir haben einen Vorfall'.

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

Use after an incident or outage is resolved — blame-free facilitation, root cause, corrective actions, memory write-back — even for a near-miss. Consumes the incident-commander skeleton.

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

Build incident response timelines and report packs from event logs. Use for detection-to-recovery reporting, phase tracking, and stakeholder-ready incident summaries.

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

Automate AWS GuardDuty threat detection findings processing using EventBridge and Lambda to enable real-time incident response, automatic quarantine of compromised resources, and security notification workflows.

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

Build a structured SOC escalation matrix defining severity tiers, response SLAs, escalation paths, and notification procedures for security incidents.

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

Performs Linux memory acquisition using LiME (Linux Memory Extractor) kernel module and analysis with Volatility 3 framework. Extracts process lists, network connections, bash history, loaded kernel modules, and injected code from Linux memory images. Use when performing incident response on compromised Linux systems.

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

Analyzes network traffic captures and flow data to identify adversary activity during security incidents, including command-and-control communications, lateral movement, data exfiltration, and exploitation attempts. Uses Wireshark, Zeek, and NetFlow analysis techniques. Activates for requests involving network traffic analysis, packet capture investigation, PCAP analysis, network forensics, C2 traffic detection, or exfiltration detection.

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

Leverages Splunk Enterprise Security and SPL (Search Processing Language) to investigate security incidents through log correlation, timeline reconstruction, and anomaly detection. Covers Windows event logs, firewall logs, proxy logs, and authentication data analysis. Activates for requests involving Splunk investigation, SPL queries, SIEM log analysis, security event correlation, or log-based incident investigation.

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

設計文書、分析レポート、報告書などを批判的な視点で徹底レビューするスキル。 6つの異なる立場（開発者、PM、顧客、QA、セキュリティ、運用）のペルソナを持つサブエージェントが並列でレビューを実行し、 「本当にそうか？」「根拠は何か？」「テストできるか？」「運用できるか？」という視点で 曖昧さ、根拠不足、論理飛躍、テスト不能、セキュリティリスク、運用懸念を検出する。 Use when reviewing design documents, analysis reports, incident reports, or any document requiring rigorous validation of claims and evidence.

大規模システムリプレース・移行プロジェクトについて、マルチベンダー管理に長けたPMOの視点で「見落とされがちな潜在リスク」を洗い出す。正常系設計や特定ベンダーの担当範囲内には現れにくい「ベンダー間の隙間」「業務影響」「異常系」の死角を、4視点の分析フレームワークで特定し、Backlog起票用のリスク表とキラークエスチョンを生成する。要件定義・運用設計・負荷試験フェーズ特化フレームワークへの切替にも対応。総合テスト終盤・移行リハーサル前・負荷試験計画時のリスク総ざらいに使用する。Do NOT use for 個別インシデントの根本原因分析（incident-rca）、要求の追加・変更・矛盾検証（requirement-management）、運用設計書そのものの新規作成（operations-design）。

インフラメトリクスの定期調査を体系的に実施し、サービスの健全性を評価する。2層アプローチで11カテゴリのメトリクスを確認し、構造化レポートを作成する。定期的なサービス監視、障害予兆の検出、パフォーマンス評価に使用する。Do NOT use for 個別インシデントの根本原因分析（incident-rcaを使用すること）。

Mitigate incidental code complexity when control flow is tangled, nesting is deep, names are hard to parse, or reasoning requires cross-file hops. Use when a review stalls on readability, you need an analysis-first refactor plan before edits, or you want essential-vs-incidental verdicts, ranked simplification steps, a small structural sketch, and a TRACE assessment (analysis-only; no edits).

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

Knowledge base from NIST SP 800-61 Rev. 3 (Incident Response Recommendations for Cybersecurity Risk Management). Use for CSF 2.0-aligned incident response life cycles, IR roles, Community Profile priorities for DE/RS/RC and preparation, playbooks, coordination, and continuous improvement. Covers 800-61r3 only; does not replace CSF 2.0 full text, SP 800-61r2 tactical playbooks, or sector-specific breach-notification law.

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

Turns an engineer's notes, a ticket history or a chat thread into a draft step-by-step runbook with preconditions, stop conditions, numbered steps with checks, verification, rollback and escalation, for the team to validate before use. Commands verbatim, placeholders marked, every gap UNKNOWN; never executes a step or fills a gap from general knowledge. Use when the user asks to "write a runbook from these notes", "turn this resolved ticket into a runbook", "document the steps we ran" or "check this runbook for gaps". Do not use for a business process without commands, use sop-drafter instead; for a knowledge article or known-error record, use knowledge-article-drafter; for the post-incident review, use incident-postmortem-drafter. Drafts for human review; never approves, authorises or signs off.

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

Proposes redactions of personal identifiers in pasted text or an attached document (names, contact details, identification and account numbers, dates that identify, quasi-identifiers) and returns a DRAFT redacted copy with consistent placeholder tokens plus a redaction table stating what was replaced, where and why, with a confidence level and a blank reviewer decision per row. Use when the user asks to "redact the names in this document", "de-identify this transcript before we share it", "strip personal data from these notes", "anonymise this report for publication" or "what would need redacting here". Do not use for assessing a planned processing activity, use dpia-draft-pack instead; do not use for working out what data an incident exposed, use data-incident-impact-brief instead. Never declares a document anonymised, safe to release or compliant. Drafts for human review; never approves, authorises or signs off.

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

Reads a project or processing description and returns a DRAFT data protection impact assessment pack: processing description, necessity and proportionality questions, a risk table with blank rating cells, mitigations to consider and open questions. Never rates risk, determines the lawful basis or judges adequacy; the DPO assesses and signs. Works from descriptions, never personal data. Use when the user asks to "start a DPIA for the new monitoring tool", "draft a data protection impact assessment", "scaffold a DPIA from this processing description" or "what would the DPO need for a DPIA on this". Do not use for redacting or de-identifying a document, use document-deidentification-pass instead; do not use for working out what data an incident exposed, use data-incident-impact-brief instead. Drafts for human review; never approves, authorises or signs off.

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

Turns reported data problems (messages, tickets, meeting notes, complaints) into one DRAFT issue log: one row per issue with the symptom as reported, dataset and fields named, reproduction steps, affected reports, first seen date, reporters, a suggested owner, and blank severity, root cause and status cells for the owner. Never asserts a root cause, severity or fix. Use when the user asks to "log these data issues", "turn these complaints about the numbers into an issue list", "build the data quality backlog", "which reports are hit by this data problem" or "write up the reproduction steps for this data bug". Do not use for exploring or profiling a dataset, use dataset-insight-pack instead; for an IT incident write-up, use incident-postmortem-drafter; for tracking fix actions once assigned, use corrective-action-tracker. Drafts for human review; never approves, authorises or signs off.

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

Build AI-focused SRE incident response practices for LLM outages, degraded quality, runaway cost events, and safety regressions.

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

Runbook skill for failures: cron error, PA failure, cascade, gateway disconnect, semantic DB stale. Walks: detect → classify → diagnose → notify → log. Replaces ad-hoc failure handling. Triggers: "cron failed", "X is broken", "cascade", "incident", "gateway down", "PA failure".

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

Use when working with Crowdstrike — crowdStrike Falcon endpoint detection and response, threat intelligence, host management, and incident investigation. Covers detection queries, host inventory, IOC searches, real-time response sessions, and vulnerability assessment. Use when investigating security incidents, reviewing endpoint health, analyzing threat detections, or managing CrowdStrike Falcon sensors.

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

Use when working with Bmc Helix — bMC Helix ITSM platform management covering incident management, problem management, change management, and CMDB operations. Use when creating or updating incidents with categorization and assignment, managing problem investigation workflows, processing change requests through CAB approval, or querying CMDB for infrastructure configuration items and relationships.

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

Use when working with Bigpanda — bigPanda AIOps platform management covering event correlation, root cause analysis, incident management, alert enrichment, topology-based correlation, environment management, and analytics. Use when configuring BigPanda correlation patterns, investigating correlated incidents, tuning noise reduction, or analyzing alert topology and root cause indicators.

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

Use when working with Better Stack — better Stack (formerly Logtail) for log search, uptime monitoring, incident management, on-call scheduling, and status page management. Covers log querying, monitor configuration, heartbeat checks, escalation policies, and team management. Use when searching logs, managing uptime monitors, handling incidents, or configuring on-call schedules via Better Stack API.

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

Use when working with Atlassian Statuspage — atlassian Statuspage management, component monitoring, incident communication, scheduled maintenance, and subscriber notifications. Covers page configuration, component group management, incident lifecycle, metric tracking, and uptime reporting. Use when managing public or private status pages, communicating outages, scheduling maintenance, or reviewing component uptime in Atlassian Statuspage.

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