Skip to content

henrygoldsmith07-wq/Claude-Code / .claude/skills/sync-ecosystem-data

sync-ecosystem-data

Verified

Pull meeting transcripts, email threads, and calendar activity into /raw/ecosystem and index in /wiki. Use when syncing ecosystem data or as part of /data-ingestion.

FileKindSize
SKILL.mdskill md1.7 KB
---
name: sync-ecosystem-data
description: 'Pull meeting transcripts, email threads, and calendar activity into /raw/ecosystem and index in /wiki. Use when syncing ecosystem data or as part of /data-ingestion.'
---

# Sync Ecosystem Data

Pipeline skill: pull personal-ecosystem signals into the knowledge base so the
system learns operational patterns. Runs standalone or as step 2 of
`/data-ingestion`.

## Sources

Use whichever connectors are available this session (check with `ToolSearch`);
skip silently any that aren't connected:

| Signal | Tool |
|--------|------|
| Meeting notes/transcripts | Notion `notion-query-meeting-notes`, Google Drive search |
| Email threads (non-newsletter) | Gmail `search_threads` — recent important threads |
| Schedule patterns | Google Calendar `list_events` — past 7 days |
| Document activity | Google Drive `list_recent_files` |

## Process

1. **Find the last sync point.** Read `raw/ecosystem/.last-sync`; default to
   7 days ago if missing.
2. **Pull and digest.** For each available source, fetch items since the sync
   point and extract only decisions, commitments, deadlines, recurring
   contacts, and operational patterns — not full bodies. Never store
   credentials, financial details, or obviously sensitive personal content;
   summarize around them.
3. **Write digests.** One file per source with content:
   `raw/ecosystem/YYYY-MM-DD_<source>.md` (e.g. `2026-07-12_meetings.md`).
   Skip sources with nothing new.
4. **Index.** Add one row per written file to the **Ecosystem Data** table in
   `wiki/index.md`.
5. **Update the sync point** in `raw/ecosystem/.last-sync`.
6. **Report.** Sources synced, sources skipped (and why), notable patterns.
   If run from `/data-ingestion`, keep this to 3 lines.
planning-and-task-breakdownaddyosmani/agent-skillsBreaks work into ordered tasks. Use when you have a spec or clear requirements and need to break work into implementable tasks. Use when a task feels too large to start, when you need to estimate scope, or when parallel work is possible.Stars: 119kUpdated Claude CodeCodexVerifiedInstall
screenpipethedotmack/claude-memSearch screen and audio history recorded by Screenpipe and optionally save selected context into claude-mem. Use when the user asks to recall desktop activity, a meeting, or something seen in another app through Screenpipe.Stars: 118kUpdated Claude CodeCodexVerifiedInstall
contact-widgetnexu-io/open-designSelf-contained floating chat widget with welcome screen, social links, meeting button, and message input. Single HTML file, zero dependencies.Stars: 108kUpdated Claude CodeCodexVerifiedInstall
meeting-notesnexu-io/open-designMeeting notes page — title bar with attendees, agenda checklist, decisions block, action items table with owners + dates, and a "next meeting" footer. Use when the brief mentions "meeting notes", "minutes", "1:1 notes", "all-hands recap", or "会议纪要".Stars: 108kUpdated Claude CodeCodexVerifiedInstall