ke

Extract and route knowledge from work sessions to memory packs and repositories.

44|125|Updated Feb 10, 2026
One-click install
npx skills add https://github.com/TserenTserenov/FMT-exocortex-template --skill ke
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ke
Source: https://github.com/TserenTserenov/FMT-exocortex-template/tree/main/.claude/skills/ke
Command: npx skills add https://github.com/TserenTserenov/FMT-exocortex-template --skill ke

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Knowledge scattered across work sessions is hard to reuse. This Skill automates extraction of salient knowledge patterns and routes them into memory packs and domain repositories, enabling faster reuse and better decision-making.

Core Features & Use Cases

  • Extracts and classifies knowledge from notes, decisions, and task outcomes.
  • Routes captures to CLAUDE.md (root workspace memory), Packs for domain knowledge, or DS docs for architectural guidance.
  • Use Case: after completing a task, capture the lesson learned and route it for future reference and automation.

Quick Start

Run knowledge extraction on the latest session log to generate a new capture and route it to the appropriate Pack.

Frequently Asked Questions about ke

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

FAQPage Schema
How do I automate knowledge extraction from work session logs?

Automate knowledge extraction by processing session logs to identify salient patterns, decisions, and domain knowledge, then routing them into memory packs and repositories for reuse.

What is the best way to route captured domain patterns to memory packs?

Route captured domain patterns by applying decision rules to classify knowledge types and direct them to CLAUDE.md, domain packs, or DS docs for architectural guidance.

How do I capture and classify decisions from task outcomes for future reference?

Capture and classify decisions from task outcomes by running extraction on session logs to identify lessons learned, then routing the captures to correct destinations for review.

Can I use this to extract knowledge across multiple repositories?

Yes, you can extract and route knowledge across repositories and domain packs, applying patterns and decision rules to ensure captures reach the correct destination for reuse.

When do I need to route captures to CLAUDE.md versus domain packs?

Route captures to CLAUDE.md for root workspace memory, domain packs for domain-specific knowledge, or DS docs for architectural guidance, based on the identified knowledge type.

What are the limitations of automating knowledge capture from session logs?

Knowledge capture relies on identifying salient patterns and routing them via decision rules; results still require review, and the process depends on the quality of session log inputs.