[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7EVWNZ370DG4P8GASH4ZTKJ":3,"skill-same:01M7EVWNZ370DG4P8GASH4ZTKJ":45},{"skillNo":4,"name":5,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":7,"ownerLogin":8,"ownerAvatarUrl":9,"ownerAccountNo":10,"ownerDisplayName":11,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":15,"categories":16,"keywords":17,"publishedAt":18,"linkOnly":19,"markdownContent":20,"markdownBody":21,"frontMatter":22,"refName":23,"commitSha":24,"skillDirectory":25,"forksCount":26,"repositoryHtmlUrl":27,"repositoryHomepageUrl":6,"ownerHtmlUrl":28,"ownerBlogUrl":29,"ownerDescription":6,"updatedAt":30,"install":31,"resources":44},"01M7EVWNZ370DG4P8GASH4ZTKJ","ams-senior-devops",null,"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-senior-devops\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: senior-devops\ndescription: DevOps\u002FSRE perspective: CI\u002FCD design, infrastructure as code, observability, incident response, and reliability trade-offs. Use when building pipelines, managing infrastructure, or improving operational maturity.\ncategory: development\n---\n\n# Senior DevOps Engineer\n\n## Overview\n\nSenior DevOps is **applied reliability**: making shipping fast *and* safe, and making systems\nexplain themselves when they break. This skill captures that practice — pipeline design, immutable\ninfrastructure, observability that actually helps at 3am, and incident response without heroics.\n\nThe through-line: automate the toil, measure what matters, and design for the failure you haven't\nhad yet.\n\n## When to use\n\n- Designing or fixing CI\u002FCD pipelines.\n- Choosing infrastructure approaches (containers, IaC, managed services).\n- Setting up monitoring, alerting, and on-call practices.\n- Responding to or learning from production incidents.\n- Reducing deploy friction, lead time, or change-failure rate.\n\n## Core concepts\n\n- **Everything as code.** Infrastructure, pipeline definitions, dashboards, and alerts live in\n  version control and go through review like application code. Click-ops is unreviewable,\n  unrepeatable, and unauditable.\n- **Immutable artifacts.** Build once, promote the same artifact through environments. Rebuilding\n  per environment means you're testing something different from what you ship.\n- **Progressive delivery.** Small, frequent deploys behind feature flags, canary analysis, and\n  automated rollback. The safest deploy is the one you do ten times a day — practice makes it boring.\n- **The four golden signals.** Latency, traffic, errors, saturation — for every service. Alerts fire\n  on symptoms (user-facing pain) with runbook links, not on every cause (a CPU spike nobody feels\n  is not a 3am page).\n- **SLOs and error budgets.** Define what \"reliable enough\" means numerically, then let the budget\n  arbitrate the ship-vs-harden debate. No budget left? You fix reliability. Budget to spare? Ship.\n- **Blameless postmortems.** Incidents are system failures, not people failures. The output is\n  action items with owners and deadlines — \"be more careful\" is not an action item.\n\n## Practical workflow\n\n1. **Map the path to production.** Commit → build → test → artifact → stage → prod. Every manual\n   step is a candidate for automation; every slow step gets measured.\n2. **Codify infrastructure.** Start with the network and compute baseline in Terraform\u002FPulumi\u002F\n   CloudFormation; application config via environment, never baked into images; secrets via a\n   secret manager, never in repos or env files committed anywhere.\n3. **Build the deployment pipeline:** lint + unit → build immutable image (pinned digests) →\n   integration tests → deploy to staging (production-like data shape) → smoke tests → progressive\n   prod rollout (canary 1% → 25% → 100% with automatic rollback on SLO breach).\n4. **Instrument before you need it.** Structured logs with correlation IDs, RED\u002FUSE metrics per\n   service, distributed traces across boundaries, and dashboards for each service's golden signals.\n5. **Define alerting tiers.** Page (user impact now, actionable, runbook attached) vs ticket\n   (degraded, investigate soon) vs log (informational). Every page must be actionable — if the\n   response is \"wait and see,\" it's not a page.\n6. **Practice incidents.** Game days \u002F fire drills for the scary scenarios; postmortems within 48h\n   of any significant incident; track action items to completion like product work.\n\nPipeline stage checklist:\n\n```text\n[ ] Build is hermetic and reproducible (pinned base images, locked deps)\n[ ] Same artifact promoted across environments (no rebuilds)\n[ ] Secrets injected at runtime from secret manager\n[ ] Rollback is one command \u002F automatic on health-check failure\n[ ] Deploy is progressive (canary or blue\u002Fgreen), not big-bang\n[ ] Post-deploy smoke tests verify user-critical paths\n[ ] Dashboard + alerts exist before first prod traffic\n```\n\n## Common pitfalls\n\n- **Snowflake environments.** \"Works in staging\" means nothing if staging differs from prod.\n  Production-like data volume, config parity, and the same artifact — or your tests are theater.\n- **Alert fatigue.** Paging on CPU thresholds and disk warnings trains on-call to ignore pages.\n  Alert on user-impacting symptoms; tune ruthlessly; every false page is a bug in the alert.\n- **Manual deploys with extra steps.** A wiki page titled \"release process\" with 30 manual steps is\n  not a pipeline. If a human must remember the order, it will eventually go wrong at 2am.\n- **Secrets in repos.** Even private repos leak (contractors, forks, history). Assume any committed\n  secret is compromised: rotate and move to a manager.\n- **No rollback plan.** \"We'll roll forward\" during an outage is optimism, not a plan. Fast,\n  tested rollback beats heroic forward-fixing under pressure.\n- **Monitoring everything, observing nothing.** 500 dashboards nobody opens. Start from questions\n  (\"is checkout healthy?\") and build the minimum telemetry that answers them.\n- **Treating toil as inevitable.** If on-call spends hours on repetitive tasks (log diving,\n  manual scaling, cert renewals), that's engineering work waiting to be automated — budget for it.\n","# Senior DevOps Engineer\n\n## Overview\n\nSenior DevOps is **applied reliability**: making shipping fast *and* safe, and making systems\nexplain themselves when they break. This skill captures that practice — pipeline design, immutable\ninfrastructure, observability that actually helps at 3am, and incident response without heroics.\n\nThe through-line: automate the toil, measure what matters, and design for the failure you haven't\nhad yet.\n\n## When to use\n\n- Designing or fixing CI\u002FCD pipelines.\n- Choosing infrastructure approaches (containers, IaC, managed services).\n- Setting up monitoring, alerting, and on-call practices.\n- Responding to or learning from production incidents.\n- Reducing deploy friction, lead time, or change-failure rate.\n\n## Core concepts\n\n- **Everything as code.** Infrastructure, pipeline definitions, dashboards, and alerts live in\n  version control and go through review like application code. Click-ops is unreviewable,\n  unrepeatable, and unauditable.\n- **Immutable artifacts.** Build once, promote the same artifact through environments. Rebuilding\n  per environment means you're testing something different from what you ship.\n- **Progressive delivery.** Small, frequent deploys behind feature flags, canary analysis, and\n  automated rollback. The safest deploy is the one you do ten times a day — practice makes it boring.\n- **The four golden signals.** Latency, traffic, errors, saturation — for every service. Alerts fire\n  on symptoms (user-facing pain) with runbook links, not on every cause (a CPU spike nobody feels\n  is not a 3am page).\n- **SLOs and error budgets.** Define what \"reliable enough\" means numerically, then let the budget\n  arbitrate the ship-vs-harden debate. No budget left? You fix reliability. Budget to spare? Ship.\n- **Blameless postmortems.** Incidents are system failures, not people failures. The output is\n  action items with owners and deadlines — \"be more careful\" is not an action item.\n\n## Practical workflow\n\n1. **Map the path to production.** Commit → build → test → artifact → stage → prod. Every manual\n   step is a candidate for automation; every slow step gets measured.\n2. **Codify infrastructure.** Start with the network and compute baseline in Terraform\u002FPulumi\u002F\n   CloudFormation; application config via environment, never baked into images; secrets via a\n   secret manager, never in repos or env files committed anywhere.\n3. **Build the deployment pipeline:** lint + unit → build immutable image (pinned digests) →\n   integration tests → deploy to staging (production-like data shape) → smoke tests → progressive\n   prod rollout (canary 1% → 25% → 100% with automatic rollback on SLO breach).\n4. **Instrument before you need it.** Structured logs with correlation IDs, RED\u002FUSE metrics per\n   service, distributed traces across boundaries, and dashboards for each service's golden signals.\n5. **Define alerting tiers.** Page (user impact now, actionable, runbook attached) vs ticket\n   (degraded, investigate soon) vs log (informational). Every page must be actionable — if the\n   response is \"wait and see,\" it's not a page.\n6. **Practice incidents.** Game days \u002F fire drills for the scary scenarios; postmortems within 48h\n   of any significant incident; track action items to completion like product work.\n\nPipeline stage checklist:\n\n```text\n[ ] Build is hermetic and reproducible (pinned base images, locked deps)\n[ ] Same artifact promoted across environments (no rebuilds)\n[ ] Secrets injected at runtime from secret manager\n[ ] Rollback is one command \u002F automatic on health-check failure\n[ ] Deploy is progressive (canary or blue\u002Fgreen), not big-bang\n[ ] Post-deploy smoke tests verify user-critical paths\n[ ] Dashboard + alerts exist before first prod traffic\n```\n\n## Common pitfalls\n\n- **Snowflake environments.** \"Works in staging\" means nothing if staging differs from prod.\n  Production-like data volume, config parity, and the same artifact — or your tests are theater.\n- **Alert fatigue.** Paging on CPU thresholds and disk warnings trains on-call to ignore pages.\n  Alert on user-impacting symptoms; tune ruthlessly; every false page is a bug in the alert.\n- **Manual deploys with extra steps.** A wiki page titled \"release process\" with 30 manual steps is\n  not a pipeline. If a human must remember the order, it will eventually go wrong at 2am.\n- **Secrets in repos.** Even private repos leak (contractors, forks, history). Assume any committed\n  secret is compromised: rotate and move to a manager.\n- **No rollback plan.** \"We'll roll forward\" during an outage is optimism, not a plan. Fast,\n  tested rollback beats heroic forward-fixing under pressure.\n- **Monitoring everything, observing nothing.** 500 dashboards nobody opens. Start from questions\n  (\"is checkout healthy?\") and build the minimum telemetry that answers them.\n- **Treating toil as inevitable.** If on-call spends hours on repetitive tasks (log diving,\n  manual scaling, cert renewals), that's engineering work waiting to be automated — budget for it.\n",{},"main","af388a77c2fe5e0b4fd879cca4300a0ffa9a6579","skills\u002Fams-senior-devops",1,"https:\u002F\u002Fgithub.com\u002FTanNhatCMS\u002Fjarvis","https:\u002F\u002Fgithub.com\u002FTanNhatCMS","https:\u002F\u002Fmrkiet.name.vn","2026-11-07 14:23:08",{"source":7,"skillName":5,"commands":32,"prompt":42,"zipAvailable":43},[33,36,39],{"tool":34,"command":35},"npx","npx skills add TanNhatCMS\u002Fjarvis --skill ams-senior-devops",{"tool":37,"command":38},"bunx","bunx skills add TanNhatCMS\u002Fjarvis --skill ams-senior-devops",{"tool":40,"command":41},"pnpm","pnpm dlx skills add TanNhatCMS\u002Fjarvis --skill ams-senior-devops","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FTanNhatCMS\u002Fjarvis\u002Fblob\u002Fmain\u002Fskills\u002Fams-senior-devops\u002FSKILL.md",true,[],[46,53,61,68,75,82],{"skillNo":47,"name":48,"nameZh":6,"description":49,"descriptionZh":6,"repositoryFullName":7,"ownerLogin":8,"ownerAvatarUrl":9,"ownerAccountNo":10,"ownerDisplayName":11,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":50,"categories":51,"keywords":52,"publishedAt":18},"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":54,"name":55,"nameZh":6,"description":56,"descriptionZh":6,"repositoryFullName":7,"ownerLogin":8,"ownerAvatarUrl":9,"ownerAccountNo":10,"ownerDisplayName":11,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":57,"sourceHtmlUrl":58,"categories":59,"keywords":60,"publishedAt":18},"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":62,"name":63,"nameZh":6,"description":64,"descriptionZh":6,"repositoryFullName":7,"ownerLogin":8,"ownerAvatarUrl":9,"ownerAccountNo":10,"ownerDisplayName":11,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":65,"categories":66,"keywords":67,"publishedAt":18},"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":69,"name":70,"nameZh":6,"description":71,"descriptionZh":6,"repositoryFullName":7,"ownerLogin":8,"ownerAvatarUrl":9,"ownerAccountNo":10,"ownerDisplayName":11,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":72,"categories":73,"keywords":74,"publishedAt":18},"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":76,"name":77,"nameZh":6,"description":78,"descriptionZh":6,"repositoryFullName":7,"ownerLogin":8,"ownerAvatarUrl":9,"ownerAccountNo":10,"ownerDisplayName":11,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":79,"categories":80,"keywords":81,"publishedAt":18},"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":83,"name":84,"nameZh":6,"description":85,"descriptionZh":6,"repositoryFullName":7,"ownerLogin":8,"ownerAvatarUrl":9,"ownerAccountNo":10,"ownerDisplayName":11,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":86,"categories":87,"keywords":88,"publishedAt":18},"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",[],[]]