context-bridge
跨 Claude、Cursor 和 Factory Droid 会话同步任务状态和元数据。在平台之间移交任务、共享计划或更新 Linear 或 Jira 等外部跟踪器时使用。
📖 中文导读:跨 Claude、Cursor 和 Factory Droid 会话同步任务状态和元数据。在平台之间移交任务、共享计划或更新 Linear 或 Jira 等外部跟踪器时使用。 以下正文为该技能的原始 SKILL.md 内容(英文),上方安装命令可直接使用。
name: context-bridge version: 1.0.0 description: 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. allowed-tools: linear_read, linear_write, github_read, github_write, slack_write
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. - 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 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//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. - **Linear**: Read/Write issues. - **GitHub**: Read repo context, update PRs/Issues. - **Slack**: Send notifications to team channels.- 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.jsonbefore syncing - Handle publishing status conflicts by preferring most recent
published_attimestamp - Preserve
publish_attemptshistory for retry tracking - Update
last_syncedtimestamp to track sync freshness - If metadata conflicts, log conflict resolution in reasoning file
- Validate metadata against