sync-context

Sync local learnings with a global knowledge base across projects.

Updated Mar 20, 2026
One-click install
npx skills add https://github.com/dynamic-dome/agentic-os --skill sync-context-dynamic-dome
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: sync-context
Source: https://github.com/dynamic-dome/agentic-os/tree/main/skills/sync-context
Command: npx skills add https://github.com/dynamic-dome/agentic-os --skill sync-context-dynamic-dome

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill helps manage knowledge transfer between different projects, ensuring that learnings and patterns are not siloed within a single project.

Core Features & Use Cases

  • Cross-Project Sync: Manually sync local learnings with a global knowledge base for reuse.
  • Privacy and Gate: Ensures privacy by filtering and requiring a promotion gate for sharing.
  • Use Case: If you have multiple projects and want to share successful patterns or learnings with other projects without automatically syncing them.

Quick Start

Run /agentic-os:sync-context to manually sync your local learnings with the global knowledge base.

Frequently Asked Questions about sync-context

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

FAQPage Schema
How do I sync local learnings with a global knowledge base across multiple projects?

Knowledge management prevents project silos by applying privacy filters and promotion gates during cross-project sync. This ensures sensitive information remains protected while allowing successful patterns to be verified before sharing them globally.

How do I manually initiate cross-project sync for pattern sharing?

Cross-project sync requires explicit user initiation to transfer learnings to the global knowledge base. This manual approach prevents unintended data leakage, ensuring you review and validate all patterns before they are shared.

How does the promotion gate work when sharing patterns between projects?

A promotion gate filters local learnings and requires explicit approval before sharing them with the global knowledge base. This mechanism ensures privacy checks are passed and sensitive information is excluded from cross-project sync.

Can I automatically sync knowledge across projects without manual initiation?

No, this approach requires explicit user initiation to prevent unintended data exposure during cross-project sync. Automatic syncing is intentionally avoided to ensure strict privacy checks and manual promotion gates govern all knowledge sharing.

When should I use manual cross-project sync instead of automatic syncing?

Use manual sync when managing multiple projects where privacy control over local learnings is critical. It prevents automatic data leaks by requiring explicit user initiation and promotion gates before sharing patterns with the global knowledge base.