periodic-rollup
Synthesize child periodic note descriptions into a parent weekly/quarterly/yearly note. For history rollup (compiling mentions of a project/topic into a Histories note), follow references/history-rollup.md.
What this skill does
# Periodic rollup Roll up periodic vault notes by synthesizing child descriptions into a parent note's `description`. If $ARGUMENTS is provided, use it to identify the periodic note to target. **History rollup** — When asked to roll up history for a project or topic, or to compile periodic mentions into a Histories note, follow [references/history-rollup.md](references/history-rollup.md) instead of this workflow. ## Workflow 1. **Gather** — Search for source notes using obsidian CLI or MCP vault search 2. **Synthesize** — Process gathered content according to the steps below 3. **Write** — Produce or update the output note ## Principles - Preserve source wikilinks back to origin notes for traceability - Respect the hierarchy: daily → weekly → quarterly → yearly - Preserve detail in archives; don't summarize what should be kept verbatim - Update `related` properties bidirectionally when creating new notes ## Process When generating a summary for a periodic note (weekly, quarterly, or yearly): 1. **Identify the note hierarchy** - Determine which periodic level you're summarizing (e.g., quarterly from weeklies, weekly from dailies) - Locate all related child notes referenced in the `related` frontmatter property 2. **Extract child descriptions** - Read the `description` property from each child note's frontmatter - These summaries usually crystallize the period's essence. However, if a description is missing, feels too vague, or if a specific day/week seems particularly significant, you are encouraged to read the original note content or sub-referenced notes to gain a more complete understanding. 3. **Scan parent note content** - Check if the parent note has any "Notes" or remarks sections that add context the children don't capture - Look for emergent patterns, meta-reflections, or threads that span multiple children - Don't treat these as equally weighted to the children—they're supplementary unless particularly revealing 4. **Synthesize without imposing narrative** - Combine child descriptions to surface what _actually_ happened across the period, not what makes a good story - Identify real tensions, recurring patterns, or unresolved threads - Avoid artificial arcs, redemption narratives, or forced thematic coherence - Keep it concise: aim for 2-4 sentences for weekly rollups, 3-5 for quarterly/yearly 5. **Update frontmatter** - Add or update the `description` property in the parent note's YAML - Use double quotes; preserve all other formatting - Only modify the description property ## Style guidelines - Use semicolons and dashes to separate ideas rather than connective adverbs - Prioritize concrete details and specific proper nouns that help memory recall - Include ambiguity or unresolved tensions if they characterize the period - Don't hedge or soften—be direct about what the period actually contained
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.