agentleFS
couzipcouzip/cc-forever/skills/delete-memory/SKILL.md

delete-memory

Skill2 starsChanged 10 months agoApache-2.0View on GitHub

Delete memories from the index. Supports deletion by IDs, project, timestamp, or all.

The file

We split this skill into the rules it gives an agent

5 rules. About 0 are common, 1 is distinctive, and 4 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 4

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Delete memories from the persistent index.

    line 10
  2. Very specific:

    If $ARGUMENTS contains "all": delete all memories (confirm first)

    line 27
  3. Very specific:

    If $ARGUMENTS starts with "project:": extract project name

    line 28
  4. Very specific:

    If $ARGUMENTS starts with "before:": extract timestamp

    line 29
  5. Very specific:

    Call mcp__cc-forever-mcp__delete_memory with appropriate parameters:

    line 38

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Delete Memories

Delete memories from the persistent index.

Arguments

  • all - Delete all memories
  • project:<name> - Delete all memories for a specific project
  • before:<timestamp> - Delete memories before an ISO timestamp (e.g., before:2025-01-01)
  • <id1> <id2> ... - Delete specific memory IDs

Arguments: $ARGUMENTS

Steps

1. Parse Arguments

Determine the deletion mode:

  • If $ARGUMENTS contains "all": delete all memories (confirm first)
  • If $ARGUMENTS starts with "project:": extract project name
  • If $ARGUMENTS starts with "before:": extract timestamp
  • Otherwise: treat as space-separated IDs

2. Confirmation for Destructive Operations

For all or project: deletions, warn the user about the scope of deletion.

3. Execute Deletion

Call mcp__cc-forever-mcp__delete_memory with appropriate parameters:

For all:

{
  "all": true
}

For project:

{
  "project": "<project-name>"
}

For before timestamp:

{
  "before": "<ISO-timestamp>"
}

For specific IDs:

{
  "ids": ["<id1>", "<id2>", ...]
}

4. Report Results

Display the deletion result:

Deletion completed:
- Deleted: {deleted_count} memories
- Criteria: {criteria used}

5. Show Updated Stats

Optionally call get_stats to show the remaining memory count.

Examples

  • /cc-forever:delete all - Delete all memories
  • /cc-forever:delete project:my-app - Delete all memories for "my-app" project
  • /cc-forever:delete before:2025-01-01T00:00:00Z - Delete memories before 2025
  • /cc-forever:delete 2025-01-15T10:30:00.000Z-0 2025-01-15T10:30:00.000Z-1 - Delete specific IDs

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.