[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M77TZ7W30DN2TV48HP6PZTC5":3,"skill-same:01M77TZ7W30DN2TV48HP6PZTC5":52},{"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},"01M77TZ7W30DN2TV48HP6PZTC5","on-call-handoff-patterns",null,"Master on-call shift handoffs with context transfer, escalation procedures, and documentation. Use this skill when transitioning on-call responsibilities between engineers and ensuring the incoming responder has full situational awareness, when writing a shift summary that captures active incidents, ongoing investigations, and recent changes, when handing off mid-incident so a fresh engineer can take over the incident commander role without losing context, when onboarding a new engineer to the on-call rotation for the first time, or when auditing and improving the quality of existing handoff processes across teams.","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\u002Fagent\u002Fskills\u002Fon-call-handoff-patterns\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\ndescription: \"Master on-call shift handoffs with context transfer, escalation procedures, and documentation. Use this skill when transitioning on-call responsibilities between engineers and ensuring the incoming responder has full situational awareness, when writing a shift summary that captures active incidents, ongoing investigations, and recent changes, when handing off mid-incident so a fresh engineer can take over the incident commander role without losing context, when onboarding a new engineer to the on-call rotation for the first time, or when auditing and improving the quality of existing handoff processes across teams.\"\n---\n# On-Call Handoff Patterns\n\nEffective patterns for on-call shift transitions, ensuring continuity, context transfer, and reliable incident response across shifts.\n\n## When to Use This Skill\n\n- Transitioning on-call responsibilities\n- Writing shift handoff summaries\n- Documenting ongoing investigations\n- Establishing on-call rotation procedures\n- Improving handoff quality\n- Onboarding new on-call engineers\n\n## Core Concepts\n\n### 1. Handoff Components\n\n| Component                  | Purpose                 |\n| -------------------------- | ----------------------- |\n| **Active Incidents**       | What's currently broken |\n| **Ongoing Investigations** | Issues being debugged   |\n| **Recent Changes**         | Deployments, configs    |\n| **Known Issues**           | Workarounds in place    |\n| **Upcoming Events**        | Maintenance, releases   |\n\n### 2. Handoff Timing\n\n```\nRecommended: 30 min overlap between shifts\n\nOutgoing:\n├── 15 min: Write handoff document\n└── 15 min: Sync call with incoming\n\nIncoming:\n├── 15 min: Review handoff document\n├── 15 min: Sync call with outgoing\n└── 5 min: Verify alerting setup\n```\n\n## Templates and detailed worked examples\n\nFull template library and detailed worked examples live in `references\u002Fdetails.md`. Read that file when you need the concrete templates.\n\n## Troubleshooting\n\n**Incoming engineer misses a critical issue because the handoff document was incomplete.**\nUse the outgoing checklist as a gate: do not mark handoff complete until every section has at least one entry (or an explicit \"none\"). Make incomplete handoffs a blameless postmortem action item.\n\n**A 30-minute sync call is not possible due to timezone gaps.**\nFall back to the async quick handoff template (Template 2). Supplement with a short Loom or voice memo walking through the watch list. Ensure the incoming engineer has a direct contact method if they have follow-up questions.\n\n**The incoming engineer inherits a mid-incident and is immediately overwhelmed.**\nUse the incident handoff template (Template 3) specifically. The outgoing engineer should remain available on Slack for 15 minutes after handoff, even if off-call, to answer clarifying questions.\n\n**On-call handoff documents are inconsistently formatted across teams.**\nAdopt the shift handoff template organization-wide and store completed handoffs in a shared location (wiki, Notion, Confluence). Link each handoff from the on-call schedule entry in PagerDuty.\n\n**Incoming engineer cannot verify their alerting is working before the outgoing engineer logs off.**\nAdd a standard step: outgoing engineer fires a test alert and confirms incoming engineer receives it in PagerDuty and Slack before ending the overlap window.\n\n## Related Skills\n\n- [incident-classification](..\u002F..\u002Fskills\u002Fincident-classification\u002FSKILL.md) — Classify and prioritize incidents that need to be included in the handoff document\n- [postmortem-facilitation](..\u002F..\u002Fskills\u002Fpostmortem-facilitation\u002FSKILL.md) — Turn resolved incidents from the shift into structured postmortems\n","# On-Call Handoff Patterns\n\nEffective patterns for on-call shift transitions, ensuring continuity, context transfer, and reliable incident response across shifts.\n\n## When to Use This Skill\n\n- Transitioning on-call responsibilities\n- Writing shift handoff summaries\n- Documenting ongoing investigations\n- Establishing on-call rotation procedures\n- Improving handoff quality\n- Onboarding new on-call engineers\n\n## Core Concepts\n\n### 1. Handoff Components\n\n| Component                  | Purpose                 |\n| -------------------------- | ----------------------- |\n| **Active Incidents**       | What's currently broken |\n| **Ongoing Investigations** | Issues being debugged   |\n| **Recent Changes**         | Deployments, configs    |\n| **Known Issues**           | Workarounds in place    |\n| **Upcoming Events**        | Maintenance, releases   |\n\n### 2. Handoff Timing\n\n```\nRecommended: 30 min overlap between shifts\n\nOutgoing:\n├── 15 min: Write handoff document\n└── 15 min: Sync call with incoming\n\nIncoming:\n├── 15 min: Review handoff document\n├── 15 min: Sync call with outgoing\n└── 5 min: Verify alerting setup\n```\n\n## Templates and detailed worked examples\n\nFull template library and detailed worked examples live in `references\u002Fdetails.md`. Read that file when you need the concrete templates.\n\n## Troubleshooting\n\n**Incoming engineer misses a critical issue because the handoff document was incomplete.**\nUse the outgoing checklist as a gate: do not mark handoff complete until every section has at least one entry (or an explicit \"none\"). Make incomplete handoffs a blameless postmortem action item.\n\n**A 30-minute sync call is not possible due to timezone gaps.**\nFall back to the async quick handoff template (Template 2). Supplement with a short Loom or voice memo walking through the watch list. Ensure the incoming engineer has a direct contact method if they have follow-up questions.\n\n**The incoming engineer inherits a mid-incident and is immediately overwhelmed.**\nUse the incident handoff template (Template 3) specifically. The outgoing engineer should remain available on Slack for 15 minutes after handoff, even if off-call, to answer clarifying questions.\n\n**On-call handoff documents are inconsistently formatted across teams.**\nAdopt the shift handoff template organization-wide and store completed handoffs in a shared location (wiki, Notion, Confluence). Link each handoff from the on-call schedule entry in PagerDuty.\n\n**Incoming engineer cannot verify their alerting is working before the outgoing engineer logs off.**\nAdd a standard step: outgoing engineer fires a test alert and confirms incoming engineer receives it in PagerDuty and Slack before ending the overlap window.\n\n## Related Skills\n\n- [incident-classification](..\u002F..\u002Fskills\u002Fincident-classification\u002FSKILL.md) — Classify and prioritize incidents that need to be included in the handoff document\n- [postmortem-facilitation](..\u002F..\u002Fskills\u002Fpostmortem-facilitation\u002FSKILL.md) — Turn resolved incidents from the shift into structured postmortems\n",{"description":7},"main","58843b159d7a4050d6b785a98b908cce505c0b92","agent\u002Fskills\u002Fon-call-handoff-patterns",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 on-call-handoff-patterns",{"tool":38,"command":39},"bunx","bunx skills add Reihantt6\u002Fsns-myagent --skill on-call-handoff-patterns",{"tool":41,"command":42},"pnpm","pnpm dlx skills add Reihantt6\u002Fsns-myagent --skill on-call-handoff-patterns","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FReihantt6\u002Fsns-myagent\u002Fblob\u002Fmain\u002Fagent\u002Fskills\u002Fon-call-handoff-patterns\u002FSKILL.md",true,[46],{"path":47,"resourceType":48,"resourceTypeDesc":49,"sizeBytes":50,"sourceHtmlUrl":51},"references\u002Fdetails.md","REFERENCE","参考文档",6276,"https:\u002F\u002Fgithub.com\u002FReihantt6\u002Fsns-myagent\u002Fblob\u002Fmain\u002Fagent\u002Fskills\u002Fon-call-handoff-patterns\u002Freferences\u002Fdetails.md",[53,60,67,74,81,88],{"skillNo":54,"name":55,"nameZh":6,"description":56,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":57,"categories":58,"keywords":59,"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":61,"name":62,"nameZh":6,"description":63,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":64,"categories":65,"keywords":66,"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":68,"name":69,"nameZh":6,"description":70,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":71,"categories":72,"keywords":73,"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":75,"name":76,"nameZh":6,"description":77,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":78,"categories":79,"keywords":80,"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":82,"name":83,"nameZh":6,"description":84,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":85,"categories":86,"keywords":87,"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":89,"name":90,"nameZh":6,"description":91,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":92,"categories":93,"keywords":94,"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",[],[]]