PromptsOpenClaw
Daily social snapshots
Use case
You cannot tell which video earned subscribers and which one only earned views unless yesterday is written down. OpenClaw stores a daily snapshot for YouTube, Instagram, X, and TikTok, hands yesterday to the morning briefing, and leaves the tables where the business council can read them.
What to connect
YouTube Analytics, Instagram insights, an X API v2 bearer or user token, and TikTok account stats. One SQLite file per platform, or one file with a table per platform.
Setup
- Store each API key locally where OpenClaw can read it, and keep the keys out of git.
- Create the snapshot databases under [SOCIAL DB DIR].
- Schedule the snapshot after midnight local time so "yesterday" is a finished day.
- Confirm the morning-briefing skill is allowed to read these tables, and that business-council is too.
- Run one snapshot by hand and check that a video row has views, watch time, and engagement, not an empty shell.
Edit before you send: Which accounts to track, the database directory, and the snapshot time.
Prompt to paste into OpenClaw
Save this as a skill named social-tracker. Every day at [1:30] [TIMEZONE], store a snapshot of yesterday for my accounts. YouTube, in [SOCIAL DB DIR]/youtube.sqlite: - Per video: views, watch time, and engagement. - Subscriber conversion: which videos gained subscribers, separate from videos that only gained views. Instagram, in [SOCIAL DB DIR]/instagram.sqlite: - Per post: engagement. - Account growth for the day. X, using the X API v2, in [SOCIAL DB DIR]/x.sqlite: - Per post: impressions, likes, reposts, bookmarks, shares. - Follower change for the day. TikTok, in [SOCIAL DB DIR]/tiktok.sqlite: - Follower growth for the day. Write the rows even when a number is zero. If a platform fails, store the error on that platform's row and continue with the others. Do not copy yesterday's numbers forward and pretend they are new. The morning briefing reads yesterday from these tables. The business council reads them too. Do not also paste the raw tables into Telegram. The briefing already has that job.
More OpenClaw prompts
- Personal CRM from mail and calendar
A year of email and meetings is a pile of names you cannot search. OpenClaw reads Gmail and Google Calendar, drops newsletters and cold pitches, and keeps a local profile for each person worth remembering. You ask in plain language who you know at a company, or who has gone quiet.
- Meeting action items with an approval queue
Meetings end and the promises disappear. OpenClaw waits until a meeting is over, pulls the Fathom transcript, matches the room to your CRM, and sends you each action item to approve. Approved items become Todoist tasks. Things other people owe you stay on a waiting-on list, except people on your own team.
- Urgent email, only when it can wait no longer
You do not live in the inbox, including on weekends. OpenClaw checks mail on a timer, ignores senders you have already marked as noise, and pings a Telegram topic only when something needs you now. When you say an alert was wrong, the next check is stricter.
- Knowledge base you fill from a Telegram topic
Links you meant to remember are scattered across chats. You drop a URL into one Telegram topic. OpenClaw saves the article, the video transcript, the full post thread, or the PDF, then you ask later in plain language. A new save can point at something you already kept.