# Context Bridge

> Synchronize task state and metadata across Claude, Cursor, and Factory Droid sessions. Use when handing off tasks between platforms, sharing plans, or updating external trackers like Linear or Jira.

- Skill: `majiayu000/context-bridge` (Agent Skill, multi-file: 2 files)
- Install (CLI): `npx skillmds add majiayu000/context-bridge`
- Raw SKILL.md: https://api.skillmd.com/api/skills/majiayu000/context-bridge/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Productivity
- Author: majiayu000 (https://skillmd.com/u/majiayu000)
- Updated: 2026-09-09
- Page: https://skillmd.com/skills/majiayu000/context-bridge

---


<identity>
Context Bridge - Synchronizes task state and metadata across Claude, Cursor, and Factory Droid sessions. Ensures "memory" is preserved when switching between different AI agents or platforms.
</identity>

<capabilities>
- Synchronizing task state and metadata across platforms
- Handing off tasks between platforms
- Sharing plans and updating external trackers (Linear, Jira)
- Preserving context when switching AI agents
</capabilities>

<instructions>
<execution_process>
1. **Identify Handoff**: When a user indicates they are switching platforms (e.g., "I'll finish this in Cursor"), invoke this skill.
2. **Persist State**: Save the current plan, active artifacts, and next steps to `.claude/context/state.json`.
3. **Sync Publishing Metadata**: 
   - Read artifact registry from source platform (e.g., `.claude/context/runs/<run_id>/artifact-registry.json`)
   - Extract publishing metadata (published, published_at, publish_status, publish_targets, publish_attempts)
   - Validate metadata against `.claude/schemas/artifact-metadata.schema.json`
   - Sync to target platform (e.g., `.cursor/plans/artifacts/` or `.factory/context/artifacts/`)
   - Handle conflicts: prefer most recent `published_at` timestamp
   - Update `last_synced` timestamp in metadata
4. **Update Trackers**: If a ticket ID is present, update the external status (Linear/GitHub).
5. **Notify**: Send a summary to the appropriate channel if requested.
</execution_process>

<integrations>
- **Linear**: Read/Write issues.
- **GitHub**: Read repo context, update PRs/Issues.
- **Slack**: Send notifications to team channels.
</integrations>

<best_practices>

- **Always** update the central state file before sending notifications.
- **Never** overwrite existing state without reading it first to preserve history.
- **Publishing Metadata Sync**: When syncing artifacts across platforms:
  - Validate metadata against `.claude/schemas/artifact-metadata.schema.json` before syncing
  - Handle publishing status conflicts by preferring most recent `published_at` timestamp
  - Preserve `publish_attempts` history for retry tracking
  - Update `last_synced` timestamp to track sync freshness
  - If metadata conflicts, log conflict resolution in reasoning file
    </best_practices>
    </instructions>