Agent skill · writing content · affaan-m
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.
Why this skill is useful
Provides a structured workflow for knowledge management that includes specific ingestion and deduplication processes not commonly found in general knowledge management practices.
What it needs
About 4k tokens when loaded. Last updated 2026-08-06. 238,342 stars on the source repository.
What this skill does
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 Rule: if something affects an active engineering plan, roadmap, rollout, or release, prefer putting it here first Layer 2: Claude Code Memory (Quick Access) Path: ~/.claude/projects//memory/ Format: Markdown files with frontmatter Types: user preferences, feedback, project context, reference Use for: quick-access context that persists across conversations Automatically loaded at session start Layer 3: MCP Memory Server (Structured Knowledge Graph) Access: MCP memory tools (createentities, createrelations, addobservations, searchnodes) Use for: Semantic search across all stored memories, relationship mapping Cross-session persistence with queryable graph structure Layer 4: Knowledge base repo / durable document store Use for: curated durable notes, session exports, synthesized research, operator memory, long-form docs Rule: this is the preferred durable store for cross-machine context …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills affaan-m/knowledge-ops--e5bcc9