877건 · 관련도순
Comprehensive incident response framework from detection through resolution and post-incident review. Battle-tested SRE/DevOps practices: severity classification, timeline reconstruction, structured post-incident analysis. Use when declaring an incident, coordinating multi-team response during an outage, leading a post-mortem, or setting up on-call practices for a new service.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Facilitate structured post-incident reviews to identify root causes, document what worked and failed, and produce actionable recommendations to improve future incident response.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Responds to security incidents in cloud environments (AWS, Azure, GCP) by performing identity-based containment, cloud-native log analysis, resource isolation, and forensic evidence acquisition adapted for ephemeral cloud infrastructure. Activates for requests involving cloud incident response, AWS security incident, Azure compromise, GCP breach, cloud forensics, or cloud identity compromise.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Reads a risk register together with meeting notes and incident reports and returns a draft update pack: existing risks whose exposure, controls, ownership or status the sources say have changed, new risk candidates, closure candidates, and the one owner decision each item needs. Never assigns or changes a likelihood, impact, score or colour and never edits the register; owners decide. Use when the user asks to "update the risk register from these minutes", "refresh the register with the incidents since the last review", "reconcile the register against the notes" or "what changed on our risks". Do not use for writing up an incident itself, use incident-postmortem-drafter or data-incident-impact-brief instead; to track actions from minutes, use corrective-action-tracker. Drafts for human review; never approves, authorises or signs off.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Responds to security incidents in cloud environments (AWS, Azure, GCP) by performing identity-based containment, cloud-native log analysis, resource isolation, and forensic evidence acquisition adapted for ephemeral cloud infrastructure. Activates for requests involving cloud incident response, AWS security incident, Azure compromise, GCP breach, cloud forensics, or cloud identity compromise.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Facilitate structured post-incident reviews to identify root causes, document what worked and failed, and produce actionable recommendations to improve future incident response.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Conduz investigação de incidente — triagem, hipótese, mitigação, RCA e postmortem. Use quando o usuário disser "está fora do ar", "incidente", "caiu", "usuários reclamando", "erro em produção", "postmortem", "RCA", "o que aconteceu". Durante incidente, a pressa causa o segundo incidente.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Respond to production incidents systematically with triage, investigation, resolution, and post-mortem analysis to minimize downtime and prevent recurrence. Use when handling production outages, triaging incidents, investigating critical bugs, coordinating incident response, implementing hotfixes, conducting post-mortems, or establishing incident response procedures.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Expert SRE incident responder specializing in rapid problem resolution, modern observability, and comprehensive incident management. Masters incident command, blameless post-mortems, error budget management, and system reliability patterns. Handles critical outages, communication strategies, and continuous improvement. Use IMMEDIATELY for production incidents or SRE practices.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Facilitate structured post-incident reviews to identify root causes, document what worked and failed, and produce actionable recommendations to improve future incident response.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Responds to security incidents in cloud environments (AWS, Azure, GCP) by performing identity-based containment, cloud-native log analysis, resource isolation, and forensic evidence acquisition adapted for ephemeral cloud infrastructure. Activates for requests involving cloud incident response, AWS security incident, Azure compromise, GCP breach, cloud forensics, or cloud identity compromise.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Develop incident response procedures for LLM outages, declining answer quality, spending spikes, and unsafe outputs. Use example monitoring alerts, severity levels, recovery playbooks, and postmortem guidance to organize detection, response, and follow-up work.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Write incident review documents that focus on system conditions and learning. Organize timelines, examine root causes with evidence, and turn findings into practical follow-up actions with owners and deadlines, supported by a meeting facilitation guide.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Investigate AWS production incidents using reusable CloudWatch log queries and metric calculations. Narrow affected resources, compare alarms with deployment events, and reconstruct a timeline to identify changes that may explain the symptoms.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Investigate security incidents in Splunk by connecting authentication, endpoint, and network logs. Use SPL, Splunk’s search language, to identify suspicious activity, reconstruct event timelines, document findings, and develop detection rules.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Draft and edit internal updates, newsletters, FAQs, and incident reports using the appropriate reference format. Turn supplied notes or information retrieved through connected tools into concise communications tailored to the audience and reporting period.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Generate an operational runbook template from a service name. Provide sections for starting, stopping, health checks, incident handling, maintenance, and rollback, so teams can add service-specific commands and build consistent operating procedures.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Plan security programs for growing companies by estimating financial risk and prioritizing controls. Produce compliance roadmaps, budget justifications, incident response plans, vendor assessments, and board reports that connect security decisions to business impact.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Reconstruct an incident timeline from recorded screens and conversations, supported by available logs and monitoring. Organize symptoms, changes, response actions, and recovery evidence while distinguishing observed facts from suspected causes.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Review Google Cloud operations and develop guidance for monitoring, incident response, resource sizing, and automated deployments. Use framework-based questions and checklists to identify gaps in production readiness and plan ongoing operational improvements.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Define reliability targets for production services and calculate error budgets, the allowed amount of failure. Create monitoring rules, incident response runbooks, capacity plans, and automation scripts, with failure experiments to check recovery behavior.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Create Dockerfiles, automated build and deployment pipelines, Kubernetes configurations, and infrastructure templates. The skill also prepares deployment checks, rollback procedures, and incident response runbooks to support application releases and production operations.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Investigate production incidents and bugs using logs, metrics, and code evidence. The skill guides hypothesis testing, root cause analysis, fix validation, and reusable investigation notes, with access to configured observability tools such as Axiom.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Trace system behavior across code, APIs, authentication, data, and networks through an interactive workflow. Store steps, branches, and findings in SQLite, then export diagrams and documentation for security audits, debugging, architecture reviews, or incident analysis.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.