sessionlog:recap
This skill should be used when the user asks to "recap", "brief me", "remind me", "what did we work on", "what happened last time", "catch me up on recent sessions", "sessionlog recap", "session recap", "recent session summary", "tldr sessions", or wants a quick summary of what was worked on in recent sessions for this project.
What this skill does
# Session Recap
Read the last 3 session logs for this project and produce a concise TLDR of what was worked on.
## Steps
### 1. Find recent sessions
```bash
project_dir="$HOME/.claude/projects/$(pwd | sed 's|/|-|g')"
sessions=$(ls -t "$project_dir"/*.jsonl 2>/dev/null | head -4)
echo "$sessions"
```
We grab up to 4 because the most recent one is the *current* session. Skip it and use the 3 before it.
### 2. Export each session to readable TXT
For each of the 3 previous sessions (skip the first/current one):
```bash
output_dir=$(mktemp -d)
sessions=$(ls -t "$project_dir"/*.jsonl 2>/dev/null | head -4 | tail -3)
for session_file in $sessions; do
sid=$(basename "$session_file" .jsonl)
"${CLAUDE_PLUGIN_ROOT}/scripts/export-session.sh" "$session_file" "$output_dir" "$sid"
done
echo "Exported to: $output_dir"
```
If fewer than 3 previous sessions exist, use however many are available.
### 3. Read each exported TXT
Read the full content of each exported `claude-<session-id>.txt` file from the temp directory. Read them in reverse chronological order (most recent first).
### 4. Generate the recap
You are summarizing recent work sessions for a developer returning to this project. Your goal is a quick, scannable recap — not a full continuity document.
**Output format — print directly to the user (do NOT write to a file):**
```
## Session Recap
Last time we worked on:
1. **<topic>** — <one-sentence summary of what was done and the outcome>
2. **<topic>** — <one-sentence summary>
3. **<topic>** — <one-sentence summary>
...
```
**Rules:**
- Group by topic/theme, not by session. If two sessions touched the same feature, merge them into one bullet.
- Each bullet should answer: *what was done* and *what was the outcome* (shipped, in progress, blocked, etc.)
- Keep it to 3-7 bullets total. Fewer is better.
- Lead with the most important/recent work.
- Skip meta-activity (reading files, exploring code) — focus on actual outcomes.
- If something was left incomplete or blocked, say so explicitly.
- Do NOT create any files. Print the recap directly.
### 5. Clean up
```bash
rm -rf "$output_dir"
```
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.