Close the learning loop after a rescue or incident — reconstruct the timeline from action_log, run root-cause analysis (platform / site / measurement / external), produce a structured postmortem document, distill reusable insights via /learn, and propose preventive guardrails. Use after a /rescue, a CPA spike, a conversion drop, or a runaway-spend event has been handled, or when the user asks for a postmortem, retrospective, root-cause writeup, or requests インシデント振り返り / ポストモーテム / 事後分析 / なぜ起きたのか / 再発防止策. Read-and-document only — makes no ad-platform writes.
$npx -y skills add logly/mureo --skill incident-postmortemInstalls into the current project.
Run `npx skills use "https://github.com/logly/mureo" --skill "logly/mureo/incident-postmortem"` and follow the generated skill instructions now. Read its complete output, redirecting it to a temporary file first if necessary. Resolve relative paths from the supporting-files directory it provides.
Use the skills in "https://github.com/logly/mureo" that are relevant to the current task. Run `npx skills add "https://github.com/logly/mureo"` and select the relevant skills, then follow their instructions.