From obsidian-homelab
Run Matt's recurring daily and weekly routines — morning briefing, vault triage, weekly Polaris review, and session completion checklist. Use when asked to run a morning briefing, process inbox notes, do a weekly review, or wrap up a work session.
How this skill is triggered — by the user, by Claude, or both
Slash command
/obsidian-homelab:daily-workflowsThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
This skill orchestrates Matt's recurring routines across Obsidian, Pippin, Telegram, and the homelab. Each workflow below can be triggered by name.
This skill orchestrates Matt's recurring routines across Obsidian, Pippin, Telegram, and the homelab. Each workflow below can be triggered by name.
/morning-briefing)The morning briefing aggregates mail, calendar, and tasks into a plain-text Telegram message.
ioreg -n IOHIDSystem | grep HIDIdleTime)open -a Mail && sleep 4Gather mail — pull unread from all accounts in parallel using Pippin:
pippin mail unread --account iCloud --limit 10 --format json
pippin mail unread --account Exchange --limit 10 --format json
# repeat for Yahoo!, Google, [email protected]
Gather calendar — use Pippin calendar or JXA fallback:
pippin calendar today --format json
# JXA fallback if Pippin fails:
# osascript -l JavaScript -e '<JXA script>'
Pull open tasks from vault:
obsidian tasks vault="Matt's Vault" format=md
Compose plain-text message — no Markdown formatting (Telegram silently drops messages with _ or *). Structure:
Good morning! Here's your briefing for <date>.
CALENDAR
<event list>
MAIL (<N> unread)
<sender — subject, per account>
OPEN TASKS
<task list, top 5>
Send via Telegram:
CHAT_ID=$(get-secret "Personal AI Telegram Chat ID")
BOT_TOKEN=$(get-secret "Personal AI Telegram Bot Token")
curl -s -X POST "https://api.telegram.org/bot${BOT_TOKEN}/sendMessage" \
-d chat_id="$CHAT_ID" \
-d text="<message>"
/vault-triage)Process notes sitting in 00-Inbox/ and move them to their correct folders.
List inbox contents:
obsidian files path="00-Inbox/" vault="Matt's Vault" format=json
For each note:
obsidian read "00-Inbox/<name>" vault="Matt's Vault"obsidian move "00-Inbox/<name>" "<target-folder>/<name>" vault="Matt's Vault"Report: list of notes processed and where each landed.
/weekly-review)A structured review of the past week and planning for the next.
Read last week's plan:
obsidian files path="01-Polaris/Weeks/" vault="Matt's Vault" format=json
# read most recent Week-*.md
Check open tasks:
obsidian tasks vault="Matt's Vault" format=md
Review Anchors — read each Anchor note and note any updates needed.
Compose new week plan using the polaris skill's Week Plan template.
Create the week plan note:
obsidian create name="01-Polaris/Weeks/Week-<YYYY-WNN>" content="..." vault="Matt's Vault" silent
Optional: write brief reflection for the closing week:
obsidian create name="01-Polaris/Reflections/Reflection-<YYYY-MM>" content="..." vault="Matt's Vault" silent
/session-done)Run at the end of any coding or infrastructure work session. From ~/.claude/CLAUDE.md:
File issues for remaining work:
bd create "Title" --description "..." --status open
Run quality gates (tests, linters) if code changed.
Update issue status:
bd close <id> # finished work
bd update <id> --status in_progress # ongoing
Push:
git stash && git pull --rebase && git stash pop && bd sync && git push
Verify git status shows "up to date with origin".
Work is not complete until git push succeeds.
# Get credentials
CHAT_ID=$(get-secret "Personal AI Telegram Chat ID")
BOT_TOKEN=$(get-secret "Personal AI Telegram Bot Token")
# Send a plain-text message
curl -s -X POST "https://api.telegram.org/bot${BOT_TOKEN}/sendMessage" \
-d chat_id="$CHAT_ID" \
-d text="<message>"
Plain text only — parse_mode: "Markdown" was removed 2026-02-25 because Telegram silently drops messages containing underscores or asterisks. Always send plain text.
npx claudepluginhub mattwag05/mw-plugins --plugin obsidian-homelabGuides creation, editing, and verification of skills for AI coding agents using test-driven development with subagent scenarios. Use when authoring or debugging skills.