knowledge-ops

Organizes, syncs, and retrieves knowledge across memory files, MCP memory, Git repos, and external data stores.

Updated May 19, 2026
One-click install
npx skills add https://github.com/azusagasaku/--claude-config --skill knowledge-ops-azusagasaku
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: knowledge-ops
Source: https://github.com/azusagasaku/--claude-config/tree/main/skills/ecc/knowledge-ops
Command: npx skills add https://github.com/azusagasaku/--claude-config --skill knowledge-ops-azusagasaku

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Knowledge scattered across local files, chat sessions, GitHub, Linear, and databases becomes hard to find and easy to duplicate. This Skill provides a structured workflow for ingesting, deduplicating, syncing, and retrieving knowledge across multiple storage layers. ## Core Features & Use Cases - Multi-Layer Knowledge Architecture: Routes information to the right store, from Claude Code memory files and the MCP memory knowledge graph to GitHub/Linear, a knowledge base repo, and external stores like Supabase. - Ingestion Workflow: Classifies new knowledge by type, deduplicates against existing entries, stores it in the appropriate layer, and updates indexes. - Sync Operations: Syncs conversation sessions, workspace state, and cross-source exports (Claude/ChatGPT/Grok conversations, bookmarks, GitHub activity) into a durable knowledge base repo. - Use Case: After a long planning session, ask the assistant to save the key decisions to the knowledge base; it will classify each fact, check for duplicates, write memory files and MCP memory entities, and commit a session summary to the KB repo. ## Quick Start Save the key decisions from this conversation to my knowledge base and sync it with my existing memory.

Frequently Asked Questions about knowledge-ops

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

FAQPage Schema
How do I save information to a persistent knowledge base from a chat session?▼

Classify the information by type first, then store it in the matching layer: memory files for preferences and project context, MCP memory entities for structured facts, and a knowledge base Git repo for durable long-form notes. Always search for existing entries before creating new ones.

What is the difference between Claude Code memory files and MCP memory?▼

Claude Code memory files are Markdown files with frontmatter stored under ~/.claude/projects/*/memory/ and loaded automatically at session start for quick recall. MCP memory is a queryable knowledge graph supporting semantic search, entities, relations, and observations across sessions.

How do I avoid creating duplicate knowledge entries?▼

Search memory files and query MCP memory with relevant terms before storing anything new, and check GitHub or Linear for existing project truth. Update existing entries instead of creating duplicates, and keep one canonical home per fact set.

Can I sync conversation history from multiple AI tools into one knowledge base?▼

Yes, the cross-source sync workflow pulls exports from Claude, ChatGPT, and Grok sessions plus browser bookmarks and GitHub activity into a knowledge base repo. It generates a session index, writes a status summary, then commits and pushes.

What should I do before committing knowledge files to Git?▼

Redact sensitive information such as API keys and passwords before committing anything to Git. Also verify no duplicate entries were created, update indexes and summaries, and add cross-references where relevant.