ld-weekly-digest

Generates a weekly household calendar digest and posts it to a kiosk display and chat.

2|Updated Aug 25, 2026
One-click install
npx skills add https://github.com/plow-pbc/life-assistant-hermes-agent --skill ld-weekly-digest-plow-pbc
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: ld-weekly-digest
Source: https://github.com/plow-pbc/life-assistant-hermes-agent/tree/main/ld-weekly-digest
Command: npx skills add https://github.com/plow-pbc/life-assistant-hermes-agent --skill ld-weekly-digest-plow-pbc

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve? Keeping a household aware of the upcoming week's schedule requires manually reviewing multiple calendars and summarizing them for a shared display. This Skill automates that by fetching live calendar events, composing a scannable weekly digest, and delivering it to both a home kiosk and the owner's chat. ## Core Features & Use Cases - Live calendar aggregation: Fetches events from all configured calendar sources via plow-gog through Plow Latch, merging them into one chronological 7-day view with optional long-lead heads-up fetches. - Privacy-safe summarization: Omits medical, private, or sensitive event titles and locations entirely so the digest is safe for a shared kiosk display readable by children. - Dual-surface delivery: Posts the digest to the kiosk as card 4 via a helper script and returns the same text in Plow Chat, with a configurable length/shape preference from the shared config. - Use Case: A cron job runs every Sunday at 17:00, reads the household's calendars, and publishes a "This week" digest card on the kitchen kiosk while also sending the same summary to the owner's chat. ## Quick Start Ask the agent to build a weekly digest from the household calendars and post it to the kiosk.

Frequently Asked Questions about ld-weekly-digest

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

FAQPage Schema
How do I generate a weekly calendar digest from multiple calendars?▼

Read the calendar account and source list from the shared config, then fetch events with a single plow-gog calendar events list call using --days=7 and comma-joined calendar IDs. Merge all events chronologically and summarize by day.

How does the weekly digest get posted to a kiosk display?▼

The digest text is written to a fixed handoff file, then the post_digest.py helper reads it and posts to the kiosk endpoint as card 4 using credentials from environment variables. On success it consumes the handoff file and the same text is returned in chat.

Can the digest length or format be customized?▼

Yes, the weekly_digest.length field in the shared config is a free-form preference that overrides the default layout. When set, the digest is composed to that preference even if it means dropping sections like the by-day breakdown.

Why must calendar fetch commands use a fixed argv with no computed dates?▼

Latch always-allow approval rules key on the exact argv, so any computed value like a date makes each run's command novel and stalls it on an approval card. The rolling window is expressed with --days=7, which plow-gog computes in local time.

How are private or medical calendar events handled in the digest?▼

Sensitive titles and locations are omitted entirely rather than generalized or paraphrased, since the kiosk is a shared display a child may read. The same privacy boundary applies to the chat-delivered text.

What happens if the calendar account is not connected?▼

The skill surfaces the connection error verbatim and stops. It never builds a digest from memory or cached data, and it never claims a kiosk post or delivery succeeded unless it actually did.