[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7EMPRWN031WBSYTHVNJXP1N":3,"skill-same:01M7EMPRWN031WBSYTHVNJXP1N":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},"01M7EMPRWN031WBSYTHVNJXP1N","cron-monitoring",null,"Monitoring scheduled jobs — heartbeat checks, missed runs, and duration anomalies — platform-agnostic patterns.","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-cron-monitoring\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: cron-monitoring\ndescription: Monitoring scheduled jobs — heartbeat checks, missed runs, and duration anomalies — platform-agnostic patterns.\ncategory: sentry\n---\n\n## Overview\n\nCron jobs fail silently: the scheduler dies, credentials expire, a deploy\nbreaks the script — and nobody notices until the missing report, stale data,\nor lapsed certificate causes real damage. Cron monitoring (heartbeat\u002Fdead-\nman's-switch checks) closes this gap by verifying jobs actually run and\nsucceed on schedule. This skill covers the patterns.\n\n## When to use\n\n- Adding monitoring to existing cron jobs or scheduled tasks\n- Choosing heartbeat vs exit-code vs log-based monitoring\n- Detecting missed runs, late runs, and duration anomalies\n- Monitoring jobs across servers, containers, and serverless\n- Building the \"did the nightly job run?\" dashboard\n\n## Core concepts\n\n**Heartbeat (dead man's switch) monitoring.** The job pings a monitoring\nendpoint at start and on successful completion; the monitor alerts if the\nexpected ping doesn't arrive within the schedule window + grace period.\nThis catches the worst failure mode — the job never running — which\nexit-code monitoring alone misses entirely.\n\n**Three signals per job.** Started on time (schedule adherence), completed\nsuccessfully (exit status \u002F success ping), and duration within norms\n(sudden 10x slowdowns signal trouble even when the job \"succeeds\"). Monitor\nall three; each catches a different failure class.\n\n**Grace periods and expected variance.** Jobs don't run at exactly 02:00:00\n— schedulers queue, machines are busy. Set the expected window generously\n(schedule interval + reasonable grace), and wider for jobs with variable\nduration. Too tight = false alarms; too loose = late detection. Tune from\nobserved history.\n\n**Distinguish \"didn't run\" from \"ran and failed\".** Start ping vs success\nping separation tells you whether the scheduler\u002Fjob never started (infra\nproblem) or started and errored (job problem) — different responders,\ndifferent runbooks.\n\n**Monitor the monitor's coverage.** Keep a registry of all scheduled jobs\nwith their expected schedules; alert on jobs with no monitoring configured.\nThe unmonitored job is the one that will fail silently.\n\n## Practical workflow\n\n1. **Inventory every scheduled job:** what, where it runs, schedule,\n   owner, and what breaks if it silently stops — this registry is the\n   foundation.\n2. **Add heartbeat instrumentation:** ping start\u002Fsuccess (or use the\n   platform's cron-monitoring feature) with the job's identity and run\n   metadata; keep the ping mechanism simple and dependency-free (a failing\n   job should still be able to report failure).\n3. **Configure expectations:** schedule + grace period per job, based on\n   observed run times; alert routing to the job's owner.\n4. **Track duration:** record run times, alert on significant deviation\n   from baseline (2–3x p99), which often precedes outright failure.\n5. **Build the overview:** a single dashboard showing all jobs, last run,\n   status, and next expected run — the \"morning check\" view for on-call.\n6. **Test the alerts:** deliberately break a non-critical job's schedule\n   (or simulate a missed ping) and verify the alert fires and routes\n   correctly — untested monitoring is decoration.\n\n## Common pitfalls\n\n- **Monitoring only failures, not absence** — exit-code alerts catch\n  failures; only heartbeats catch \"never ran\". You need both.\n- **Grace periods too tight** — normal scheduler jitter pages on-call\n  weekly; base windows on measured history.\n- **No job registry** — jobs added without monitoring, discovered only\n  when they fail silently; make monitoring part of the job-creation\n  checklist.\n- **Heartbeat endpoint as a dependency** — if the monitoring endpoint is\n  down, every job \"fails\"; keep pings fire-and-forget and monitor the\n  monitor separately.\n- **Ignoring duration drift** — a job creeping from 5 to 50 minutes is\n  heading for timeout\u002Foverlap failure; trend it.\n- **Alerting to nobody** — cron alerts to an unmonitored email alias;\n  route to the owner with an escalation path like any other alert.\n","## Overview\n\nCron jobs fail silently: the scheduler dies, credentials expire, a deploy\nbreaks the script — and nobody notices until the missing report, stale data,\nor lapsed certificate causes real damage. Cron monitoring (heartbeat\u002Fdead-\nman's-switch checks) closes this gap by verifying jobs actually run and\nsucceed on schedule. This skill covers the patterns.\n\n## When to use\n\n- Adding monitoring to existing cron jobs or scheduled tasks\n- Choosing heartbeat vs exit-code vs log-based monitoring\n- Detecting missed runs, late runs, and duration anomalies\n- Monitoring jobs across servers, containers, and serverless\n- Building the \"did the nightly job run?\" dashboard\n\n## Core concepts\n\n**Heartbeat (dead man's switch) monitoring.** The job pings a monitoring\nendpoint at start and on successful completion; the monitor alerts if the\nexpected ping doesn't arrive within the schedule window + grace period.\nThis catches the worst failure mode — the job never running — which\nexit-code monitoring alone misses entirely.\n\n**Three signals per job.** Started on time (schedule adherence), completed\nsuccessfully (exit status \u002F success ping), and duration within norms\n(sudden 10x slowdowns signal trouble even when the job \"succeeds\"). Monitor\nall three; each catches a different failure class.\n\n**Grace periods and expected variance.** Jobs don't run at exactly 02:00:00\n— schedulers queue, machines are busy. Set the expected window generously\n(schedule interval + reasonable grace), and wider for jobs with variable\nduration. Too tight = false alarms; too loose = late detection. Tune from\nobserved history.\n\n**Distinguish \"didn't run\" from \"ran and failed\".** Start ping vs success\nping separation tells you whether the scheduler\u002Fjob never started (infra\nproblem) or started and errored (job problem) — different responders,\ndifferent runbooks.\n\n**Monitor the monitor's coverage.** Keep a registry of all scheduled jobs\nwith their expected schedules; alert on jobs with no monitoring configured.\nThe unmonitored job is the one that will fail silently.\n\n## Practical workflow\n\n1. **Inventory every scheduled job:** what, where it runs, schedule,\n   owner, and what breaks if it silently stops — this registry is the\n   foundation.\n2. **Add heartbeat instrumentation:** ping start\u002Fsuccess (or use the\n   platform's cron-monitoring feature) with the job's identity and run\n   metadata; keep the ping mechanism simple and dependency-free (a failing\n   job should still be able to report failure).\n3. **Configure expectations:** schedule + grace period per job, based on\n   observed run times; alert routing to the job's owner.\n4. **Track duration:** record run times, alert on significant deviation\n   from baseline (2–3x p99), which often precedes outright failure.\n5. **Build the overview:** a single dashboard showing all jobs, last run,\n   status, and next expected run — the \"morning check\" view for on-call.\n6. **Test the alerts:** deliberately break a non-critical job's schedule\n   (or simulate a missed ping) and verify the alert fires and routes\n   correctly — untested monitoring is decoration.\n\n## Common pitfalls\n\n- **Monitoring only failures, not absence** — exit-code alerts catch\n  failures; only heartbeats catch \"never ran\". You need both.\n- **Grace periods too tight** — normal scheduler jitter pages on-call\n  weekly; base windows on measured history.\n- **No job registry** — jobs added without monitoring, discovered only\n  when they fail silently; make monitoring part of the job-creation\n  checklist.\n- **Heartbeat endpoint as a dependency** — if the monitoring endpoint is\n  down, every job \"fails\"; keep pings fire-and-forget and monitor the\n  monitor separately.\n- **Ignoring duration drift** — a job creeping from 5 to 50 minutes is\n  heading for timeout\u002Foverlap failure; trend it.\n- **Alerting to nobody** — cron alerts to an unmonitored email alias;\n  route to the owner with an escalation path like any other alert.\n",{"name":5,"category":24,"description":7},"sentry","main","af388a77c2fe5e0b4fd879cca4300a0ffa9a6579","skills\u002Fams-cron-monitoring",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 cron-monitoring",{"tool":39,"command":40},"bunx","bunx skills add TanNhatCMS\u002Fjarvis --skill cron-monitoring",{"tool":42,"command":43},"pnpm","pnpm dlx skills add TanNhatCMS\u002Fjarvis --skill cron-monitoring","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FTanNhatCMS\u002Fjarvis\u002Fblob\u002Fmain\u002Fskills\u002Fams-cron-monitoring\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",[],[]]