[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7EV83AFTKZ1Y4PQ2JSV6J7Z":3,"skill-same:01M7EV83AFTKZ1Y4PQ2JSV6J7Z":47},{"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":25,"commitSha":26,"skillDirectory":27,"forksCount":28,"repositoryHtmlUrl":29,"repositoryHomepageUrl":6,"ownerHtmlUrl":30,"ownerBlogUrl":31,"ownerDescription":6,"updatedAt":32,"install":33,"resources":46},"01M7EV83AFTKZ1Y4PQ2JSV6J7Z","pagerduty-pro",null,"Operate PagerDuty effectively — on-call schedules, escalation policies, incident workflows, and alert hygiene.","TanNhatCMS\u002Fjarvis","TanNhatCMS","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F113796420?v=4","01M753MV17KG5CD3152G3WQEQY","KietNT","01M7EKEDYVYQ6PWVJJMZ911VMX",0,"MIT","https:\u002F\u002Fgithub.com\u002FTanNhatCMS\u002Fjarvis\u002Fblob\u002Fmain\u002Fskills\u002Fams-pagerduty-pro\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: pagerduty-pro\ndescription: Operate PagerDuty effectively — on-call schedules, escalation policies, incident workflows, and alert hygiene.\ncategory: enterprise-communication\n---\n\n## Overview\n\nPagerDuty (the category-defining on-call platform) routes alerts to the right humans fast. This skill covers operating it well: service and schedule design, escalation policies, incident response workflows, alert hygiene, and analytics — written as transferable on-call platform practices with PagerDuty as the reference implementation.\n\n\nPagerDuty is the industry-standard incident management platform: on-call scheduling, alert routing, incident orchestration, and response analytics.\nMastery covers the full incident lifecycle — from alert ingestion to postmortem — and the cultural practices (blameless retrospectives, sustainable on-call) that make tooling effective.\n## When to use\n\n- Setting up on-call rotations\n- Designing escalation policies\n- Reducing alert fatigue\n- Running incidents in PagerDuty\n- Analyzing on-call health metrics\n- Integrating monitoring with paging\n\n- Building incident response from scratch\n- Managing on-call at scale across teams\n- Integrating alerting with ChatOps workflows\n- Measuring and improving incident metrics (MTTR, MTBF)\n## Core concepts\n\n**Services.** Model each service (or component) with: owning team, integrations (monitoring sources), escalation policy, alert grouping, and response plays. Good service boundaries (aligned to team ownership) make routing obvious; vague services route to everyone.\n\n**Schedules and rotations.** Follow-the-sun for global teams, weekly rotations (the common sweet spot), overrides for swaps\u002Ftime-off, and handoff hygiene (pending alerts briefed, not just \"you're on\"). Fair rotations sustain teams; unfair ones burn people out.\n\n**Escalation policies.** Layered: primary on-call (5–15 min) → secondary\u002Fteam lead (15–30 min) → manager → broader. Timeouts per layer, urgency levels (high = page now, low = notify only), and rules per service. Escalation is for unacknowledged alerts, not for FYIs.\n\n**Alert grouping and suppression.** Group related alerts into one incident (per service, time-windowed), suppress flapping, and auto-resolve on recovery signals. Raw alert-to-page pipelines create fatigue; intelligent grouping preserves sanity.\n\n**Incident workflows.** Declare → page → acknowledge → triage → mitigate → resolve → postmortem. Status updates, stakeholder notifications, conference bridges, and response plays (runbook links attached to incidents). Practice via game days.\n\n**Analytics.** MTTA (mean time to acknowledge), MTTR (mean time to resolve), alert volume per service\u002Fperson, after-hours page frequency, and escalation rates. These metrics diagnose on-call health — rising MTTA signals fatigue or misrouting.\n\n\n**Service-oriented alerting.** Alerts route to services, services map to teams, teams own runbooks.\nService definitions are the foundation — vague ownership means alerts go nowhere.\nMap every production component to a service with a named owner; review quarterly.\n**Incident roles.** Commander (decision authority), scribe (timeline), communications (stakeholder updates), subject-matter experts (fixers).\nAssign roles at incident start, not mid-crisis.\nSmall incidents need commander + fixers; large ones need the full structure.\n**Response plays.** Pre-built workflows per incident type: who gets paged, which runbooks run, which stakeholders notify.\nPlays turn chaos into procedure — build them from past incidents.\nReview plays after every major incident; they encode organizational learning.\n**Analytics.** MTTA (acknowledge), MTTR (resolve), alert volume per team, escalations, and postmortem action completion.\nTrends matter more than absolutes — improving MTTR 20% quarterly compounds.\nShare metrics transparently; they drive investment in reliability.\n## Practical workflow\n\n1. **Model services.** Inventory services, assign owners, define escalation policies per service, and set urgency rules. Align with actual team boundaries.\n2. **Build schedules.** Rotation length (weekly typical), layering (primary\u002Fsecondary), overrides process, follow-the-sun if global, and fair distribution tracking.\n3. **Integrate monitoring.** Connect alert sources with: severity mapping (not everything pages), grouping rules, suppression for known noise, and enrichment (runbook links, dashboards, recent deploys).\n4. **Define incident process.** Roles (commander, comms, scribe), communication channels, stakeholder update cadence, and postmortem requirements. Document the runbook; train the team.\n5. **Fight fatigue.** Weekly: review alert volume per person, tune noisy alerts (fix or suppress), adjust thresholds, and ensure after-hours pages are truly page-worthy. Alert fatigue is a safety issue.\n6. **Review metrics.** Monthly on-call health review: MTTA\u002FMTTR trends, volume, after-hours burden, escalation patterns, and action items. Quarterly: schedule fairness and process improvements.\n\n**On-call health dashboard:** alerts per person per week → % after-hours → MTTA\u002FMTTR trends → escalations → unresolved postmortems → upcoming schedule gaps.\n\n\n**Implementation roadmap:** inventory services and owners → configure integrations (monitoring → PagerDuty) → build escalation policies → create response plays for top 5 incident types → train teams (game days) → go live → weekly alert review → monthly incident metrics review.\nPhase the rollout — big-bang incident tooling migrations fail under pressure.\n**Postmortem process:** blameless template (timeline, impact, root causes, action items) → scheduled within 48h → action items tracked to completion → shared org-wide for SEV-1\u002F2.\nPostmortems without completed actions are theater — track completion ruthlessly.\n## Common pitfalls\n\n- **Everything pages.** No severity discipline. Only customer-impacting, actionable issues page; the rest notify.\n- **No grouping.** 50 pages for one outage. Group by service and time window.\n- **Unfair rotations.** Same people always on-call. Track and balance; burnout is a retention risk.\n- **Stale schedules.** Overrides not recorded, gaps in coverage. Single source of truth, always current.\n- **Missing runbooks.** Paged with no guidance. Attach runbooks to services; keep them current.\n- **Skipping postmortems.** Incidents resolved, nothing learned. Blameless reviews with action items, every significant incident.\n- **Ignoring analytics.** Never reviewing MTTA\u002FMTTR\u002Fvolume. Metrics reveal fatigue before resignations do.\n- **Paging without context.** Alerts lacking runbooks, dashboards, or recent-change info. Enrich alerts at ingestion — context determines response speed.\n- **Hero culture.** Rewarding all-night firefighting over preventing fires. Celebrate reliability improvements, not heroic recoveries.\n- **Stale escalation policies.** Policies referencing reorganized teams. Quarterly audits; tie to org charts where possible.\n- **Skipping postmortems for 'small' incidents.** Patterns hide in small incidents. Lightweight postmortems for SEV-3s catch systemic issues early.\n","## Overview\n\nPagerDuty (the category-defining on-call platform) routes alerts to the right humans fast. This skill covers operating it well: service and schedule design, escalation policies, incident response workflows, alert hygiene, and analytics — written as transferable on-call platform practices with PagerDuty as the reference implementation.\n\n\nPagerDuty is the industry-standard incident management platform: on-call scheduling, alert routing, incident orchestration, and response analytics.\nMastery covers the full incident lifecycle — from alert ingestion to postmortem — and the cultural practices (blameless retrospectives, sustainable on-call) that make tooling effective.\n## When to use\n\n- Setting up on-call rotations\n- Designing escalation policies\n- Reducing alert fatigue\n- Running incidents in PagerDuty\n- Analyzing on-call health metrics\n- Integrating monitoring with paging\n\n- Building incident response from scratch\n- Managing on-call at scale across teams\n- Integrating alerting with ChatOps workflows\n- Measuring and improving incident metrics (MTTR, MTBF)\n## Core concepts\n\n**Services.** Model each service (or component) with: owning team, integrations (monitoring sources), escalation policy, alert grouping, and response plays. Good service boundaries (aligned to team ownership) make routing obvious; vague services route to everyone.\n\n**Schedules and rotations.** Follow-the-sun for global teams, weekly rotations (the common sweet spot), overrides for swaps\u002Ftime-off, and handoff hygiene (pending alerts briefed, not just \"you're on\"). Fair rotations sustain teams; unfair ones burn people out.\n\n**Escalation policies.** Layered: primary on-call (5–15 min) → secondary\u002Fteam lead (15–30 min) → manager → broader. Timeouts per layer, urgency levels (high = page now, low = notify only), and rules per service. Escalation is for unacknowledged alerts, not for FYIs.\n\n**Alert grouping and suppression.** Group related alerts into one incident (per service, time-windowed), suppress flapping, and auto-resolve on recovery signals. Raw alert-to-page pipelines create fatigue; intelligent grouping preserves sanity.\n\n**Incident workflows.** Declare → page → acknowledge → triage → mitigate → resolve → postmortem. Status updates, stakeholder notifications, conference bridges, and response plays (runbook links attached to incidents). Practice via game days.\n\n**Analytics.** MTTA (mean time to acknowledge), MTTR (mean time to resolve), alert volume per service\u002Fperson, after-hours page frequency, and escalation rates. These metrics diagnose on-call health — rising MTTA signals fatigue or misrouting.\n\n\n**Service-oriented alerting.** Alerts route to services, services map to teams, teams own runbooks.\nService definitions are the foundation — vague ownership means alerts go nowhere.\nMap every production component to a service with a named owner; review quarterly.\n**Incident roles.** Commander (decision authority), scribe (timeline), communications (stakeholder updates), subject-matter experts (fixers).\nAssign roles at incident start, not mid-crisis.\nSmall incidents need commander + fixers; large ones need the full structure.\n**Response plays.** Pre-built workflows per incident type: who gets paged, which runbooks run, which stakeholders notify.\nPlays turn chaos into procedure — build them from past incidents.\nReview plays after every major incident; they encode organizational learning.\n**Analytics.** MTTA (acknowledge), MTTR (resolve), alert volume per team, escalations, and postmortem action completion.\nTrends matter more than absolutes — improving MTTR 20% quarterly compounds.\nShare metrics transparently; they drive investment in reliability.\n## Practical workflow\n\n1. **Model services.** Inventory services, assign owners, define escalation policies per service, and set urgency rules. Align with actual team boundaries.\n2. **Build schedules.** Rotation length (weekly typical), layering (primary\u002Fsecondary), overrides process, follow-the-sun if global, and fair distribution tracking.\n3. **Integrate monitoring.** Connect alert sources with: severity mapping (not everything pages), grouping rules, suppression for known noise, and enrichment (runbook links, dashboards, recent deploys).\n4. **Define incident process.** Roles (commander, comms, scribe), communication channels, stakeholder update cadence, and postmortem requirements. Document the runbook; train the team.\n5. **Fight fatigue.** Weekly: review alert volume per person, tune noisy alerts (fix or suppress), adjust thresholds, and ensure after-hours pages are truly page-worthy. Alert fatigue is a safety issue.\n6. **Review metrics.** Monthly on-call health review: MTTA\u002FMTTR trends, volume, after-hours burden, escalation patterns, and action items. Quarterly: schedule fairness and process improvements.\n\n**On-call health dashboard:** alerts per person per week → % after-hours → MTTA\u002FMTTR trends → escalations → unresolved postmortems → upcoming schedule gaps.\n\n\n**Implementation roadmap:** inventory services and owners → configure integrations (monitoring → PagerDuty) → build escalation policies → create response plays for top 5 incident types → train teams (game days) → go live → weekly alert review → monthly incident metrics review.\nPhase the rollout — big-bang incident tooling migrations fail under pressure.\n**Postmortem process:** blameless template (timeline, impact, root causes, action items) → scheduled within 48h → action items tracked to completion → shared org-wide for SEV-1\u002F2.\nPostmortems without completed actions are theater — track completion ruthlessly.\n## Common pitfalls\n\n- **Everything pages.** No severity discipline. Only customer-impacting, actionable issues page; the rest notify.\n- **No grouping.** 50 pages for one outage. Group by service and time window.\n- **Unfair rotations.** Same people always on-call. Track and balance; burnout is a retention risk.\n- **Stale schedules.** Overrides not recorded, gaps in coverage. Single source of truth, always current.\n- **Missing runbooks.** Paged with no guidance. Attach runbooks to services; keep them current.\n- **Skipping postmortems.** Incidents resolved, nothing learned. Blameless reviews with action items, every significant incident.\n- **Ignoring analytics.** Never reviewing MTTA\u002FMTTR\u002Fvolume. Metrics reveal fatigue before resignations do.\n- **Paging without context.** Alerts lacking runbooks, dashboards, or recent-change info. Enrich alerts at ingestion — context determines response speed.\n- **Hero culture.** Rewarding all-night firefighting over preventing fires. Celebrate reliability improvements, not heroic recoveries.\n- **Stale escalation policies.** Policies referencing reorganized teams. Quarterly audits; tie to org charts where possible.\n- **Skipping postmortems for 'small' incidents.** Patterns hide in small incidents. Lightweight postmortems for SEV-3s catch systemic issues early.\n",{"name":5,"category":24,"description":7},"enterprise-communication","main","af388a77c2fe5e0b4fd879cca4300a0ffa9a6579","skills\u002Fams-pagerduty-pro",1,"https:\u002F\u002Fgithub.com\u002FTanNhatCMS\u002Fjarvis","https:\u002F\u002Fgithub.com\u002FTanNhatCMS","https:\u002F\u002Fmrkiet.name.vn","2026-11-07 14:23:08",{"source":8,"skillName":5,"commands":34,"prompt":44,"zipAvailable":45},[35,38,41],{"tool":36,"command":37},"npx","npx skills add TanNhatCMS\u002Fjarvis --skill pagerduty-pro",{"tool":39,"command":40},"bunx","bunx skills add TanNhatCMS\u002Fjarvis --skill pagerduty-pro",{"tool":42,"command":43},"pnpm","pnpm dlx skills add TanNhatCMS\u002Fjarvis --skill pagerduty-pro","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FTanNhatCMS\u002Fjarvis\u002Fblob\u002Fmain\u002Fskills\u002Fams-pagerduty-pro\u002FSKILL.md",true,[],[48,55,63,70,77,84],{"skillNo":49,"name":50,"nameZh":6,"description":51,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":52,"categories":53,"keywords":54,"publishedAt":19},"01M7EWYJR0J8DARY7E59Z6Y9MV","web-scrape","Turn web pages into LLM-ready markdown via the Firecrawl API (renders JS, anti-bot handling). Use when browser_open\u002Ffetch fails on JS-heavy pages, or when you need clean markdown\u002Fstructured extraction from a site. Requires FIRECRAWL_API_KEY.","https:\u002F\u002Fgithub.com\u002FTanNhatCMS\u002Fjarvis\u002Fblob\u002Fmain\u002Fskills\u002Fweb-scrape\u002FSKILL.md",[],[],{"skillNo":56,"name":57,"nameZh":6,"description":58,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":59,"sourceHtmlUrl":60,"categories":61,"keywords":62,"publishedAt":19},"01M7EWYBN5P6F2AJG3FR24T9BP","design-taste-frontend","tasteskill v2, the anti-slop frontend skill. Art direction for websites, distilled from a study of 247 curated gallery sites (One Page Love, Awwwards Sites of the Day). Deals researched directions (idea, composition, type, palette, photographs, section blueprints) from a library, enforces a strict no-slop house style with a real-browser inspector, and runs a look-and-fix loop on screenshots. Use this whenever you build, design, redesign, restyle, polish or review a landing page, marketing site, portfolio, product page, one-pager, hero or any public-facing web page, in any stack (HTML\u002FCSS, React, Next.js, Vue, Svelte, Astro, Tailwind) — also when the user says a page looks generic, templated, \"AI-made\", sloppy, or asks to make it look designed, premium, award-level or less like every other site. Not for dashboards or app screens.","https:\u002F\u002Fgithub.com\u002FTanNhatCMS\u002Fjarvis\u002Fblob\u002Fmain\u002Fskills\u002Ftaste-design\u002FLICENSE","https:\u002F\u002Fgithub.com\u002FTanNhatCMS\u002Fjarvis\u002Fblob\u002Fmain\u002Fskills\u002Ftaste-design\u002FSKILL.md",[],[],{"skillNo":64,"name":65,"nameZh":6,"description":66,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":67,"categories":68,"keywords":69,"publishedAt":19},"01M7EWY8FQFNQ2GB7NZZWGSSDX","test-driven-development","Use when implementing any feature or bugfix, before writing implementation code","https:\u002F\u002Fgithub.com\u002FTanNhatCMS\u002Fjarvis\u002Fblob\u002Fmain\u002Fskills\u002Fsuperpowers-tdd\u002FSKILL.md",[],[],{"skillNo":71,"name":72,"nameZh":6,"description":73,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":74,"categories":75,"keywords":76,"publishedAt":19},"01M7EWY5SHBFRH1HDHVWM9K7TV","systematic-debugging","Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes","https:\u002F\u002Fgithub.com\u002FTanNhatCMS\u002Fjarvis\u002Fblob\u002Fmain\u002Fskills\u002Fsuperpowers-debugging\u002FSKILL.md",[],[],{"skillNo":78,"name":79,"nameZh":6,"description":80,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":81,"categories":82,"keywords":83,"publishedAt":19},"01M7EWY3NM0Z0JAKS7HDZ24K66","requesting-code-review","Use when completing tasks, implementing major features, or before merging to verify work meets requirements","https:\u002F\u002Fgithub.com\u002FTanNhatCMS\u002Fjarvis\u002Fblob\u002Fmain\u002Fskills\u002Fsuperpowers-code-review\u002FSKILL.md",[],[],{"skillNo":85,"name":86,"nameZh":6,"description":87,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":88,"categories":89,"keywords":90,"publishedAt":19},"01M7EWY0WRMWX4M9ZFY0WKC593","brainstorming","You MUST use this before any creative work - creating features, building components, adding functionality, modifying behavior, or planning anything new, in software or out of it (a talk, a business, a renovation).","https:\u002F\u002Fgithub.com\u002FTanNhatCMS\u002Fjarvis\u002Fblob\u002Fmain\u002Fskills\u002Fsuperpowers-brainstorming\u002FSKILL.md",[],[]]