kratos-memory

Category: Development & Coding | Uploader: ceorkm | Downloads: 0 | Version: v1.0（Latest）

Save, search, and manage persistent memories across coding sessions. Use when the user asks to remember something, recall past work, or search their memory.

Changelog: Source: GitHub https://github.com/ceorkm/kratos-mcp

Directory Structure

Current level: plugin/skills/kratos-memory/

📄 SKILL.md 1.7 KB

SKILL.md

---
name: kratos-memory
description: Save, search, and manage persistent memories across coding sessions. Use when the user asks to remember something, recall past work, or search their memory.
---

# Kratos Memory

You have access to a persistent memory system via the `kratos` CLI. Use it to save important observations and recall past decisions.

## When to save memories

- Architecture decisions ("we chose X because Y")
- Bug fixes ("fixed Z by doing W")
- File/component relationships ("auth logic lives in src/auth/")
- User preferences and project conventions
- Important discoveries about the codebase

## Commands

### Save a memory
```bash
kratos save "description of what happened" --tags tag1,tag2 --importance 3 --paths file1.ts,file2.ts
```
- `--tags`: comma-separated tags for categorization
- `--importance`: 1-5 (5 = critical, 3 = default)
- `--paths`: related file paths
- `--compress`: compress before saving

### Search memories
```bash
kratos search "query terms"
kratos search "auth" --tags backend --debug
```

### Ask natural language questions
```bash
kratos ask "what do I know about the database schema?"
```

### Get recent memories
```bash
kratos recent --limit 10
```

### Get full memory details
```bash
kratos get <memory-id>
```

### Delete a memory
```bash
kratos forget <memory-id>
```

### Check system status
```bash
kratos status
```

### Scan for PII/secrets
```bash
kratos scan "text that might contain secrets" --redact
```

## Guidelines

- Save memories with relevant tags so they're findable later
- Use importance 4-5 for architecture decisions and critical fixes
- Use importance 1-2 for routine observations
- Always include file paths when the memory relates to specific files
- Keep summaries concise but preserve technical terms

Comments 0

Latest | Hot

Please login before commenting.

No comments yet. Be the first one!

kratos-memory

Directory Structure

SKILL.md

Report

Notice