[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7EV6VM2PJSCM8X7AGGTEPHZ":3,"skill-same:01M7EV6VM2PJSCM8X7AGGTEPHZ":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},"01M7EV6VM2PJSCM8X7AGGTEPHZ","opsgenie-pro",null,"Run Opsgenie for alerting and on-call — integrations, routing rules, schedules, and incident collaboration.","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-opsgenie-pro\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: opsgenie-pro\ndescription: Run Opsgenie for alerting and on-call — integrations, routing rules, schedules, and incident collaboration.\ncategory: enterprise-communication\n---\n\n## Overview\n\nOpsgenie (Atlassian's alerting and on-call platform) centralizes alerts and routes them to the right responders. This skill covers operating it effectively: team and schedule setup, integration and routing design, alert policies, incident collaboration, and on-call analytics — as transferable on-call practices with Opsgenie as the reference.\n\n\nOpsgenie is Atlassian's incident response platform: alerting, on-call scheduling, and incident coordination integrated with Jira and the Atlassian suite.\nMastery covers alert routing, escalation design, and the integrations that make Opsgenie the connective tissue of incident response.\n## When to use\n\n- Setting up Opsgenie teams and rotations\n- Designing alert routing rules\n- Integrating monitoring tools\n- Reducing alert noise\n- Running incidents with responder collaboration\n- Measuring on-call load\n\n- Setting up on-call rotations in Opsgenie\n- Routing alerts from monitoring tools\n- Coordinating incident response with Jira\n- Reducing alert noise and fatigue\n## Core concepts\n\n**Teams and ownership.** Teams own services and their alerts: define team membership, roles, and responsibilities clearly. Routing rules direct alerts to teams based on source, tags, or content. Clear ownership eliminates \"not my alert\" delays.\n\n**Schedules and rotations.** Rotation types (weekly, daily, custom), participants, time restrictions, and overrides. Forwarding rules for personal preferences. Keep schedules accurate — stale rotations page the wrong people at 3am.\n\n**Integrations.** Monitoring, ticketing (Jira), chat (Slack\u002FTeams), and custom webhooks. Per integration: field mapping, alert creation rules, and bidirectional sync (acknowledge in chat → reflected in Opsgenie). Test integrations before relying on them.\n\n**Alert policies.** Routing, suppression (duplicate\u002Fflapping), auto-close on recovery, and delay policies. Policies are the noise filter — invest in them. Untagged, unfiltered alert streams destroy on-call morale.\n\n**Escalations.** Rules per team: escalate if unacknowledged in X minutes, escalate to next rotation layer, then to managers. Schedule-based vs. rule-based escalations. Escalation chains should be short and tested — long chains delay response.\n\n**Incident collaboration.** Incident creation from alerts, responder management, timeline notes, conference bridges, stakeholder updates, and post-incident reports. Centralized incident context prevents scattered war rooms.\n\n\n**Alert lifecycle.** Created → acknowledged → closed (or snoozed\u002Fescalated).\nEvery alert needs: clear description, priority, source, tags, and runbook link.\nAlerts without runbooks are just noise with extra steps — link or do not alert.\n**Routing rules.** Match alerts to teams by: source system, tags, time of day, and alert content.\nRoute precisely — misrouted alerts delay response and erode trust in the system.\nReview routing monthly; team structures change faster than routing rules.\n**Escalation policies.** Time-based escalation chains with round-robin or load-balanced routing.\nDesign for the 3am scenario: the right person paged, with context, within minutes.\nTest escalations quarterly — policies rot as teams change.\n**Jira integration.** Auto-create Jira issues from alerts, link incidents to postmortems, and track follow-up actions.\nThe alert-to-action loop closes in Jira — integration turns incidents into improvements.\n## Practical workflow\n\n1. **Structure teams.** Define teams aligned to service ownership, set up memberships and roles, and document who's responsible for what.\n2. **Build schedules.** Rotations per team, overrides process, forwarding rules, and coverage verification (no gaps, fair distribution).\n3. **Integrate sources.** Connect monitoring with alert-creation rules: severity mapping, tagging for routing, and suppression of known noise. Validate with test alerts.\n4. **Design policies.** Routing rules (source\u002Ftag → team), escalation rules (timeouts per layer), suppression (dups, flapping), and auto-close conditions. Document the policy logic.\n5. **Run incidents.** Alert → acknowledge → collaborate (timeline, bridge, responders) → resolve → post-incident review. Use the timeline religiously — it's the record.\n6. **Analyze and tune.** Alert volume per team\u002Fperson, ack\u002Fresolve times, after-hours load, escalation frequency. Monthly tuning: suppress noise, fix flaky alerts, rebalance load.\n\n**Alert policy checklist:** routing correct? → severity mapped? → duplicates suppressed? → flapping handled? → auto-close configured? → escalation tested? → runbook linked?\n\n\n**Setup sequence:** define teams and rotations → configure integrations (monitoring sources) → build routing rules → design escalation policies → create alert templates → link runbooks → test end-to-end (fire test alerts) → train teams → go live with hypercare.\nTest with real pages before going live — untested paging fails when it matters.\n**Noise reduction program:** weekly alert review (actionable? correctly routed? timely?) → tune thresholds → deduplicate and correlate → suppress known-noise → track alerts per person per week.\nTarget: every alert deserves a human. Anything less is noise to eliminate.\n## Common pitfalls\n\n- **Unfiltered integrations.** Every monitoring blip becomes an alert. Filter at the integration level.\n- **Vague ownership.** Alerts routed to \"the team\" with no clear responder. Named rotations, always.\n- **Stale schedules.** People paged who left the team. Audit membership quarterly.\n- **No suppression.** Duplicate storms during outages. Dedup and group aggressively.\n- **Escalation theater.** Chains so long nobody responds in time. Short, tested chains.\n- **Ignoring analytics.** Alert volume creeping up unnoticed. Review monthly; tune continuously.\n- **Skipping post-incidents.** Resolving without learning. Reports with action items for significant incidents.\n- **Alert fatigue.** Hundreds of unactionable alerts. Engineers stop responding — then miss the real one. Ruthless tuning is safety work.\n- **No rotation hygiene.** Stale rotations paging people who left. Audit rotations monthly; tie to HRIS if possible.\n- **Missing runbooks.** Alerts without response procedures. Every alert links to a runbook or gets deleted — no exceptions.\n- **Overlapping tools.** Opsgenie + PagerDuty + Slack alerts creating confusion. One alerting system of record; others notify, not page.\n","## Overview\n\nOpsgenie (Atlassian's alerting and on-call platform) centralizes alerts and routes them to the right responders. This skill covers operating it effectively: team and schedule setup, integration and routing design, alert policies, incident collaboration, and on-call analytics — as transferable on-call practices with Opsgenie as the reference.\n\n\nOpsgenie is Atlassian's incident response platform: alerting, on-call scheduling, and incident coordination integrated with Jira and the Atlassian suite.\nMastery covers alert routing, escalation design, and the integrations that make Opsgenie the connective tissue of incident response.\n## When to use\n\n- Setting up Opsgenie teams and rotations\n- Designing alert routing rules\n- Integrating monitoring tools\n- Reducing alert noise\n- Running incidents with responder collaboration\n- Measuring on-call load\n\n- Setting up on-call rotations in Opsgenie\n- Routing alerts from monitoring tools\n- Coordinating incident response with Jira\n- Reducing alert noise and fatigue\n## Core concepts\n\n**Teams and ownership.** Teams own services and their alerts: define team membership, roles, and responsibilities clearly. Routing rules direct alerts to teams based on source, tags, or content. Clear ownership eliminates \"not my alert\" delays.\n\n**Schedules and rotations.** Rotation types (weekly, daily, custom), participants, time restrictions, and overrides. Forwarding rules for personal preferences. Keep schedules accurate — stale rotations page the wrong people at 3am.\n\n**Integrations.** Monitoring, ticketing (Jira), chat (Slack\u002FTeams), and custom webhooks. Per integration: field mapping, alert creation rules, and bidirectional sync (acknowledge in chat → reflected in Opsgenie). Test integrations before relying on them.\n\n**Alert policies.** Routing, suppression (duplicate\u002Fflapping), auto-close on recovery, and delay policies. Policies are the noise filter — invest in them. Untagged, unfiltered alert streams destroy on-call morale.\n\n**Escalations.** Rules per team: escalate if unacknowledged in X minutes, escalate to next rotation layer, then to managers. Schedule-based vs. rule-based escalations. Escalation chains should be short and tested — long chains delay response.\n\n**Incident collaboration.** Incident creation from alerts, responder management, timeline notes, conference bridges, stakeholder updates, and post-incident reports. Centralized incident context prevents scattered war rooms.\n\n\n**Alert lifecycle.** Created → acknowledged → closed (or snoozed\u002Fescalated).\nEvery alert needs: clear description, priority, source, tags, and runbook link.\nAlerts without runbooks are just noise with extra steps — link or do not alert.\n**Routing rules.** Match alerts to teams by: source system, tags, time of day, and alert content.\nRoute precisely — misrouted alerts delay response and erode trust in the system.\nReview routing monthly; team structures change faster than routing rules.\n**Escalation policies.** Time-based escalation chains with round-robin or load-balanced routing.\nDesign for the 3am scenario: the right person paged, with context, within minutes.\nTest escalations quarterly — policies rot as teams change.\n**Jira integration.** Auto-create Jira issues from alerts, link incidents to postmortems, and track follow-up actions.\nThe alert-to-action loop closes in Jira — integration turns incidents into improvements.\n## Practical workflow\n\n1. **Structure teams.** Define teams aligned to service ownership, set up memberships and roles, and document who's responsible for what.\n2. **Build schedules.** Rotations per team, overrides process, forwarding rules, and coverage verification (no gaps, fair distribution).\n3. **Integrate sources.** Connect monitoring with alert-creation rules: severity mapping, tagging for routing, and suppression of known noise. Validate with test alerts.\n4. **Design policies.** Routing rules (source\u002Ftag → team), escalation rules (timeouts per layer), suppression (dups, flapping), and auto-close conditions. Document the policy logic.\n5. **Run incidents.** Alert → acknowledge → collaborate (timeline, bridge, responders) → resolve → post-incident review. Use the timeline religiously — it's the record.\n6. **Analyze and tune.** Alert volume per team\u002Fperson, ack\u002Fresolve times, after-hours load, escalation frequency. Monthly tuning: suppress noise, fix flaky alerts, rebalance load.\n\n**Alert policy checklist:** routing correct? → severity mapped? → duplicates suppressed? → flapping handled? → auto-close configured? → escalation tested? → runbook linked?\n\n\n**Setup sequence:** define teams and rotations → configure integrations (monitoring sources) → build routing rules → design escalation policies → create alert templates → link runbooks → test end-to-end (fire test alerts) → train teams → go live with hypercare.\nTest with real pages before going live — untested paging fails when it matters.\n**Noise reduction program:** weekly alert review (actionable? correctly routed? timely?) → tune thresholds → deduplicate and correlate → suppress known-noise → track alerts per person per week.\nTarget: every alert deserves a human. Anything less is noise to eliminate.\n## Common pitfalls\n\n- **Unfiltered integrations.** Every monitoring blip becomes an alert. Filter at the integration level.\n- **Vague ownership.** Alerts routed to \"the team\" with no clear responder. Named rotations, always.\n- **Stale schedules.** People paged who left the team. Audit membership quarterly.\n- **No suppression.** Duplicate storms during outages. Dedup and group aggressively.\n- **Escalation theater.** Chains so long nobody responds in time. Short, tested chains.\n- **Ignoring analytics.** Alert volume creeping up unnoticed. Review monthly; tune continuously.\n- **Skipping post-incidents.** Resolving without learning. Reports with action items for significant incidents.\n- **Alert fatigue.** Hundreds of unactionable alerts. Engineers stop responding — then miss the real one. Ruthless tuning is safety work.\n- **No rotation hygiene.** Stale rotations paging people who left. Audit rotations monthly; tie to HRIS if possible.\n- **Missing runbooks.** Alerts without response procedures. Every alert links to a runbook or gets deleted — no exceptions.\n- **Overlapping tools.** Opsgenie + PagerDuty + Slack alerts creating confusion. One alerting system of record; others notify, not page.\n",{"name":5,"category":24,"description":7},"enterprise-communication","main","af388a77c2fe5e0b4fd879cca4300a0ffa9a6579","skills\u002Fams-opsgenie-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 opsgenie-pro",{"tool":39,"command":40},"bunx","bunx skills add TanNhatCMS\u002Fjarvis --skill opsgenie-pro",{"tool":42,"command":43},"pnpm","pnpm dlx skills add TanNhatCMS\u002Fjarvis --skill opsgenie-pro","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FTanNhatCMS\u002Fjarvis\u002Fblob\u002Fmain\u002Fskills\u002Fams-opsgenie-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",[],[]]