session-learner
Extract and persist learnings from the current session. This skill should be used when the user wants Claude to analyze the conversation and capture insights, patterns, preferences, or knowledge discovered during work. Triggers on requests like "learn from this session", "what did we learn", or "capture insights".
What this skill does
# Session Learner Analyze the current session to extract learnings and persist them to appropriate locations. ## Workflow ### Step 1: Analyze Session Review the entire conversation to identify learnings in these categories: 1. **User Preferences** - Working style, communication preferences, tool preferences 2. **Agent Failure Patterns** - Mistakes Claude made, misunderstandings, approaches that didn't work 3. **Project Technical Patterns** - Code patterns, architecture decisions, project-specific conventions 4. **Reusable Workflows** - Multi-step procedures that could become skills 5. **Reference Knowledge** - Architectural decisions, domain knowledge, API behaviors ### Step 2: Categorize by Destination Map each learning to its appropriate destination: | Learning Type | Destination | Rationale | |---------------|-------------|-----------| | User preferences | `~/.claude/CLAUDE.md` | Applies across all projects | | Agent failure patterns | `~/.claude/CLAUDE.md` | Prevents repeating mistakes globally | | Project technical patterns | Project `CLAUDE.md` | Project-specific guidance | | Reusable workflows | New skill | Procedural knowledge for reuse | | Reference knowledge | Project `docs/` folder | Documentation for future reference | ### Step 3: Check for Conflicts Before presenting findings, check if any learning contradicts existing content: 1. Read the target file (user CLAUDE.md, project CLAUDE.md, or relevant docs) 2. Identify any conflicts between new learnings and existing content 3. Flag conflicts explicitly for user decision ### Step 4: Present Findings Present findings grouped by destination. For each group: 1. State the destination file path 2. List each learning with a brief description (1-2 sentences) 3. If conflicts exist, show: - The existing content - The proposed new content - Ask user to choose: keep existing, replace with new, or merge Format: ``` ## Learnings for ~/.claude/CLAUDE.md 1. [Brief description of learning] 2. [Brief description of learning] ⚠️ CONFLICT: [description] Existing: [current content] Proposed: [new content] Keep existing / Replace / Merge? ## Learnings for [project]/CLAUDE.md 1. [Brief description of learning] ## Learnings for [project]/docs/ 1. [Brief description] → docs/[filename].md ## Potential New Skill 1. [Workflow name]: [brief description] ``` ### Step 5: Apply Approved Learnings After user approves (or modifies) findings: 1. For CLAUDE.md files: Append to appropriate section, or create section if needed 2. For docs/: Create or update the markdown file 3. For new skills: Offer to create using the skill-creator skill ## Guidelines - Keep learnings concise and actionable - Prefer specific examples over abstract principles - Do not duplicate information already in target files - When uncertain about destination, ask the user to choose - Learnings should be evergreen - no temporal references like "today we learned"
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.