# Post 1: Valentine Story (Set the Stage) **Format:** X Article (recommended) or Long Post **Timing:** Post this FIRST (today or tomorrow morning) **Platform:** X/Twitter (primary), LinkedIn (optional, 24h later) --- ## Hook & Title ### X Article Title Option 1 (Recommended): **"I Built an AI Agent to Run Valentine's Day (Here's What Broke)"** ### X Article Title Option 2: **"OpenClaw + Cron + R2: Automating Valentine's Day Messages (And Why You Need Guardrails)"** ### Short Post Hook (if not Article): **"I used OpenClaw to automate my wife's Valentine's Day: timed messages, surprise web pages, and a 'roses are here' trigger when UPS delivered. She loved it. The agent? Not so much."** --- ## Full Article Draft ### Opening [IMAGE_PLACEHOLDER: Screenshot of Mac terminal showing `openclaw cron list` with valentine jobs OR a generic "message scheduling" screenshot — NO real messages/links] I wanted Valentine's Day to feel special this year, but I'm a builder—so I automated it. **The setup:** - **OpenClaw** running on my Mac (local agent, no servers) - **Cron jobs** for timed WhatsApp messages throughout the day - **Custom web pages** on Cloudflare R2 (romantic timeline, surprise reveals) - **One smart trigger:** A script that watched UPS tracking and sent a "roses are here" message the moment they were delivered **The result:** My wife said it was *"memorable and precious"* and thanked me for the thought and effort. Mission accomplished. --- ### The Technical Stack Here's what actually ran: ```bash # Setup script created all the cron jobs ./setup-valentine-final.sh # 9am Friday: "Will you be my Valentine?" + web page link # 12pm Friday: Romantic message # When UPS delivered: "48 roses on the way up!" (script-triggered) # 5pm Friday: "Get ready, we're going out at 6" # 9am Saturday: Wake-up message + preserved rose gift reveal + memory timeline page # 1pm, 3pm, 5pm, 7pm, 11pm Saturday: Messages tied to activities ``` Each message was sent via OpenClaw's WhatsApp integration. The web pages were static HTML hosted on R2 with gradients, embedded Spotify playlists, photo timelines—all generated by Claude and served at unique URLs. The UPS tracking script was the fun part: a bash loop that polled the tracking API every 15 minutes, and when status changed to "Delivered," it triggered the cron job immediately. No delays, no manual intervention. --- ### What Actually Broke **1. Message tool was too chatty** When the agent sent a romantic message, sometimes it included its own confirmation: ``` [My romantic message] Message sent to +1... Status: delivered ✓ ``` So my wife would get *my* words plus *the agent's* meta-commentary. Not terrible, but not the clean "just from you" experience I wanted. **2. No limits on what the agent could do** The agent could: - Run ANY shell command (`rm -rf` included) - Access ANY file on my system - Send unlimited messages to any number - Deploy anything to R2 without restrictions For a controlled Valentine's setup, this was fine—I wrote the scripts, tested everything, kept the Mac awake for 2 days. But imagine: - A typo in the cron schedule that sends 100 messages instead of 10 - A prompt injection that changes the message content - A bad command that wipes your deployed web pages - An agent that decides to "optimize" by sending all messages at once --- ### Why This Matters **This same stack—OpenClaw + cron + WhatsApp + file access—is what people are using for:** - Email automation - Code deployments - Database operations - Customer messaging - Financial transactions And most of them don't have guardrails. The Valentine's Day project was low-risk. But the pattern is everywhere: give the agent access, write a good prompt, hope it follows instructions. **That's not security. That's luck.** --- ### So We Built Guardrails After Valentine's, I added **pre-action authorization** to the stack: **Before the agent runs ANY tool:** 1. Check: Is this command in the allowlist? 2. Check: Does this operation exceed limits? 3. Check: Is there a kill switch active? 4. THEN: Allow or deny (no prompt negotiation) ```bash # Every tool call goes through this now ~/.openclaw/.skills/aport-guardrail.sh system.command.execute '{"command":"mkdir test"}' # Exit 0 = allowed, Exit 1 = denied # Reads passport + policies, writes structured decision ``` The agent can't bypass it. The prompt can't disable it. It runs at the platform level, before execution. **Same stack that made my wife's day special—now with "only these commands, only these limits, only these messages."** --- ### The Personal Part I'm not sharing the actual messages or the surprise pages—those stay between us. But her reaction was real: > *"Thank you for the intrigue, excitement, fun, and thoughtfulness you put into planning our Valentine celebration. I love you and I'm blessed to be loved by you."* Worth every hour of setup, testing, and one close call where I almost triggered a test message at 2am. --- ### Next Post Shipping the guardrails today. Local-first, 5-minute setup, works with OpenClaw out of the box. If you're building with agents—whether it's Valentine messages or production systems—you want this running before the agent does anything it can't undo. --- **[End of Article]** --- ## Short Version (Regular Post, not Article) [IMAGE_PLACEHOLDER: Terminal showing `openclaw cron list` OR generic message scheduling screenshot] **I automated Valentine's Day with OpenClaw: timed WhatsApp messages, custom web pages on R2, and a script that sent "roses are here" when UPS delivered.** My wife loved it. She said it was "memorable and precious." **But the stack had issues:** - Message tool sometimes sent my text + a "Message sent" confirmation - Agent could run any command, access any file, send unlimited messages - No guardrails = hope the prompt is right For a one-off Valentine? Fine. For anything else? Scary. **So I built pre-action authorization:** check before every tool run. Same stack, now with allowlists, limits, and kill switches. Next post: shipping the guardrails. Local-first, 5-min setup, works with OpenClaw today. --- ## Image Suggestions **Option 1 (Recommended):** Screenshot of `openclaw cron list` showing valentine jobs (blur job IDs if needed, keep the names like "valentine-friday-0900") **Option 2:** Terminal showing the setup script output (generic, no personal info) **Option 3:** Generic "message scheduling" diagram: User → OpenClaw → WhatsApp **DO NOT USE:** - Real web page links or screenshots (keep the surprise private) - Actual message content - Your wife's phone number or personal photos - Gift photos or specific locations --- ## Platform-Specific Notes ### X/Twitter - **Article preferred** for this one (better narrative flow, more engagement for stories) - Post time: Morning (8-10am ET) or evening (6-8pm ET) for max reach - Include 1-2 hashtags max: `#OpenClaw` `#AIAgents` (don't overdo it) ### LinkedIn (Optional) - Post 24h after X post - Slightly more formal tone: "I used OpenClaw to automate a personalized Valentine's experience for my wife" - Emphasize: "Same patterns we see in production: agent access + good prompt ≠ security" - Link to X post for full story, or re-post the short version - Relevant hashtags: `#AIAutomation` `#OpenClaw` `#AIEngineering` --- ## Pre-Post Checklist - [ ] Choose Article vs Short Post (Article recommended) - [ ] Add ONE screenshot (terminal or generic diagram—no personal content) - [ ] Remove all placeholders from article text - [ ] Schedule Post 2 (Guardrail) for 8-24h later - [ ] Test all formatting (line breaks, code blocks, links) - [ ] Double-check: NO real web page URLs, NO personal info --- ## Why This Works Based on successful OpenClaw posts from 2025-2026: 1. **Real outcome upfront:** "She loved it" = social proof 2. **Technical depth:** Actual commands, stack details, UPS tracking script 3. **Relatable problem:** "Message tool was chatty" = everyone's had this 4. **One human quote:** Your wife's message = emotional anchor 5. **Bridge to product:** "So we built X" in ONE sentence (not salesy) 6. **Clear next step:** "Next post: shipping the guardrails" **Most important:** This positions you as a builder who ships, not a marketer. The Valentine story is genuine, the technical details are specific, and the problem (no guardrails) emerges naturally from the experience.