ld-wall-setup

Provisions a Raspberry Pi wall dashboard by minting its bearer token and configuring it through Plow Latch.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve? Setting up a household wall dashboard on a Raspberry Pi requires minting a bearer token, shipping it securely to the Pi, installing packages over ssh, and registering scheduled card producers — all while the agent runs in the cloud and cannot reach the home network directly. This Skill orchestrates that entire setup through the owner's Mac via Plow Latch, with a no-Mac fallback path. ## Core Features & Use Cases - Token minting and shipping: Runs mint_wall_token.py to idempotently mint the dashboard bearer token, persist it to the agent's dotenv, and write pi.env and dashboard.hdr files (mode 600) that are shipped whole via Latch file writes — never through chat or argv. - Pi bring-up through Latch: Probes ssh key auth, runs package installation and the updater bootstrap on the Pi, ships the env file, restarts the viewer, and verifies via /api/version; includes a no-Mac fallback where the owner runs the lines themselves. - Cron registration and proof: Registers the seven scheduled card producers, runs all five card producers immediately (alert, affirmation, weather, digest, sports), reads every card back from the Pi, and runs the calendar feed once to approve its Latch argv. - Use Case: The owner texts their life-assistant agent asking to set up the kitchen wall display; the agent mints the token, brings the Pi up through their Mac, fills all five cards, and confirms the wall is live. ## Quick Start Ask the assistant in your private one-to-one thread to set up your wall dashboard on your Raspberry Pi.

Frequently Asked Questions about ld-wall-setup

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

FAQPage Schema
How do I set up a Raspberry Pi wall dashboard through a cloud agent?▼

Run the setup in the owner's private thread: mint the wall token with mint_wall_token.py, bring the Pi up over ssh through Plow Latch on the owner's Mac, register the card producer crons, and run each producer once to fill all five cards before marking setup complete.

How does the wall token get to the Pi without exposing it?▼

The token travels only inside files shipped whole with the Latch file-write tool — pi.env to the Pi and dashboard.hdr to the Mac. It never appears in chat or on argv, since argv is shown on approval cards and kept in an audit record.

Can the wall be set up if the owner has no Mac?▼

Yes, via a fallback path: the agent texts the owner the two Pi command lines and the env line, the owner runs them on the Pi directly, and the agent writes a pi-brought-up marker once the owner confirms the screen is up. Scheduled card delivery still requires a Mac with Latch.

Why does the setup script refuse to proceed with my Pi address?▼

mint_wall_token.py refuses addresses that are not on the household network (a private IP or .local name) or that contain characters outside [A-Za-z0-9.-], because the address lands in a URL and an ssh argv element. It also refuses to guess an ssh login — the owner must supply it.

What happens if the wall setup is re-run after completion?▼

Each phase is gated on a durable artifact, so completed phases are skipped. The token script prints 'already minted' and never re-mints, since the Pi holds the original token; a re-run with a different address re-points the endpoint while keeping the token.