Knowledge Ops

This is a multi-layered knowledge management system that routes information to the right place: active work goes to GitHub and Linear, quick-access context lives in Claude Code memory files, semantic relationships go into an MCP memory graph, and durable notes land in a knowledge base repo. It handles ingestion, deduplication, and sync across all these layers. The architecture is opinionated about separating execution truth from reference material, which prevents the common mess of having the same information scattered across local notes, repo files, and issue trackers. Useful when you're tired of re-explaining context or losing track of decisions across tools.

skills.sh installs: 5.4K
GitHub stars: 300.3K
last updated: Aug 21, 2026

View on GitHub

Install

$ npx -y skills add affaan-m/ecc --skill knowledge-ops --agent claude-code

Installs into .claude/skills of the current project.

Files

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