Generate a clean morning brief in Claude Code — pulls today's priorities, unposted content, and weather from your vault.
npx skills add https://github.com/BrianRWagner/ai-marketing-claude-code-skills --skill 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.
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.
When this skill is invoked, follow these phases exactly.
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. /root/obsidian-vault)
2. Your city for weather (e.g. Ann+Arbor or London)
Do not proceed to PHASE 2 until both values are confirmed.
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/bambf/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"
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:
content/ready-to-post/ doesn't exist: No ready-to-post folder foundContent queue is emptyNo actions file for today — create one at bambf/tracking/daily-actions/YYYY-MM-DD.mdWeather unavailable (offline) — do not abort the briefBefore delivering, run this internal check. Fix anything that fails — do not deliver until all 4 pass.
ITEM| lines in Step 2 output. Does the number shown in the brief match? Were any files skipped?☀️ Morning Brief — Friday, February 28
TODAY'S 3 ACTIONS
1. Finish Q1 content calendar
2. Send invoice to BAMBF 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
Expected path: <vault>/bambf/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.
content/ready-to-post/ folder (files must contain Posted: ❌ to register as unposted)curl installed (weather fails gracefully without it)This skill should be used when the user asks to "create a hook", "add a PreToolUse/PostToolUse/Stop hook", "validate tool use", "implement prompt-based hooks", "use ${CLAUDE_PLUGIN_ROOT}", "set up event-driven automation", "block dangerous commands", or mentions hook events (PreToolUse, PostToolUse, Stop, SubagentStop, SessionStart, SessionEnd, UserPromptSubmit, PreCompact, Notification). Provides comprehensive guidance for creating and implementing Claude Code plugin hooks with focus on advanced prompt-based hooks API.
This skill should be used when the user asks to "create a hook", "add a PreToolUse/PostToolUse/Stop hook", "validate tool use", "implement prompt-based hooks", "use ${CLAUDE_PLUGIN_ROOT}", "set up event-driven automation", "block dangerous commands", or mentions hook events (PreToolUse, PostToolUse, Stop, SubagentStop, SessionStart, SessionEnd, UserPromptSubmit, PreCompact, Notification). Provides comprehensive guidance for creating and implementing Claude Code plugin hooks with focus on advanced prompt-based hooks API.
Build agentic applications with GitHub Copilot SDK. Use when embedding AI agents in apps, creating custom tools, implementing streaming responses, managing sessions, connecting to MCP servers, or creating custom agents. Triggers on Copilot SDK, GitHub SDK, agentic app, embed Copilot, programmable agent, MCP server, custom agent.
Coding Agent Session Search - unified CLI/TUI to index and search local coding agent history from Claude Code, Codex, Gemini, Cursor, Aider, ChatGPT, Pi-Agent, Factory, and more. Purpose-built for AI agent consumption with robot mode.
Destructive Command Guard - High-performance Rust hook for Claude Code that blocks dangerous commands before execution. SIMD-accelerated, modular pack system, whitelist-first architecture. Essential safety layer for agent workflows.
Makepad UI development skills for Rust apps: setup, patterns, shaders, packaging, and troubleshooting.
Secure environment variable management ensuring secrets are never exposed in Claude sessions, terminals, logs, or git commits
Prompt for generating an AGENTS.md file for a repository
Take brianrwagner/daily-briefing-builder from the repository into ~/.claude/skills for personal
use, or into .claude/skills inside a project.
The agent identifies a skill by the name field in its header. Two skills with the
same name cannot sit side by side — one of them will be ignored.