work-log-writer
Use only when the user explicitly names the work-log-writer skill; never auto-activate from generic work log, daily log, EOD summary, status update, or date-range summary requests.
What this skill does
# Work Log Writer ## Scope Write concise work logs for a specified date range in the current git repository. Do not use this skill unless the user explicitly invokes `$work-log-writer` or names `work-log-writer`. Operate on one git repository at a time. Do not write files unless the user explicitly asks for a saved note or file update. ## Date Range Resolve the requested range before collecting evidence. - If the user uses a relative range such as today, yesterday, or last week, check the current local date first. - Interpret "last week" as the previous calendar week by default. If context suggests the user might mean the last 7 days, ask one concise clarification question before proceeding. - If the user gives explicit dates or a start/end range, use them directly. - If no date range is provided, ask which date or period to summarize. Use concrete dates in the final title, not relative labels. Example commands: ```bash date +%F git config user.name git config user.email git log --since="2026-05-01 00:00" --until="2026-05-05 23:59:59" --date=iso --pretty=format:"%h%x09%ad%x09%an <%ae>%x09%s" ``` ## Evidence Collection Start from commits in the resolved range. 1. Gather commit hashes, authors, dates, and messages. 2. If commits include multiple authors, prefer commits from the current git user when `git config user.name` or `git config user.email` identifies them. If the current author cannot be determined, ask whether to summarize only the user's own commits. 3. If commit messages are too vague, inspect relevant diffs with `git show --stat <sha>` or `git show --name-only <sha>` before summarizing. 4. If the range includes today, optionally inspect uncommitted changes with `git status --short` and `git diff --stat`. 5. Use user notes or pasted context when provided, but do not invent completed work. ## Output Rules Required format: ```markdown # Work Log - <resolved date range> - ... - ... - ... ``` Use a title that includes the resolved date range. Keep the body as a single flat bullet list with no sections or subheadings. Each bullet should describe one high-level work item, progress point, blocker, or follow-up. Prefer concise summaries over implementation details, and order bullets from highest to lowest team impact. If team impact is unclear, use the evidence to prioritize likely cross-team/customer impact, risk reduction, unblockers, and follow-ups before lower-impact implementation details. ## Uncertainty Do not guess what the user completed. If evidence is insufficient, either mark the uncertainty in a bullet or ask for the minimum missing context needed to proceed.
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.