Skills on-call-handoff-patterns
📦

on-call-handoff-patterns

Content revision r2 Medium Risk ⚙️ External commands🌐 Network access

改善待命交接

當事件、變更與風險分散各處時，待命輪班會遺失脈絡。此技能提供結構化交接範本、檢查清單與升級處理指引。

Supports: Claude Codex Code(CC)
Maintain this Skill? Claim it 📊 70 Adequate

Install with my Agent

Copy this request to your Agent. It includes the canonical Skill page and manifest.

Agent request
Review the Skillstore skill "on-call-handoff-patterns" from https://skillstore.io/skills/sickn33-on-call-handoff-patterns.md and its manifest at https://skillstore.io/api/skills/sickn33-on-call-handoff-patterns/manifest. Verify the artifact. You may proceed after verification, subject to the environment's own policy.

Your Agent should still show its plan and request any confirmation required by the security policy.

Agent-readable resources

Use these links when an AI agent, crawler, or script needs clean context instead of reading the full page.

Markdown detail GET /skills/sickn33-on-call-handoff-patterns.md Signed manifest GET /api/skills/sickn33-on-call-handoff-patterns/manifest Signed lockfile GET /api/skills/sickn33-on-call-handoff-patterns/lockfile

Test it

Using "on-call-handoff-patterns". 我有一個進行中的付款事件、一項記憶體調查，還有明天的發布。

Expected outcome:

  • 包含嚴重性、影響、緩解措施與負責人的進行中事件摘要。
  • 記憶體調查的關注清單與後續檢查項目。
  • 即將發布的備註，包含監控與升級處理指引。

Using "on-call-handoff-patterns". 我們團隊需要一套適用於每週輪值的可重複交接流程。

Expected outcome:

一套結構化流程，包含 30 分鐘重疊時間、交出與接手責任、必要章節與驗證步驟。

Using "on-call-handoff-patterns". 擴展 pods 後付款錯誤正在改善，但原因仍然未知。

Expected outcome:

一份事件進行中的轉移文件，記錄目前錯誤率、已採取的行動、剩餘假設、下一個決策點與升級聯絡人。

Security Audit

Medium Risk
v5 • 8/4/2026 Open versioned report

All 37 static alerts are false positives caused by Markdown formatting, example links, or ordinary prose. A separate semantic review found one destructive Redis command presented without sufficient execution safeguards.

1
Files scanned
462
Lines analyzed
0
Review items
0
False positives ignored

Confirmed security concerns (1)

Medium
SKILL.md:201-202
Destructive Redis Command Lacks Safeguards
The quick reference presents redis-cli FLUSHDB as an emergency cache-clear command. It deletes the selected Redis database without target, backup, or authorization checks.
FLUSHDB has documented destructive semantics, and the surrounding guidance provides only an emergency-only label rather than execution safeguards.

Risk Factors

⚙️ External commands (21)
SKILL.md:23 SKILL.md:48-59 SKILL.md:59-65 SKILL.md:65-161 SKILL.md:161-191 SKILL.md:191-203 SKILL.md:203-230 SKILL.md:230-234 SKILL.md:234-256 SKILL.md:256-260 SKILL.md:260-311 SKILL.md:311-317 SKILL.md:317-339 SKILL.md:339-345 SKILL.md:345-372 SKILL.md:372-376 SKILL.md:376-395 SKILL.md:395-399 SKILL.md:399-408 SKILL.md:408-414 SKILL.md:414-434
🌐 Network access (13)
SKILL.md:98 SKILL.md:118 SKILL.md:119 SKILL.md:129 SKILL.md:206 SKILL.md:207 SKILL.md:208 SKILL.md:209 SKILL.md:301 SKILL.md:302 SKILL.md:454 SKILL.md:455 SKILL.md:456
Audited by: codex View Audit History →
Share & cite this report

Share the versioned assessment report, neutral badge, embed card, and citations. Skillstore reports evidence without deciding whether this Skill is safe.

Open versioned report
Security Assessment

Copy report link

https://skillstore.io/skills/sickn33-on-call-handoff-patterns/audits/5?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_report

Markdown badge

