BrianRWagner/ai-marketing-claude-code-skills / daily-briefing-builder
daily-briefing-builder
VerifiedGenerate a clean morning brief in Claude Code — pulls today's priorities, unposted content, and weather from your vault.
Daily Briefing Builder
Generates a morning brief from your Obsidian vault. Reads today's action file, scans for unposted content, and fetches weather — all inside a Claude Code session.
No APIs. No paid services. No agent autonomy required. You run it, you get your brief.
Mode
Detect from context or ask: "Just today's top 3, the full brief, or the full brief plus a week-ahead look?"
| Mode | What you get | Best for |
|---|---|---|
quick | Today's 3 actions only (Step 1). No content scan, no weather. | Busy mornings, a 30-second check |
standard | Full brief: actions, unposted content, weather, self-critique | Your normal morning routine |
deep | Full brief plus carryover from the last 7 days of action files, stalled drafts older than 14 days, and one "if you only do one thing" call | Monday planning, or after time away |
Default: standard. Use quick if they say "just the top 3." Use deep on Mondays or when they ask what slipped.
How to Use
Open Claude Code in your vault directory and say:
Run the Daily Briefing Builder skill.
Or with context upfront:
Run the Daily Briefing Builder skill. My vault is at /path/to/vault and my city is Ann+Arbor.
Skill Instructions (for Claude Code)
When this skill is invoked, follow these phases exactly.
PHASE 1: INTAKE
Check whether the user has provided:
vault_path— absolute path to their Obsidian vaultcity— city name for weather (wttr.in format, spaces as+)
If either is missing, ask before proceeding:
To run your morning brief, I need two things:
1. Your vault path (e.g. $HOME/vault)
2. Your city for weather (e.g. Ann+Arbor or London)
Do not proceed to PHASE 2 until both values are confirmed.
PHASE 2: ANALYZE
Run these shell commands in sequence. Capture all output before formatting.
Step 1 — Today's actions:
TODAY=$(date +%Y-%m-%d)
VAULT="VAULT_PATH_HERE"
ACTIONS_FILE="$VAULT/tracking/daily-actions/${TODAY}.md"
if [ -f "$ACTIONS_FILE" ]; then
echo "FILE_FOUND"
awk '/## Today.s 3 Actions/{found=1; next} found && /^[0-9]/{print} found && /^##/{exit}' "$ACTIONS_FILE"
else
echo "FILE_MISSING:$ACTIONS_FILE"
fi
Step 2 — Unposted content scan:
VAULT="VAULT_PATH_HERE"
READY_DIR="$VAULT/content/ready-to-post"
if [ -d "$READY_DIR" ]; then
find "$READY_DIR" -name "*.md" -printf "%T@ %p\n" 2>/dev/null \
| sort -rn | awk '{print $2}' \
| while read f; do
if grep -q '\*\*Posted:\*\* ❌' "$f" 2>/dev/null; then
platform=$(echo "$f" | sed "s|.*/ready-to-post/||" | cut -d'/' -f1)
title=$(grep -m1 '^[^#\-\*>|` ]' "$f" 2>/dev/null | head -c 100)
rel="${f##$VAULT/}"
echo "ITEM|$platform|$rel|$title"
fi
done
else
echo "DIR_MISSING:$READY_DIR"
fi
Step 3 — Weather:
curl -s --max-time 5 "wttr.in/CITY_HERE?format=3" || echo "WEATHER_UNAVAILABLE"
PHASE 3: OUTPUT
Format and print the brief to the terminal:
☀️ Morning Brief — [Weekday, Month Day]
TODAY'S 3 ACTIONS
[numbered actions, or fallback message if file missing]
READY TO POST ([shown] of [total])
[platform] [title] — [relative file path]
...and X more in the pipeline ← only if total > 5
WEATHER
[wttr.in output or fallback]
Formatting rules:
- Cap ready-to-post display at 5 items (newest-modified first)
- If
content/ready-to-post/doesn't exist:No ready-to-post folder found - If no unposted files:
Content queue is empty - If actions file missing:
No actions file for today — create one at tracking/daily-actions/YYYY-MM-DD.md - If weather fails:
Weather unavailable (offline)— do not abort the brief
PHASE 4: SELF-CRITIQUE
Before delivering, run this internal check. Fix anything that fails — do not deliver until all 4 pass.
- Actions accuracy — Was the actions file found? Did numbered items extract correctly? If the file exists but no items were found, note the potential heading mismatch.
- Content completeness — Count the
ITEM|lines in Step 2 output. Does the number shown in the brief match? Were any files skipped? - Weather result — Did curl return valid output? Is the fallback shown if it failed?
- Format cleanliness — No raw bash output. No placeholder text. All three sections present.
Example Output
☀️ Morning Brief — Friday, February 28
TODAY'S 3 ACTIONS
1. Finish Q1 content calendar
2. Send invoice to a client
3. Publish LinkedIn post on AI ops
READY TO POST (5 of 9)
[linkedin] Nobody talks about what happens when your AI system fails... — content/ready-to-post/linkedin/ai-ops-failure.md
[twitter] The overnight ops shift is real. We run Scribe at 2am... — content/ready-to-post/twitter/async-ops.md
[newsletter] AI marketing systems that actually work — content/ready-to-post/newsletter/systems-post.md
[linkedin] Three things I stopped doing after deploying agents — content/ready-to-post/linkedin/stopped-doing.md
[twitter] Founders who ignore async AI ops are about to find out why — content/ready-to-post/twitter/ignore-ops.md
...and 4 more in the pipeline
WEATHER
Ann Arbor: ☀️ +42°F
Daily Actions File Format
Expected path: <vault>/tracking/daily-actions/YYYY-MM-DD.md
Expected structure:
# Daily Actions — 2026-03-01
## Today's 3 Actions
1. First priority
2. Second priority
3. Third priority
If you use a different path or heading, tell Claude Code when invoking the skill.
Requirements
- Claude Code with bash tool access
- Vault with
content/ready-to-post/folder (files must contain**Posted:** ❌to register as unposted) curlinstalled (weather fails gracefully without it)- Daily actions file optional — brief still runs without it
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| reverse-engineer-anythingmorluto/reaReverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA, and build agent environments (AgentEnv bundles) of web applications from a live instance or a capture, and of Linux desktop apps with a task from a request. Use shipped-artifact or requested runtime evidence to explain features, compare versions, decompile code, or guide a reconstruction. Skip REA for ordinary source-repository architecture analysis. | Stars: 471k | Updated | Claude CodeCodex | Verified | Install |
| diagnosing-superpowersobra/superpowersUse when a superpowers session went wrong and your human partner wants to know why — repeated work, ignored plans, stumbles, poor results, a skill that didn't fire, "it took too long", "why is it so expensive", "what is it doing" — or wants to build a bug report for the superpowers maintainers, for the current session or a past one identified by id or path, on any harness. | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| executing-plansobra/superpowersUse when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is available | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |