design-on-call-rotation SKILL.md skillA
design-on-call-rotation from pjt222/agent-almanac is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add pjt222/agent-almanac/design-on-call-rotation@v1.0Pins v1.0 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- pjt222/agent-almanac
- Path
i18n/caveman-lite/skills/design-on-call-rotation/SKILL.md- Versions recorded
- 4
- Latest version
- v1.0, committed Aug 17, 2026
- First version recorded
- Apr 19, 2026
- Size
- 11,128 bytes
- Repository stars
- 43
- License
- MIT
Design sustainable on-call rotations with balanced schedules, clear escalation policies, fatigue management, and handoff procedures. Minimize burnout while maintaining incident response coverage. Use when setting up on-call for the first time, scaling a team from 2-3 to 5+ engineers, addressing on-call burnout or alert fatigue, improving incident response times, or after a post-mortem identifies handoff issues.
Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.
What the file says
# Design On-Call Rotation Create a sustainable on-call schedule that balances coverage with engineer well-being. ## When to Use - Setting up on-call for the first time - Scaling team from 2-3 to 5+ engineers - Addressing on-call burnout or alert fatigue - Improving incident response times - After post-mortem identifies handoff issues ## Inputs - **Required**: Team size and time zones - **Required**: Service SLA requirements (response time, coverage hours) - **Optional**: Historical incident volume and timing - **Optional**: Budget for on-call compensation - **Optional**: Existing on-call tool (PagerDuty, Opsgenie) ## Procedure ### Step 1: Define Rotation Schedule Choose rotation length based on team size: ```markdown ## Rotation Models ### Weekly Rotation (5+ person team) - **Length**: 7 days (Monday 09:00 to Monday 09:00) - **Pros**: Predictable, easy to plan around - **Cons**: Whole week disrupted if alerts are frequent ### 12-Hour Split (3-4 person team) - **Day shift**: 08:00-20:00 local time - **Night shift**: 20:00-08:00 local time - **Pros**: Shared burden, night coverage paid differently - **Cons**: More handoffs, coordination needed …
Read the whole file at its exact version.
How to install
mdr add pjt222/agent-almanac/design-on-call-rotation@sha256:f5960cad89e8f937The line at the top of this page pins the label v1.0, which is what most people want. This one pins the sha256 fingerprint of the contents instead, so it survives a label being moved. Either way the exact version is written to mdr.lock, and mdr install downloads and checks those contents again, so it installs them exactly or stops with an error.
[](https://markdownregistry.com/a/art_ceuxujhtqpegemvr)
3 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 4 versions of this file, between Apr 19, 2026 and Aug 17, 2026, about one every 40 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| v1.0 latest | 2026-08-17 | a784899 | 11,128 B | A | view · diff |
| v1.0 | 2026-06-05 | 33b561c | 11,099 B | A | view · diff |
| v1.0 | 2026-04-23 | eb36d45 | 11,091 B | A | view · diff |
| v1.0 | 2026-04-19 | e334ebd | 11,146 B | A | view |
Audit of the latest version
- pass: Frontmatter block present
- pass: Frontmatter declares a name
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (11128 bytes)
- pass: No zero-width or bidi control characters
- pass: No instruction hidden inside an HTML comment
- pass: No link to an exfiltration or paste host
- pass: No credential-shaped string
- pass: No instruction to send local credentials anywhere
- pass: No text hidden with inline styles
- pass: No prompt-injection phrasing
- pass: No curl or wget piped into a shell
- pass: No recursive delete of root, home or parent
- pass: No instruction to read or print local credentials
- pass: No base64 blob over 200 characters
- pass: No link to a raw IP address
- pass: No script tag
Source
pjt222/agent-almanac · 43 stars · license MIT · pushed 2026-11-06 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_ceuxujhtqpegemvr GET https://markdownregistry.com/api/v1/resolve?ref=pjt222/agent-almanac/design-on-call-rotation GET https://markdownregistry.com/api/v1/blob/f5960cad89e8f9377ea847f3f07248633da09f2dedd82f1125df3a1eaf0415e3
Your AI assistant does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.
Guides: the SKILL.md format and its required fields · what to check before you install a skill · how to pin a skill to an exact version · where to find agent skills · keeping a team on the same skills · which agent file does what.