Skip to content
Get packs

Vigil Monitoring Log

Lets the agent check the Vigil event log, post events, read the held digest, and set up the monitoring tick.

Source Download skill
Repository
danielmiessler/LifeOS
Stars
19,682
Licence
MIT
Files
6 files

What it does

Vigil is a central event log for a personal LifeOS setup. Background jobs and subsystems write events (like a certificate about to expire or a service failing) into one format, and a five-minute tick sorts them by severity into a text message, a daily digest, or a dashboard. With this skill installed, the agent can answer questions like 'anything I should know?', check whether the monitoring tick is still running, post a new event to the log, read the held or medium-priority digest, or help install the tick.

Great for

  • Developers and power users already running the LifeOS framework who want one place for system alerts
  • People who want an agent to summarise what has been flagged without digging through logs
  • Anyone setting up a scheduled monitoring job on macOS with launchd

Skip it if

  • People who do not use LifeOS: the skill depends on its folder layout, policy files and launchd setup, so it will not work on its own (reason: missing prerequisites)
  • Anyone expecting it to alert them on arbitrary systems: it only routes events that subsystems post to its local log (reason: scope is narrow)
  • Use where phone texts are sent by a service you have not configured: texts and store uploads need credentials and a deployed Worker (reason: setup risk and possible data leaving your machine)

Try asking

  • “Anything I should know about right now?”
  • “Is the Vigil tick alive?”
  • “Log this to Vigil: backup job finished with warnings”
  • “What got held in the pending digest today?”
Step-by-step guide: how to use Vigil Monitoring LogInstall, first run, examples, tips and FAQs

Install in 3 steps

  1. 1

    Download the skill

    The ZIP contains the 6 original files, the MIT licence and an attribution note.

    Vigil.zip
  2. 2

    Add it to your agent

    Claude Code (all projects)

    mkdir -p ~/.claude/skills && unzip Vigil.zip -d ~/.claude/skills/

    Claude Code / Agent SDK (this project only)

    mkdir -p .claude/skills && unzip Vigil.zip -d .claude/skills/

    Claude apps (web/desktop): Settings → Capabilities → Skills → Upload skill, and choose the ZIP.

  3. 3

    Ask for the task

    No special command needed — the agent reads the skill's description and loads it when your request matches. Try one of the prompts above.

Get better results

  • Run the status check first after install; a first tick against a fresh cursor only writes a baseline and sends nothing, which is expected.
  • Keep store credentials in the env file only; the skill is written never to print them, but check your own logs before sharing output.
  • Use --dry-run to preview routing decisions before enabling texts, and review policy.json under your own USER folder rather than editing the skill.

What's inside

  • Intents/Digest.md
  • Intents/Emit.md
  • Intents/Install.md
  • Intents/Status.md
  • Setup.md
  • SKILL.md

Redistributed unmodified from danielmiessler/LifeOS under the MIT licence. The assessment was drafted with AI from the skill's files on 2026-10-29. Skills can instruct your agent to run code — read SKILL.md and any scripts before installing.