daily
Runs the daily startup ritual for the Obsidian vault — creates today's periodic notes, surfaces carry-forward items, checks inbox, and sets the day's focus. Make sure to use this skill whenever the user says "start my day", "daily startup", "morning routine", "what's my focus today", "set up today's note", or runs /daily. A 5-minute structured startup beats 30 minutes of reactive context-switching.
What this skill does
# Daily Startup
Structured morning ritual that creates periodic notes, surfaces what carried forward from yesterday,
checks the inbox, and locks in today's focus.
## Ask, Don't Assume
Shared principle (canonical version in the `vault` skill): never guess, deduce, or fill gaps with
assumptions about the user's notes, priorities, or intent. If you don't know — a date range, what
counts as a win, which goals are active — **ask**. Before writing any synthesis or judgment into a
note, show your draft with its source and get explicit confirmation. Missing data is not permission
to invent.
## Step 1 — Create Periodic Notes (no confirmation needed)
**Performance rule: batch all existence checks in parallel, then batch all template fetches in
parallel, then create. Minimize round-trips.**
Get today's path and check if the daily note exists:
```bash
TODAY="2 - Areas/Daily Ops/$(date +%Y)/$(date +%Y-%m-%d).md"
obsidian read path="$TODAY" 2>/dev/null
```
If missing, render from template and create:
```bash
obsidian template:read name="Daily Notes" resolve title="$TODAY"
obsidian create path="$TODAY" content="$PROCESSED_TEMPLATE"
```
**Template variable substitution** — if `resolve` doesn't substitute all variables, replace
manually:
- `{{date}}` → `YYYY-MM-DD`
- `{{title}}` → note title
- `{{week}}` → `W05`
- `{{month}}` → `January`
- `{{quarter}}` → `Q1`
- `{{year}}` → `YYYY`
**NEVER create empty notes.** If template fetch fails, report the error.
Run these checks in parallel based on today's date, then create all missing notes:
| Period | Condition | Path | Template |
| --------- | -------------------------- | ------------------------------------------------------- | ----------------- |
| Daily | always | `2 - Areas/Daily Ops/YYYY/YYYY-MM-DD.md` | `Daily Notes` |
| Weekly | Monday | `2 - Areas/Daily Ops/Weekly/M - Month YYYY/YYYY-Www.md` | `Weekly Planning` |
| Monthly | 1st of month | `2 - Areas/Goals/Monthly/M - Month YYYY.md` | `Monthly Goals` |
| Quarterly | Jan 1, Apr 1, Jul 1, Oct 1 | `2 - Areas/Goals/Quarterly/Quaterly Goals - QN YYYY.md` | `Quarterly Goals` |
**Note:** The quarterly FOLDER is `Quarterly/` but the FILE name uses the typo
`Quaterly Goals - QN YYYY.md` — preserve this to match existing vault structure.
## Step 2 — Yesterday's Carry-Forward
**Always check carry-forward before setting today's priorities.**
Read yesterday's daily note:
```bash
YESTERDAY=$(date -v-1d +%Y/%Y-%m-%d)
obsidian read path="2 - Areas/Daily Ops/$YESTERDAY.md" 2>/dev/null
```
Extract any items marked "Carry Forward → Tomorrow" or similar. Prepend them to today's note
immediately:
```bash
obsidian prepend path="$TODAY" content="**Carry forward from yesterday:**\n- [ ] Item 1\n- [ ] Item 2"
```
These are the first candidates for today's focus.
## Step 3 — Gather Context (run in parallel)
```bash
# Inbox count
obsidian files folder="0 - Inbox/" format=json
# Active projects
obsidian base:query path="MOCs/Active Projects.base" format=json 2>/dev/null || \
obsidian files folder="1 - Projects/" format=json
# Open tasks (from today's daily note; daily flag needs the Daily Notes plugin)
obsidian tasks todo path="$TODAY"
```
## Step 4 — Focus Interview (interactive)
Ask via `AskUserQuestion` with `multiSelect`:
> "Which projects are you focusing on today?" (list active projects from Step 3)
Then a single-select follow-up:
> "What's the single most important thing to finish today?"
## Step 5 — Update Daily Note
Fill today's Focus and Carry Forward sections. The CLI has no `patch`, so it cannot edit a named
section in place. Choose based on the note:
- If the section is empty or appending is acceptable, write with `append`/`prepend`:
```bash
obsidian append path="$TODAY" content="..."
```
- If the content must land in or replace a specific section, ask the user: use the MCP
`obsidian_patch_content` tool (heading-targeted), or recreate the note via
`obsidian read path="$TODAY"` + `obsidian create path="$TODAY" content="..." overwrite`.
## Report
After completion, tell the user:
- Which periodic notes were created (daily / weekly / monthly / quarterly)
- Inbox count (and flag if > 10 items — might need an ingest session)
- Carry-forward items surfaced from yesterday
- Confirmed today's focus
Related in General
modeling-omnistudio-epc-catalog
IncludedSalesforce Industries CME EPC product-modeling skill for Product2-based catalog creation. Use when creating EPC products, configuring product attributes, building offer bundles with Product Child Items, or reviewing EPC DataPack JSON metadata for product catalog changes. TRIGGER when: user creates or updates Product2 EPC records, AttributeAssignment payloads, AttributeMetadata/AttributeDefaultValues, Offer bundles, or ProductChildItem relationships. DO NOT TRIGGER when: designing OmniScripts/FlexCards/Integration Procedures (use building-omnistudio-omniscript, building-omnistudio-flexcard, or building-omnistudio-integration-procedure), implementing Apex business logic (use generating-apex), or troubleshooting deployment pipelines (use deploying-metadata).
relationship-science-coach
IncludedUse this skill for direct, practical adult relationship coaching: couples conflict, repair, trust, marriage, dating, flirting, attachment patterns, emotional connection, sex, desire differences, eroticism, kink negotiation, affection, love languages, breakups, and long-term passion. Draw on Gottman, EFT and Hold Me Tight, attachment science, modern sex research, Perel, Nagoski, Kerner, Schnarch, Love and Stosny, and flexible love-language tools. Be concrete and low-hedge. Redirect only for imminent danger, abuse, coercive control, minors, non-consent, self-harm, stalking, or medical/legal/psychiatric decisions.
building-sf-integrations
IncludedSalesforce integration architecture and runtime plumbing with 120-point scoring. Use this skill to set up Named Credentials, External Credentials, External Services, REST/SOAP callout patterns, Platform Events, and Change Data Capture. TRIGGER when: user sets up Named Credentials, External Services, REST/SOAP callouts, Platform Events, CDC, or touches .namedCredential-meta.xml files. DO NOT TRIGGER when: Connected App/OAuth config (use configuring-connected-apps), Apex-only logic (use generating-apex), or data import/export (use handling-sf-data).
venue-templates
IncludedAccess comprehensive LaTeX templates, formatting requirements, and submission guidelines for major scientific publication venues (Nature, Science, PLOS, IEEE, ACM), academic conferences (NeurIPS, ICML, CVPR, CHI), research posters, and grant proposals (NSF, NIH, DOE, DARPA). This skill should be used when preparing manuscripts for journal submission, conference papers, research posters, or grant proposals and need venue-specific formatting requirements and templates.
let-fate-decide
IncludedDraws the 12 Houses of the Zodiac Tarot spread to inject entropy into planning when prompts are vague, ambiguous, or casually delegated. Interprets the spread to guide next steps. Use when the user says 'let fate decide', 'YOLO', 'whatever', 'idk', or other nonchalant phrases, makes Yu-Gi-Oh references, or when you are about to arbitrarily pick between multiple reasonable approaches. Prefer over ask-questions-if-underspecified when the user's tone is casual or playful rather than precision-seeking.
net-ops
IncludedCross-platform network troubleshooting (Windows, macOS, Linux) via local or remote shell. Use for: DNS broken, can't resolve hostnames, nslookup/dig works but apps fail, NRPT, WFP, scutil, /etc/resolver, systemd-resolved, /etc/resolv.conf, NetworkManager, VPN DNS leak residue (ProtonVPN/Mullvad/WireGuard/AnyConnect), AV/firewall blocking DNS or DoH, Tailscale DNS interaction, intermittent connectivity, remote diagnostics over SSH.