Generate 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. How to Use Open Claude Code in your vault directory and say: Or with context upfront: 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 vault city — city name for weather (wttr.in format, spaces as + ) If either is missing, ask before proceeding: 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: Step 2 — Unposted content scan: Step 3 — Weather: PHASE 3: OUTPUT Format and print the brief to the terminal: 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 bambf/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. 1. 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. 2. Content completeness — Count the ITEM lines in Step 2 output. Does the number shown in the brief match? Were any files skipped? 3. Weather result — Did curl return valid output? Is the fallback shown if it failed? 4. Format cleanliness — No raw bash output. No placeholder text. All three sections present. Example Output Daily Actions File Format Expected path: <vault /bambf/tracking/daily actions/YYYY MM DD.md Expected structure: 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) curl installed (weather fails gracefully without it) Daily actions file optional — brief still runs without it

daily-briefing-builder