session-end
Session wrap-up documentation.
What this skill does
# Session End Document your session before clearing context. This is a TWO-STEP process: `/session-end` documents, then user manually runs `/clear`. ## Contract Inputs: - Current session context and changed-file summary - Pending tasks, blockers, decisions, and reusable rules/workflows Outputs: - Saved session documentation - Clear next-step instruction for context reset Creates/Modifies: - `.agents/SESSIONS/YYYY-MM-DD.md` - Related `.agents/` task or summary files when delegated to `session-documenter` External Side Effects: - None Confirmation Required: - Before rewriting existing session entries - Before promoting captured rules or skills outside session docs Delegates To: - `session-documenter` - `rules-capture` for unresolved reusable preferences - `skill-capture` for reusable workflows that should become skills ## Workflow ### Step 1: Document Session When invoked, immediately: 1. Run the `session-documenter` skill to save all session context 2. Let it complete — it will document tasks, decisions, files changed, patterns, and mistakes 3. Confirm documentation saved > **Cross-platform note**: If your agent platform doesn't support skill invocation, follow the session-documenter workflow manually by reading the `session-documenter` skill definition. ### Step 2: Remind User to Clear After documentation is complete, tell the user: ``` Session documented to .agents/SESSIONS/YYYY-MM-DD.md NEXT STEP: Run /clear to clear the conversation context. Your session is safely preserved and will be loaded on next /session-start. ``` ## Why This Matters - WITHOUT documentation: all context is lost forever, next session has no idea what was done - WITH documentation: context preserved, next `/session-start` reads the session file, continuity maintained ## Important Notes - **ONE FILE PER DAY**: Session documenter appends to the same day's file - **Multiple invocations**: Each one adds a new session entry - **Does NOT clear context**: User must run `/clear` manually after ## Related Skills - **session-start** — Loads preferences and today's session after clearing - **session-documenter** — The underlying documentation skill
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.