Back to Skills

cortex-manage

verified

Manage memories - search, view, update, delete, rename projects

View on GitHub

Marketplace

cortex

hjertefolger/cortex

Plugin

cortex

memory

Repository

hjertefolger/cortex
148stars

skills/cortex-manage/SKILL.md

Last Verified

February 1, 2026

Install Skill

Select agents to install to:

Scope:
npx add-skill https://github.com/hjertefolger/cortex/blob/main/skills/cortex-manage/SKILL.md -a claude-code --skill cortex-manage

Installation paths:

Claude
.claude/skills/cortex-manage/
Powered by add-skill CLI

Instructions

# Memory Management

Help the user manage their Cortex memories.

## Capabilities

### Search and View Memories

Use `cortex_recall` to find specific memories:
- Search by content
- Filter by project
- View memory details

### Update Memory

Use `cortex_update` to edit a memory:
- Update content (will re-generate embedding)
- Move to different project
- Both at once

```
cortex_update(memoryId: 123, content: "corrected content")
cortex_update(memoryId: 123, projectId: "new-project")
```

### Rename Project

Use `cortex_rename_project` to move all memories from one project to another:
- Useful when project directory is renamed
- Bulk operation - moves all memories at once

```
cortex_rename_project(oldProjectId: "old-name", newProjectId: "new-name")
```

### Delete Specific Memory

Use `cortex_delete` to remove a memory fragment:
1. First call WITHOUT `confirm: true` to preview what will be deleted
2. Show the user the preview (content, project, timestamp)
3. Ask for explicit confirmation
4. If confirmed, call with `confirm: true` to delete

### Forget Project Memories

Use `cortex_forget_project` to delete all memories for a project:
1. First call WITHOUT `confirm: true` to get count
2. Show the user how many memories will be deleted
3. Ask for explicit confirmation
4. If confirmed, call with `confirm: true` to proceed

## Important Safety Rules

**ALWAYS follow these rules for destructive actions:**

1. **Preview First**: Always call the delete/forget tool without confirm first
2. **Show Impact**: Display exactly what will be affected
3. **Explicit Confirmation**: Ask user "Are you sure you want to delete X?"
4. **Never Assume**: Don't delete without explicit user approval
5. **Be Clear**: State what will be permanently lost

## Example Flows

### Updating a Memory

User: "Fix the typo in memory 42"

1. First recall to see the memory:
   ```
   cortex_recall(query: "...")
   ```

2. Update with corrected content:
   ```
   cortex_update(memoryId: 42, content: "corr

Validation Details

Front Matter
Required Fields
Valid Name Format
Valid Description
Has Sections
Allowed Tools
Instruction Length:
3335 chars