knowledge-ops
Knowledge base management, ingestion, sync, and retrieval across multiple storage layers (local files, MCP memory, vector stores, Git repos). Use when the user wants to save, organize, sync, deduplicate, or search across their knowledge systems.
- Kind
- Skill
- Works with
- Claude Code, Codex
- Source
- affaan-m/ECC @ d3b8a3e90890
- Path
- skills/knowledge-ops/SKILL.md
- License
- MIT
- Jobs
- Context management, Git workflow
InstallCopy it from the source repository, or sign in and let the assistant adapt it for your project.
# Knowledge Operations Manage a multi-layered knowledge system for ingesting, organizing, syncing, and retrieving knowledge across multiple stores. Prefer the live workspace model: - code work lives in the real cloned repos - active execution context lives in GitHub, Linear, and repo-local working-context files - broader human-facing notes can live in a non-repo context/archive folder - durable cross-machine memory belongs in the knowledge base, not in a shadow repo workspace ## When to Activate - User wants to save information to their knowledge base - Ingesting documents, conversations, or data into structured storage - Syncing knowledge across systems (local files, MCP memory, Supabase, Git repos) - Deduplicating or organizing existing knowledge - User says "save this to KB", "sync knowledge", "what do I know about X", "ingest this", "update the knowledge base" - Any knowledge management task beyond simple memory recall ## Knowledge Architecture ### Layer 1: Active execution truth - **Sources:** GitHub issues, PRs, discussions, release notes, Linear issues/projects/docs - **Use for:** the current operational state of the work …