[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M77MR68ZS46G10CS0RRAZSYP":3,"skill-same:01M77MR68ZS46G10CS0RRAZSYP":46},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":24,"commitSha":25,"skillDirectory":26,"forksCount":27,"repositoryHtmlUrl":28,"repositoryHomepageUrl":6,"ownerHtmlUrl":29,"ownerBlogUrl":30,"ownerDescription":6,"updatedAt":31,"install":32,"resources":45},"01M77MR68ZS46G10CS0RRAZSYP","incident-postmortem",null,"Use when an outage, production incident, or significant service degradation has occurred and the team needs to write a structured blameless post-mortem. Triggers on phrases like \"write a post-mortem\", \"incident review\", \"what went wrong\", \"outage report\", \"root cause analysis\", or \"RCA\". Covers timeline reconstruction, contributing factor analysis, impact quantification, and action item generation with owners.","Reihantt6\u002Fsns-myagent","Reihantt6","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F219822095?v=4","01M77KK94PV8B7C2D9XWXNS8DJ","Mohamad Reihan tegar prasetya","01M77KK958QFMTHYXGXFV7KZ79",2,"MIT","https:\u002F\u002Fgithub.com\u002FReihantt6\u002Fsns-myagent\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fincident-postmortem\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: incident-postmortem\ndescription: 'Use when an outage, production incident, or significant service degradation has occurred and the team needs to write a structured blameless post-mortem. Triggers on phrases like \"write a post-mortem\", \"incident review\", \"what went wrong\", \"outage report\", \"root cause analysis\", or \"RCA\". Covers timeline reconstruction, contributing factor analysis, impact quantification, and action item generation with owners.'\n---\n\n# Incident Post-Mortem\n\nGuide a team through writing a structured, blameless post-mortem after a production incident. The output is a document that builds shared understanding, identifies root causes without blame, and produces concrete action items to prevent recurrence.\n\n## Blameless Principle\n\nSystems fail, not people. The goal is to understand HOW the incident happened — not WHO caused it. Avoid language like \"X forgot to\", \"Y should have known\". Use \"the system did not\", \"the process lacked\", \"the alert did not fire\".\n\n## When to Use\n\n- Production outage or service degradation has been resolved\n- A significant near-miss occurred (would have been an incident if caught later)\n- User-facing errors, data loss, or SLA breach happened\n- Team wants to capture learnings before context fades\n\n**Not for:** Minor bugs caught in staging, planned maintenance windows, or incidents with no learning value.\n\n## Input Requirements\n\nGather these details before writing the post-mortem. Ask for anything missing:\n\n### Incident Metadata\n- Incident title (short, descriptive)\n- Date and time of detection (with timezone)\n- Date and time of resolution\n- Severity \u002F impact level (P1–P4 or equivalent)\n- Incident commander \u002F on-call owner\n\n### Impact\n- Affected services and systems\n- User-facing impact (errors, slowness, full outage)\n- Estimated number of users affected\n- Data loss or corruption (yes\u002Fno, scope)\n- SLA\u002FSLO breach (yes\u002Fno, by how much)\n\n### Timeline Events\nKey moments to reconstruct:\n- First symptom occurred\n- Alert fired (or was noticed manually)\n- On-call paged \u002F incident declared\n- Investigation started\n- Root cause identified\n- Mitigation applied\n- Full resolution confirmed\n- Customer communication sent (if any)\n\n### Contributing Factors\nAsk the team: \"What made this worse than it needed to be?\" — not \"who failed\". Examples:\n- Alert threshold too high \u002F alert didn't fire\n- Runbook was missing or outdated\n- Deploy lacked a feature flag for rollback\n- Monitoring didn't cover this failure mode\n- On-call handoff missed context\n\n## Process\n\n### Step 1 — Gather Metadata\nIf the user has not provided full incident details, ask for them section by section. Don't proceed to writing until you have: title, times, severity, affected services, and at least a rough timeline.\n\n### Step 2 — Reconstruct Timeline\nWork with the user to build a precise chronological timeline. For each event:\n- Exact time (UTC preferred)\n- What happened (system event or human action)\n- Who observed it or took the action\n- Link to log \u002F alert \u002F Slack message if available\n\nFlag gaps: \"We don't know what happened between 14:32 and 14:47 — worth checking logs.\"\n\n### Step 3 — Root Cause Analysis\nUse the **5 Whys** iteratively:\n\n```\nWhy did users see 500 errors?\n→ The API pods were crash-looping.\n\nWhy were they crash-looping?\n→ Memory limit was exceeded.\n\nWhy was the limit exceeded?\n→ A new query was loading full result sets into memory.\n\nWhy wasn't this caught before deploy?\n→ Load tests only covered the p50 case, not high-cardinality accounts.\n\nWhy did load tests only cover p50?\n→ We had no test fixtures for large accounts.\n```\n\nStop when you reach a system\u002Fprocess gap you can fix. The last \"why\" should point to an action item.\n\nDistinguish:\n- **Root cause** — the deepest systemic gap (one or two)\n- **Contributing factors** — conditions that made it worse but aren't the root cause\n\n### Step 4 — Impact Quantification\nHelp the user be precise:\n- Duration: detection to resolution (not symptom start to resolution — separate these)\n- Error rate at peak vs. normal baseline\n- Percentage of traffic affected\n- Revenue \u002F business impact if known\n\n### Step 5 — Action Items\nFor each root cause and contributing factor, generate at least one action item:\n\n| # | Action | Owner | Due Date | Priority |\n|---|--------|-------|----------|----------|\n| 1 | Add load test fixtures for accounts > 10k records | @eng-team | 2026-07-01 | High |\n| 2 | Lower memory alert threshold from 90% to 75% | @platform | 2026-06-23 | High |\n| 3 | Add runbook for memory OOM pods | @on-call-rotation | 2026-06-30 | Medium |\n\nAction items must have an owner (a person, not a team) and a due date. Vague actions like \"improve monitoring\" are not acceptable — break them into specific deliverables.\n\n### Step 6 — Write the Document\nProduce the full post-mortem using the template below. Save to `docs\u002Fpostmortems\u002FYYYY-MM-DD-\u003Cslug>.md`.\n\n## Output Template\n\n```markdown\n# Post-Mortem: [Incident Title]\n\n**Date:** YYYY-MM-DD  \n**Severity:** P[1-4]  \n**Duration:** X hours Y minutes (HH:MM UTC – HH:MM UTC)  \n**Incident Commander:** @name  \n**Status:** Resolved\n\n---\n\n## Summary\n\n[2–3 sentences. What happened, what was the user impact, how was it resolved. Written for someone who wasn't involved.]\n\n## Impact\n\n| Dimension | Value |\n|-----------|-------|\n| Affected services | [list] |\n| User-facing impact | [errors \u002F degraded \u002F full outage] |\n| Users affected | [estimated number or %] |\n| Peak error rate | [X% vs Y% baseline] |\n| Data loss | [none \u002F describe scope] |\n| SLA breach | [yes\u002Fno — by how much] |\n\n## Timeline\n\nAll times UTC.\n\n| Time | Event |\n|------|-------|\n| HH:MM | [First symptom \u002F alert fired] |\n| HH:MM | [On-call paged] |\n| HH:MM | [Incident declared] |\n| HH:MM | [Root cause identified] |\n| HH:MM | [Mitigation applied] |\n| HH:MM | [Full resolution confirmed] |\n| HH:MM | [Customer communication sent] |\n\n## Root Cause\n\n[1–2 paragraphs. The deepest systemic gap that, if fixed, would have prevented the incident. Written in blameless language. Reference the 5 Whys chain if helpful.]\n\n## Contributing Factors\n\n- [Factor 1 — condition that made the incident worse]\n- [Factor 2]\n- [Factor 3]\n\n## What Went Well\n\n- [Thing that worked — good alert, fast response, clear runbook]\n- [Another positive]\n\n## What Could Have Gone Better\n\n- [Gap in process, tooling, or coverage — no blame language]\n- [Another gap]\n\n## Action Items\n\n| # | Action | Owner | Due Date | Priority |\n|---|--------|-------|----------|----------|\n| 1 | [Specific deliverable] | @person | YYYY-MM-DD | High\u002FMedium\u002FLow |\n| 2 | | | | |\n\n## Lessons Learned\n\n[Optional. 2–4 bullet points capturing non-obvious insights worth sharing with the broader team.]\n```\n\n## Common Mistakes\n\n| Mistake | Fix |\n|---------|-----|\n| \"Bob forgot to check the config\" | \"The deploy checklist did not include config validation\" |\n| Root cause is \"human error\" | Keep asking Why — human error is always a symptom |\n| Action items without owners | Every item needs a named individual, not a team |\n| Timeline reconstructed from memory | Check logs, alerts, Slack, PagerDuty before writing |\n| \"Improve monitoring\" as an action | Specify: which service, which metric, what threshold, by when |\n| Post-mortem written weeks later | Write within 48–72 hours while context is fresh |\n","# Incident Post-Mortem\n\nGuide a team through writing a structured, blameless post-mortem after a production incident. The output is a document that builds shared understanding, identifies root causes without blame, and produces concrete action items to prevent recurrence.\n\n## Blameless Principle\n\nSystems fail, not people. The goal is to understand HOW the incident happened — not WHO caused it. Avoid language like \"X forgot to\", \"Y should have known\". Use \"the system did not\", \"the process lacked\", \"the alert did not fire\".\n\n## When to Use\n\n- Production outage or service degradation has been resolved\n- A significant near-miss occurred (would have been an incident if caught later)\n- User-facing errors, data loss, or SLA breach happened\n- Team wants to capture learnings before context fades\n\n**Not for:** Minor bugs caught in staging, planned maintenance windows, or incidents with no learning value.\n\n## Input Requirements\n\nGather these details before writing the post-mortem. Ask for anything missing:\n\n### Incident Metadata\n- Incident title (short, descriptive)\n- Date and time of detection (with timezone)\n- Date and time of resolution\n- Severity \u002F impact level (P1–P4 or equivalent)\n- Incident commander \u002F on-call owner\n\n### Impact\n- Affected services and systems\n- User-facing impact (errors, slowness, full outage)\n- Estimated number of users affected\n- Data loss or corruption (yes\u002Fno, scope)\n- SLA\u002FSLO breach (yes\u002Fno, by how much)\n\n### Timeline Events\nKey moments to reconstruct:\n- First symptom occurred\n- Alert fired (or was noticed manually)\n- On-call paged \u002F incident declared\n- Investigation started\n- Root cause identified\n- Mitigation applied\n- Full resolution confirmed\n- Customer communication sent (if any)\n\n### Contributing Factors\nAsk the team: \"What made this worse than it needed to be?\" — not \"who failed\". Examples:\n- Alert threshold too high \u002F alert didn't fire\n- Runbook was missing or outdated\n- Deploy lacked a feature flag for rollback\n- Monitoring didn't cover this failure mode\n- On-call handoff missed context\n\n## Process\n\n### Step 1 — Gather Metadata\nIf the user has not provided full incident details, ask for them section by section. Don't proceed to writing until you have: title, times, severity, affected services, and at least a rough timeline.\n\n### Step 2 — Reconstruct Timeline\nWork with the user to build a precise chronological timeline. For each event:\n- Exact time (UTC preferred)\n- What happened (system event or human action)\n- Who observed it or took the action\n- Link to log \u002F alert \u002F Slack message if available\n\nFlag gaps: \"We don't know what happened between 14:32 and 14:47 — worth checking logs.\"\n\n### Step 3 — Root Cause Analysis\nUse the **5 Whys** iteratively:\n\n```\nWhy did users see 500 errors?\n→ The API pods were crash-looping.\n\nWhy were they crash-looping?\n→ Memory limit was exceeded.\n\nWhy was the limit exceeded?\n→ A new query was loading full result sets into memory.\n\nWhy wasn't this caught before deploy?\n→ Load tests only covered the p50 case, not high-cardinality accounts.\n\nWhy did load tests only cover p50?\n→ We had no test fixtures for large accounts.\n```\n\nStop when you reach a system\u002Fprocess gap you can fix. The last \"why\" should point to an action item.\n\nDistinguish:\n- **Root cause** — the deepest systemic gap (one or two)\n- **Contributing factors** — conditions that made it worse but aren't the root cause\n\n### Step 4 — Impact Quantification\nHelp the user be precise:\n- Duration: detection to resolution (not symptom start to resolution — separate these)\n- Error rate at peak vs. normal baseline\n- Percentage of traffic affected\n- Revenue \u002F business impact if known\n\n### Step 5 — Action Items\nFor each root cause and contributing factor, generate at least one action item:\n\n| # | Action | Owner | Due Date | Priority |\n|---|--------|-------|----------|----------|\n| 1 | Add load test fixtures for accounts > 10k records | @eng-team | 2026-07-01 | High |\n| 2 | Lower memory alert threshold from 90% to 75% | @platform | 2026-06-23 | High |\n| 3 | Add runbook for memory OOM pods | @on-call-rotation | 2026-06-30 | Medium |\n\nAction items must have an owner (a person, not a team) and a due date. Vague actions like \"improve monitoring\" are not acceptable — break them into specific deliverables.\n\n### Step 6 — Write the Document\nProduce the full post-mortem using the template below. Save to `docs\u002Fpostmortems\u002FYYYY-MM-DD-\u003Cslug>.md`.\n\n## Output Template\n\n```markdown\n# Post-Mortem: [Incident Title]\n\n**Date:** YYYY-MM-DD  \n**Severity:** P[1-4]  \n**Duration:** X hours Y minutes (HH:MM UTC – HH:MM UTC)  \n**Incident Commander:** @name  \n**Status:** Resolved\n\n---\n\n## Summary\n\n[2–3 sentences. What happened, what was the user impact, how was it resolved. Written for someone who wasn't involved.]\n\n## Impact\n\n| Dimension | Value |\n|-----------|-------|\n| Affected services | [list] |\n| User-facing impact | [errors \u002F degraded \u002F full outage] |\n| Users affected | [estimated number or %] |\n| Peak error rate | [X% vs Y% baseline] |\n| Data loss | [none \u002F describe scope] |\n| SLA breach | [yes\u002Fno — by how much] |\n\n## Timeline\n\nAll times UTC.\n\n| Time | Event |\n|------|-------|\n| HH:MM | [First symptom \u002F alert fired] |\n| HH:MM | [On-call paged] |\n| HH:MM | [Incident declared] |\n| HH:MM | [Root cause identified] |\n| HH:MM | [Mitigation applied] |\n| HH:MM | [Full resolution confirmed] |\n| HH:MM | [Customer communication sent] |\n\n## Root Cause\n\n[1–2 paragraphs. The deepest systemic gap that, if fixed, would have prevented the incident. Written in blameless language. Reference the 5 Whys chain if helpful.]\n\n## Contributing Factors\n\n- [Factor 1 — condition that made the incident worse]\n- [Factor 2]\n- [Factor 3]\n\n## What Went Well\n\n- [Thing that worked — good alert, fast response, clear runbook]\n- [Another positive]\n\n## What Could Have Gone Better\n\n- [Gap in process, tooling, or coverage — no blame language]\n- [Another gap]\n\n## Action Items\n\n| # | Action | Owner | Due Date | Priority |\n|---|--------|-------|----------|----------|\n| 1 | [Specific deliverable] | @person | YYYY-MM-DD | High\u002FMedium\u002FLow |\n| 2 | | | | |\n\n## Lessons Learned\n\n[Optional. 2–4 bullet points capturing non-obvious insights worth sharing with the broader team.]\n```\n\n## Common Mistakes\n\n| Mistake | Fix |\n|---------|-----|\n| \"Bob forgot to check the config\" | \"The deploy checklist did not include config validation\" |\n| Root cause is \"human error\" | Keep asking Why — human error is always a symptom |\n| Action items without owners | Every item needs a named individual, not a team |\n| Timeline reconstructed from memory | Check logs, alerts, Slack, PagerDuty before writing |\n| \"Improve monitoring\" as an action | Specify: which service, which metric, what threshold, by when |\n| Post-mortem written weeks later | Write within 48–72 hours while context is fresh |\n",{"name":5,"description":7},"main","58843b159d7a4050d6b785a98b908cce505c0b92",".agents\u002Fskills\u002Fincident-postmortem",0,"https:\u002F\u002Fgithub.com\u002FReihantt6\u002Fsns-myagent","https:\u002F\u002Fgithub.com\u002FReihantt6","reihsns.web.id","2026-08-19 20:08:18",{"source":8,"skillName":5,"commands":33,"prompt":43,"zipAvailable":44},[34,37,40],{"tool":35,"command":36},"npx","npx skills add Reihantt6\u002Fsns-myagent --skill incident-postmortem",{"tool":38,"command":39},"bunx","bunx skills add Reihantt6\u002Fsns-myagent --skill incident-postmortem",{"tool":41,"command":42},"pnpm","pnpm dlx skills add Reihantt6\u002Fsns-myagent --skill incident-postmortem","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FReihantt6\u002Fsns-myagent\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fincident-postmortem\u002FSKILL.md",true,[],[47,54,61,68,75,82],{"skillNo":48,"name":49,"nameZh":6,"description":50,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":51,"categories":52,"keywords":53,"publishedAt":19},"01M77XDCYZ407XYMF2T4P6F7VT","youtube-transcript","Extract transcripts from YouTube videos. Use when the user asks for a transcript, subtitles, or captions of a YouTube video and provides a YouTube URL (youtube.com\u002Fwatch?v=, youtu.be\u002F, or similar). Supports output with or without timestamps.","https:\u002F\u002Fgithub.com\u002FReihantt6\u002Fsns-myagent\u002Fblob\u002Fmain\u002Fagent\u002Fskills\u002Fyoutube-transcript\u002FSKILL.md",[],[],{"skillNo":55,"name":56,"nameZh":6,"description":57,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":58,"categories":59,"keywords":60,"publishedAt":19},"01M77XD7PBC98J6MXGJJ2TJ8DX","youtube-thumbnail-design","YouTube thumbnail design with specific dimensions, contrast rules, and mobile preview optimization. Covers safe zones, text placement, face expression psychology, and A\u002FB testing. Use for: YouTube thumbnails, video cover images, click-through optimization. Triggers: youtube thumbnail, thumbnail design, video thumbnail, click through rate, ctr optimization, youtube cover, video cover image, thumbnail maker, thumbnail tips, youtube design, video preview image","https:\u002F\u002Fgithub.com\u002FReihantt6\u002Fsns-myagent\u002Fblob\u002Fmain\u002Fagent\u002Fskills\u002Fyoutube-thumbnail-design\u002FSKILL.md",[],[],{"skillNo":62,"name":63,"nameZh":6,"description":64,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":65,"categories":66,"keywords":67,"publishedAt":19},"01M77XD2541C8HXJ6RHYZP4NGJ","youtube-short-maker","Make YouTube Shorts that hold attention with Pexo — vertical 9:16, fast-paced, hook in the first 3 seconds. Describe your topic and Pexo writes the script, generates the shots, picks the models, and assembles a finished Short with music and captions. Use for YouTube Shorts: \"youtube short\", \"make a youtube short\", \"shorts video\", \"short-form video\". NOT for long-form or landscape video.","https:\u002F\u002Fgithub.com\u002FReihantt6\u002Fsns-myagent\u002Fblob\u002Fmain\u002Fagent\u002Fskills\u002Fyoutube-short-maker\u002FSKILL.md",[],[],{"skillNo":69,"name":70,"nameZh":6,"description":71,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":72,"categories":73,"keywords":74,"publishedAt":19},"01M77XCXKVSYK7KTZ3PQBVVGFD","xcode-project-setup","Safely modifies Xcode projects (.pbxproj) to add Swift Packages and link files. Use this skill whenever an iOS project needs dependencies installed (e.g. Firebase, Alamofire).","https:\u002F\u002Fgithub.com\u002FReihantt6\u002Fsns-myagent\u002Fblob\u002Fmain\u002Fagent\u002Fskills\u002Fxcode-project-setup\u002FSKILL.md",[],[],{"skillNo":76,"name":77,"nameZh":6,"description":78,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":79,"categories":80,"keywords":81,"publishedAt":19},"01M77XCR1DV8ZQK2NHWKVY4EWX","x402","Set up Browser Use Cloud payments with x402 — pay per request from a crypto wallet (USDC on Base mainnet), no signup or API key. Two setups it works out up front — \"just use it\" (set up a wallet so you or Claude Code can run cloud browser tasks paid from the wallet — Claude writes and runs throwaway scripts, nothing touches your codebase) or \"build it in\" (install the SDK and write the key + code into your project). Walks through wallet setup, funding, .env, and a ~$1 test run. Use when the user asks about x402, pay-per-use, USDC payments, or wants Browser Use Cloud without an API key. For the free-tier signup (reverse-CAPTCHA → API key), use `browser-use cloud signup` or the `cloud` skill instead.","https:\u002F\u002Fgithub.com\u002FReihantt6\u002Fsns-myagent\u002Fblob\u002Fmain\u002Fagent\u002Fskills\u002Fx402\u002FSKILL.md",[],[],{"skillNo":83,"name":84,"nameZh":6,"description":85,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":86,"categories":87,"keywords":88,"publishedAt":19},"01M77XCMD3R3ZBZQQSW6E0793B","x-twitter-scraper","Build GitHub Copilot workflows with Xquik X API SDKs, REST endpoints, hosted Apify Actor runs, MCP tools, TweetClaw OpenClaw plugin installs, signed webhooks, tweet search, user lookup, follower exports, media actions, and agent automation.","https:\u002F\u002Fgithub.com\u002FReihantt6\u002Fsns-myagent\u002Fblob\u002Fmain\u002Fagent\u002Fskills\u002Fx-twitter-scraper\u002FSKILL.md",[],[]]