wrap-up
End-of-session command that persists context to Obsidian. Resolves project from local registry, loads any session handoff, then writes an Obsidian session note (when configured) and an Obsidian daily note. Use when finishing a work session, saving progress before clearing context, or documenting what was accomplished. Triggers: "wrap up", "wrap-up", "end session", "finish up", "close session". Not for mid-session note-taking (Obsidian writes happen at the end only).
What this skill does
# Wrap Up Session
End-of-session documentation to Obsidian.
## Workflow
```
mapping --> handoff:Load --> obsidian-notes (enrich + compose) --> handoff:Detect+Cleanup
```
Resolve project from current working directory, load any session
handoff (when present), then write Obsidian notes. `obsidian-notes`
opens with an Enrich step that folds relevant current-session
observations from claude-mem into working context (silent skip when
MCP unavailable). No confirmation between note-writing steps. The
closing step runs structural-delta detection — silent unless a delta
fires — then clears the handoff file automatically (wrap-up has
already persisted the snapshot to Obsidian, so the on-disk copy is
redundant).
## Triggers
- **End-of-session command** ("wrap up", "wrap-up", "end session",
"finish up", "close session") → run all references in sequence
The skill is single-trigger: every invocation runs the full workflow.
Loading order:
1. [mapping.md](references/mapping.md) — resolve project paths and base tags
2. [handoff.md](references/handoff.md) (Load phase) — fold latest snapshot when present
3. [obsidian-notes.md](references/obsidian-notes.md) — write Obsidian session + daily notes
4. [handoff.md](references/handoff.md) (Detect + Cleanup phases) — architecture-refresh hint + auto-clear
## Guidelines
- Call Obsidian MCP tools directly — no skill indirection
- Execute all steps in order without confirmation between them
- Search existing notes before creating new ones to avoid duplicates
- Skip Obsidian session note when mapping returns `--` for Obsidian session
- Always create or update the Obsidian daily note, regardless of mapping
- Keep session and daily notes brief and human-scannable
- Use Obsidian `#hashtags` for observations and `## Relations` typed edges
## Anti-Pattern: Confirmation Between Steps
Pausing for user approval between mapping and obsidian-notes breaks
the wrap-up promise: a single command persists everything. The user
has already invoked the skill — that is the confirmation. Run all
steps and report at the end.
## Anti-Pattern: Re-Reading the Session Handoff
The session handoff is read once during the Load phase and shared via
working context with downstream references. Re-reading the file in
obsidian-notes wastes I/O and risks divergence if the file changes
mid-flow. Load once, share, then clear at the end.
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.