sync
Prep for 1:1s with your manager — auto-summarizes journal entries since your last sync into a briefing with wins, progress, and blockers.
What this skill does
You are helping the user prepare for a 1:1 meeting with their manager by summarizing recent work from their journal.
## Setup
1. The manager directory is `${user_config.manager_directory}`. If that's empty or not set, fall back to `${CLAUDE_PLUGIN_DATA}`.
2. Read `${CLAUDE_PLUGIN_ROOT}/references/setup.md` and follow the setup instructions to resolve `<manager_dir>` and `<daily_dir>`.
3. Read the goals file (`<manager_dir>/goals.md`) to have the user's goals in context.
4. Determine the date range to summarize:
- Read the sync log file at `<manager_dir>/.last_sync`. It contains a single date (`YYYY-MM-DD`) — the last time a sync was run.
- If the sync log doesn't exist, default to the last 14 days.
- The range is: **day after last sync** through **today**.
## Gathering Context
5. List journal files in `<daily_dir>` that fall within the date range. Read all of them.
5. If the user passed an argument (e.g. a manager name or topic), note it — you'll tailor the summary to that context.
## Generating the Sync Summary
6. Present a structured summary to the user in this format:
```
## 1:1 Sync Prep — [date range]
### Wins & Accomplishments
- [Concrete things completed, shipped, or unblocked — pull from "Accomplished" and "Finished today" sections]
### In Progress
- [Work that's actively ongoing — pull from recent "Plans for today" and "Notes for tomorrow" sections]
### Blockers & Concerns
- [Anything flagged as a blocker, things that didn't get done repeatedly, or frustrations mentioned]
### Goal Alignment
[2-3 sentence assessment of how the period went relative to long-term goals. Reference specific days and entries — not vague summaries. Name which goals got attention and which didn't. If deep work was lacking, say so plainly.]
### Suggested Talking Points
- [2-4 bullet points the user might want to raise with their manager, based on the above]
```
7. After presenting the summary, ask the user:
- "Anything you want to add, change, or emphasize before I save this?"
8. Incorporate any feedback, then save the sync summary by appending to today's journal entry at `<daily_dir>/YYYY-MM-DD.md`:
```markdown
## 1:1 Sync Prep [HH:MM]
**Period:** [start date] to [end date]
**Wins:**
[bulleted list]
**In Progress:**
[bulleted list]
**Blockers:**
[bulleted list]
**Goal alignment:**
[your assessment]
**Talking points:**
[bulleted list]
```
9. Update the sync log file at `<manager_dir>/.last_sync` with today's date (overwrite the file with just `YYYY-MM-DD`).
## General Rules
- If the journal file for today doesn't exist, create it with a `# Journal - YYYY-MM-DD` heading before appending.
- Always confirm that the sync prep has been saved and the sync log has been updated.
- Keep the summary concise and actionable — this is a meeting prep tool, not an essay.
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.