Automations Anonymous
Sheet
Display
Read
Type

Sheet 03 · /automations

Automations

Every published automation as a structured record: trigger, steps, prerequisites, failure modes, and the runnable payload.

tool: anycategory: anydifficulty: any
  1. Fail the build when published content stops being valid

    A CI step parses every code snippet a site publishes using the real tool for its declared format, so a snippet that stops being valid breaks the build instead of sitting published and wrong.

  2. 02intermediatebashcurlnode

    Check that your API and MCP server still say what your website says

    A read-only script asserts that every machine-readable view of a site answers, that its MCP server completes a handshake and lists its tools, and that no private field appears in any public response.

  3. 03intermediatebashcurlagent-browser

    Screenshot every route at phone and desktop width after every change

    One script walks every route in a site, checks each against an expected status code, captures the canonical, robots and description tags, screenshots at two widths, and exits non-zero when any check fails.

  4. Post every form response to a chat channel

    An Apps Script trigger on the responses spreadsheet posts each new form submission to a chat channel as a readable message, so the people who act on it never open the sheet.

  5. 05intermediatecrondocker

    Reclaim disk space from Docker every Sunday

    A weekly cron line prunes Docker images, containers, networks and build cache untouched for seven days, and deliberately leaves volumes alone so data survives.

  6. 06intermediategithub-actionsnpm

    Build, test and deploy on every push to main

    A GitHub Actions workflow installs, tests and builds on every push to main and then runs one publish step, cancelling an older run when a newer push arrives.

  7. 07beginnergmail

    File every receipt out of the inbox automatically

    One Gmail filter labels anything that looks like a receipt or an invoice and archives it, so purchases stay searchable in one place and out of the inbox.

  8. Tell a chat channel when a site goes down, once

    A five minute cron check posts to a chat webhook only when a site changes state, so an outage announces itself once and the recovery announces itself once.

  9. 09beginnercronbashtar

    Back up one folder every night and keep two weeks

    A nightly cron job archives one folder to a dated tar.gz and deletes archives older than fourteen days, so a restore is always a single file away.