spot-drift
Compares stated intentions against actual vault behavior over the past 30 days — surfaces gaps between what the user says matters and where time and energy actually go, and finds what's being avoided. Make sure to use this skill whenever the user says "what am I avoiding?", "am I drifting?", "check my priorities vs behavior", "what's getting neglected?", "spot drift", or runs /spot-drift. Absence of vault data does not equal absence of action — verify gaps with the user before concluding avoidance.
What this skill does
# Spot Drift Compare stated intentions against actual vault behavior over the past 30 days. Surface the gap between what you say matters and where energy actually goes. Find what's being avoided. ## 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. ## Obsidian Access Use Obsidian CLI via Bash. On failure: "Obsidian CLI isn't working — update Obsidian with CLI enabled." ## Step 1 — Gather Stated Intentions ### OKRs and Goals ```bash obsidian files folder="2 - Areas/Goals/Quarterly/" format=json obsidian files folder="2 - Areas/Goals/Monthly/" format=json # Read the most recent quarterly and monthly goal notes obsidian base:query path="2 - Areas/Goals/OKR Dashboard.base" format=json ``` Extract: stated priorities, self-commitments, items marked important/urgent, open questions flagged for investigation, projects in active/current status. ### Daily Note Intentions (past 30 days) ```bash TODAY="2 - Areas/Daily Ops/$(date +%Y)/$(date +%Y-%m-%d).md" # then read backwards obsidian read path="2 - Areas/Daily Ops/YYYY/YYYY-MM-DD.md" obsidian property:read path="2 - Areas/Daily Ops/YYYY/YYYY-MM-DD.md" name="energy_sleep" ``` Look for: "I need to..." / "I should..." / "I want to..." statements, carry-forward items from reflections, recurring themes that keep appearing, things flagged as tomorrow's priority that never get done. ## Step 2 — Gather Actual Behavior ### Vault Activity per Stated Priority ```bash obsidian search:context query="<stated priority A>" format=json limit=10 obsidian search:context query="<stated priority B>" format=json limit=10 obsidian backlinks file="<priority project note>" counts ``` For each stated priority: measure how much vault activity it generated. Which projects have recent activity? Which are stale? ### Active Projects Check ```bash obsidian files folder="1 - Projects/" format=json obsidian base:query path="MOCs/Active Projects.base" format=json obsidian property:read path="1 - Projects/<project>.md" name="status" ``` ## Step 3 — The Drift Report ### Alignment Score For each stated priority, rate intention vs. action: | Priority | Stated Importance | Actual Activity | Alignment | Drift | | -------- | ----------------- | --------------- | --------- | ----------- | | ... | High | Low | 3/10 | Significant | ### What's Getting Unplanned Attention Things consuming time not in any priority list. Where is energy leaking? ### What's Being Avoided The uncomfortable list. For each avoided item: - **What**: the thing being avoided - **Evidence**: mentions vs. actions (cite specific dates and notes) - **Possible why**: fear, unclear next step, not actually important, too big, requires a difficult conversation - **The cost**: what happens if avoidance continues **Avoidance Decision Tree** — run for each avoided item: - **(a) Mentioned in past 7 days?** Yes = active avoidance. No = passive. - **(b) Related items getting done?** If yes, avoidance is specific to THIS thing. Dig into why. - **(c) Has a clear next step?** If no, avoidance may be ambiguity. Define one concrete action. - **(d) Requires someone else?** If yes, the block may be relational. Name who and what the ask is. ### Recurring Push Pattern Tasks or intentions that appear, get pushed, reappear, get pushed again. For each: how many cycles? What breaks the loop? ### The Honest Assessment Direct, compassionate summary — not judgmental, just clear. "Here's what you said mattered. Here's what you actually did. Here's where they don't match." **Important:** Daily notes capture reflection, not everything done. When vault data is absent, use `AskUserQuestion` to verify before concluding avoidance. ### Recommended Corrections For each significant drift, exactly one of: - **Drop it** — keeps getting avoided → probably not a real priority. Remove. - **Do it now** — genuinely matters → schedule in the next 48 hours. - **Delegate it** — matters but won't get done → name who and when. - **Reframe it** — next step unclear → define one concrete action. ## Output Guidelines - Be honest but not harsh. This is a mirror, not a critic. - Always cite specific dates, notes, and data points. - The most valuable insight is often the simplest: "You said X matters. You haven't touched it in 3 weeks." - Don't conflate busyness with avoidance. - Distinguish "dropped and should stay dropped" from "dropped and it's costing you." - Absence of vault data ≠ absence of action. Verify with the user first.
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.