[![Skillstore security assessment](https://skillstore.io/badges/skills/sickn33-on-call-handoff-patterns/security.svg)](https://skillstore.io/skills/sickn33-on-call-handoff-patterns?utm_source=security_passport_badge)

HTML badge

<a href="https://skillstore.io/skills/sickn33-on-call-handoff-patterns?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/sickn33-on-call-handoff-patterns/security.svg" alt="Skillstore security assessment" loading="lazy"></a>

Embed card

<iframe src="https://skillstore.io/embed/skills/sickn33-on-call-handoff-patterns.html" title="Skillstore Security Assessment" sandbox="allow-popups allow-popups-to-escape-sandbox" loading="lazy" referrerpolicy="no-referrer" width="420" height="180"></iframe>
Academic citations (APA · BibTeX · CFF)

APA citation

sickn33. (2026). on-call-handoff-patterns security audit report (audit version 5) [Author version unspecified]. Skillstore. https://skillstore.io/skills/sickn33-on-call-handoff-patterns/audits/5

BibTeX citation

@techreport{sickn33-sickn33-on-call-handoff-patterns-2026, author = {sickn33}, title = {on-call-handoff-patterns security audit report (audit version 5)}, institution = {Skillstore}, year = {2026}, number = {5}, url = {https://skillstore.io/skills/sickn33-on-call-handoff-patterns/audits/5}, note = {Author version unspecified} }

CITATION.cff

cff-version: 1.2.0 message: "If you use this Skill, cite its author and this versioned security audit report." title: "on-call-handoff-patterns security audit report (audit version 5)" version: "unspecified" type: report authors: - name: "sickn33" date-released: "2026-08-04" url: "https://skillstore.io/skills/sickn33-on-call-handoff-patterns/audits/5" identifiers: - type: other value: "skillstore:sickn33-on-call-handoff-patterns:audit:5" description: "Skillstore immutable audit report identifier"

Compare variants

2 installable variants

Each author remains a separate installable skill. The recommended variant is ranked by Skillstore evidence.

Why this variant is first

Highest Skillstore Score
sickn33 Recommended Current

sickn33-on-call-handoff-patterns

Skillstore Score 70
Evidence Confidence High
Skillstore usage 16
Updated

2026-09-09

wshobson

wshobson-on-call-handoff-patterns

Skillstore Score 38
Evidence Confidence Medium
Skillstore usage 22
Updated

2026-09-09

Skillstore Score

Why this score Evidence Confidence: High
55
Architecture
85
Maintainability
87
Content
69
Community
83
Spec Compliance

What You Can Build

準備輪班交接

建立一份交接內容，記錄事件、調查、近期變更、已知問題與即將發生的事件。

轉移即時事件

在事件期間摘要目前狀態、緩解進度、後續行動、負責人與溝通狀態。

標準化團隊流程

建立可重複執行的交接例行流程，包含重疊時間、檢查清單、升級觸發條件與文件期望。

Try These Prompts

草擬基本交接 
為我的輪班建立一份待命交接。請詢問我進行中事件、持續調查、近期變更、已知問題與即將發生的事件。
建立非同步交接 
將這些筆記轉成給下一位待命工程師的精簡非同步交接：[paste notes]。強調需關注項目與未解問題。
組織事件進行中的轉移 
為此進行中事件建立一份事件中交接：[paste incident details]。包含目前狀態、已採取的行動、後續步驟、負責人與升級路徑。
改善團隊交接流程 
審查目前這個待命交接流程：[paste process]。找出缺口、加入檢查清單、定義時程，並建議升級處理改進方式。

Best Practices

  • 讓交接聚焦於目前風險、近期變更、後續行動與升級路徑。
  • 針對進行中事件或複雜調查，使用簡短的同步檢視。
  • 將佔位連結、聯絡人與服務名稱替換為目前由團隊維護的參考資料。

Avoid

  • 事件進行中時，不要只透過聊天記錄交接。
  • 不要在缺少環境、核准與回復脈絡的情況下包含命令。
  • 不要省略已知問題、失敗的緩解措施或未解問題。

Frequently Asked Questions

此技能可以建立完整的待命交接文件嗎？
可以。它提供輪班摘要、進行中事件、調查、近期變更與升級提醒的範本。
它是否整合 PagerDuty、Slack、Grafana 或工單工具？
不可以。它只提供文件模式與佔位連結。團隊必須加入自己的系統。
它可以在進行中事件期間使用嗎？
可以。它包含事件進行中的交接格式，用於記錄狀態、緩解措施、負責人、後續步驟與溝通狀態。
誰應該使用它？
待命工程師、事件指揮官、SRE 負責人與 DevOps 團隊都可以使用它來減少脈絡遺失。
它會執行操作命令嗎？
不會。此技能僅用於文件。任何命令範例在執行前都需要人工審查。
團隊應如何調整這些範本？
將範例服務、連結、聯絡人、嚴重性標籤與升級路徑替換為團隊核准的參考資料。

Developer Details

Author

sickn33

License

MIT

Skillstore revision

r2

Version notice

The author did not declare a version.

Repository

https://github.com/sickn33/antigravity-awesome-skills/tree/main/skills/on-call-handoff-patterns

Ref

81e05e636292629114b76cbb3922fbe57672fc02

Maintenance freshness

8/5/2026

Usage

8 downloads · 107 views

File structure

📄 SKILL.md