I cleaned up ten OpenClaw skill folders from my Raspberry Pi setup so you can inspect how each job is wired. Some are scheduled jobs. Some are reference folders. I mostly wanted the folder structure visible: a SKILL.md, setup notes, and scripts where the workflow needs them.
Hardware: Raspberry Pi 5, 8GB RAM, running Raspberry Pi OS. OpenClaw handles the agent layer. Each folder has a SKILL.md for the job, a SETUP.md for the boring install parts, and scripts where the workflow needs actual code instead of another prompt.
Delivers a daily briefing to Telegram at 6:30am with weather, calendar events, market data, AI news, and personal notes. Pulls from Google Calendar API, wttr.in, and web search.
Python, Google Calendar API, Brave Search, Telegram
Builds transcript-backed YouTube learning packets and saves them where they can be reviewed later.
YouTube Data API, Supadata API, OpenAI, Notion
Turns the week into a short review of content output, project status, and what needs attention next.
Bash, files, weekly notes
Overnight build-and-research slot that picks one real problem, ships a concrete artifact, and records what not to repeat.
OpenClaw agent, memory files, research log
Takes raw notes from the intake stage, drafts social posts in a consistent voice, audits for AI patterns, generates hooks, and queues them for review.
Python, LLM drafting and auditing, File pipeline
Weekday briefing on war, defense, and cybersecurity, with sources separated from the final summary.
Bash, Brave Search, notes
Pulls transcripts and content from YouTube, Instagram, and TikTok URLs. Used by other skills for video learning and content intake.
Supadata API, Python
Pulls current conditions and forecasts from simple weather sources so other jobs do not need to solve that part again.
wttr.in, Open-Meteo
Turns recipe-card images into structured recipe entries with OCR, cleanup, and Notion output.
OpenAI, Notion, OCR workflow
Manages Google Calendar through OAuth so calendar work can happen through an actual API instead of copy-paste.
Google Calendar API, OAuth2, Python
Most OpenClaw "skills" shared online are prompt files: a SKILL.md with instructions and nothing else. These folders show more of the wiring:
The difference matters when you are setting up a morning briefing and the calendar API integration does not work because the token path is wrong. Or when your content pipeline fails because the prompt assumes a folder name you do not use. A folder with setup notes gives you something to inspect before you start changing your own stack.
6:00am - Morning briefing
2:00pm - Daily video learning
3:00pm - Content flywheel
weekday - Geopolitical briefing
Monday - Weekly review
10:00pm - Nightly YOLO buildThe Pi runs 24/7 at ~3-5 watts. No cloud costs, no server management, no worries about a VM getting patched and rebooting. OpenClaw runs as a systemd service and auto-restarts on failure. The whole setup costs $80 in hardware and $0/month to operate.
I chose this over a VPS because the agent runs cron jobs that need reliable timing and persistent state. A $5/month VPS works too, but the Pi gives me physical control and zero recurring cost.
Get the 10 folders with setup guides and scripts where the workflow needs them.
Questions? Find me on Telegram at @aaronmakelky or at aaronmakelky.com.