platform-sync

Automate cross-platform synchronization of Claude Life OS instances across Code, Desktop, Web, and iOS.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/dabrewskie/owens-lifeos --skill platform-sync
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: platform-sync
Source: https://github.com/dabrewskie/owens-lifeos/tree/main/skills/_archive/platform-sync
Command: npx skills add https://github.com/dabrewskie/owens-lifeos --skill platform-sync

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Cross-platform synchronization across Claude instances (Code, Desktop, Web, iOS) to keep operational context in sync, including automated briefing packet generation, COP updates to Notion, session logs, action items, and repository sync.

Core Features & Use Cases

  • Automates briefing packet generation and distribution across platforms.
  • Pushes COP and session data to Notion and tracks action items.
  • Syncs local skill/agent repos to GitHub and maintains cross-platform consistency.

Quick Start

Run the platform-sync workflow to refresh all Claude contexts and propagate updates across the stack.

Frequently Asked Questions about platform-sync

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automate cross-platform synchronization for Claude Life OS across Code, Desktop, Web, and iOS?

Cross-platform synchronization for Claude Life OS is automated by orchestrating briefing packet generation, COP updates to Notion, session logs, action items, and repo synchronization across Code, Desktop, Web, and iOS environments.

What is the best way to sync Claude session logs and action items to Notion and GitHub?

Syncing session logs and action items to Notion and GitHub is handled by a workflow that pushes COP updates to Notion pages, syncs local repositories to GitHub, and reports status with staleness checks.

How does briefing packet generation work for Claude instances?

Briefing packet generation works by reading COP.md, PROFILE.md, CLAUDE.md, and HISTORY.md files to generate BRIEFING_PACKET.md, which propagates operational context across Claude instances.

Do I need specific environment files to run Claude Life OS synchronization?

You need COP.md, PROFILE.md, CLAUDE.md, and HISTORY.md files present in your environment to generate briefing packets and execute the cross-platform synchronization workflow successfully.

Can I use this to sync local skill and agent repositories to GitHub?

Yes, you can sync local skill and agent repositories to GitHub to maintain cross-platform consistency, while simultaneously propagating session data and action items to Notion.

Why does my Claude Life OS operational context show staleness across platforms?

Operational context staleness occurs when cross-platform synchronization has not been run to refresh Claude contexts, propagate updates, and perform staleness checks across the stack.