morning-health-check

Run daily TBM repository audits and GAS endpoint smoke tests with Pushover alerts.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/blucsigma05/tbm-apps-script --skill morning-health-check
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: morning-health-check
Source: https://github.com/blucsigma05/tbm-apps-script/tree/main/.claude/scheduled-tasks/morning-health-check
Command: npx skills add https://github.com/blucsigma05/tbm-apps-script --skill morning-health-check

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It prevents overnight failures in the Thompson Family Management (TBM) system from going unnoticed by running an automated daily check that audits the repo, verifies the live smoke endpoint, and detects error-log growth or deployed-version drift.

Core Features & Use Cases

  • Automated daily repo audit: Runs a static audit (audit-source.sh) and surfaces FAIL/WARN signals for early correction.
  • Endpoint smoke testing with retries: Calls the live GAS endpoint (?action=runTests) and distinguishes production downtime (non-200) from intermittent endpoint issues (timeouts/empty responses).
  • Operational monitoring signals: Scans the last 24 hours of ErrorLog entries and compares deployed versions (from ?action=version) against git HEAD to detect version drift.
  • Actionable alerting: Sends a single Pushover summary with severity tuned to audit/smoke results and error-log thresholds.

Quick Start

Tell the morning-health-check skill to run the daily 6am TBM health check that pulls main, audits the source, performs the runTests smoke call with retries, scans ErrorLog for the last 24 hours, and reports audit/smoke/errorlog/version-drift status via Pushover.

Frequently Asked Questions about morning-health-check

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automate a daily Google Apps Script health check and smoke test?

Automate a daily Google Apps Script health check by scheduling a script to pull the latest main branch, run static source audits, and invoke live GAS endpoints with retries. It validates JSON responses and emits prioritized Pushover alerts based on PASS, WARN, or FAIL statuses.

What is version drift detection and how does it monitor deployed endpoints?

Version drift detection compares the deployed application version retrieved from a live endpoint against the git HEAD commit. It identifies operational drift by pulling the canonical remote repository, checking the deployed version, and flagging mismatches in a consolidated status report.

How do I set up Pushover alerts for production error log monitoring?

Set up Pushover alerts by scanning the last 24 hours of ErrorLog entries and applying severity thresholds. The monitoring process tail checks the error logs, evaluates endpoint downtime versus intermittent timeouts, and sends a single prioritized Pushover notification summarizing the system health.

Can I run a static source audit and endpoint smoke test together on a schedule?

You can run a static source audit and endpoint smoke test together on a daily schedule. The process pulls the latest main branch, executes audit-source.sh for static checks, calls the runTests action with automatic retries, and validates the JSON output before reporting the combined results.

Why does my Google Apps Script endpoint smoke test fail with intermittent timeouts?

Intermittent endpoint timeouts during a Google Apps Script smoke test are distinguished from actual production downtime by checking for non-200 HTTP status codes versus empty responses. The health check applies retry logic to transient failures and validates the JSON payload before flagging a hard failure.

Does morning-health-check work with my existing Gitea repository and GAS deployment?

The morning-health-check process works with a Gitea repository and Google Apps Script deployment by pulling the latest main from the canonical Gitea remote. It audits the source, compares deployed GAS versions against git HEAD, and tests live endpoints to detect operational drift and failures.