save-note
Files the current conversation answer as a permanent wiki page in Obsidian. Make sure to use this skill whenever the user says "save this to my notes", "add this to my knowledge base", "create a wiki page for this", "save what we discussed", or "file this answer". Converts session synthesis, insights, or technical decisions into a self-contained reference note. Never writes a note that references "the conversation above" — the body must stand alone.
What this skill does
# Save Note File this session's answer as a permanent wiki page in Obsidian. The note must be self-contained — a reader with no context should be able to understand it. ## Step 1 — Determine Title and Folder If `$ARGUMENTS` provides a title, use it. Otherwise ask: "What should this note be titled, and which folder?" using `AskUserQuestion`. Default subfolders in `3 - Resources/`: | Subfolder | When to use | | ---------------- | ---------------------------------------------------- | | `Coding/` | Engineering patterns, technical decisions, API notes | | `Reflections/` | Personal insights, mental models, lessons learned | | `Concepts/` | General concepts, frameworks, ideas | | `Communication/` | Leadership, writing, comms patterns | ## Step 2 — Search Before Writing ```bash obsidian search query="<topic>" ``` - Score ≥ 0.7 → append a dated section to the existing page - Score < 0.5 → create a new page ## Step 3 — Write the Note **New page:** ```bash obsidian create path="3 - Resources/<subfolder>/<title>.md" content="<note>" ``` **Append to existing:** ```bash obsidian append path="3 - Resources/<subfolder>/<existing>.md" \ content="\n## Update — $(date +%Y-%m-%d)\n\n<content>" ``` Frontmatter for new pages: ```yaml --- source: claude-memory created: YYYY-MM-DD tags: [claude-memory, <topic-tags>] --- ``` Body: the synthesized answer from this session. Neutral, reference-focused voice — no "I learned that..." framing. Should make sense to a reader with no context. ## Step 4 — Update Index and Log Add to `index.md` under the `## Concept notes (claude-memory)` heading. The CLI has no `patch`, so this section-targeted insert means either the MCP `obsidian_patch_content` tool (target the heading, `operation: append`) or `read` + `create ... overwrite`. Ask the user which. Entry format: ``` - **<Title>** ($(date +%Y-%m-%d)) — [[<stem>]] (<path>). _<one-line summary>_ ``` Append to `log.md` (chronological — append is fine): ```bash obsidian append path="3 - Resources/log.md" content="\n## $(date +%Y-%m-%d)\nsave-note | <title>" ``` ## Hard Rules - Body must be self-contained — no "as we discussed" or "see above" - Search before writing — never create duplicate pages - Write in wiki style: neutral, reference-focused, not diary voice - If Obsidian CLI fails: tell the user "Obsidian CLI isn't working — update Obsidian with CLI enabled"
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.