Skip to content
Agentmart
Submit a tool

db-maintenance

Skill for maintaining the health and performance of the Mnemosyne redb-based semantic database and content-addressable storage (CAS).

Skill by alessandrobrunoh

IndexedApache-2.0★ 11
Write a review

Install

Works with Claude Code, Claude apps, Codex, Cursor, Gemini CLI, GitHub Copilot, VS Code, OpenCode, Goose, Windsurf. Read the repository before you give any tool access to your data.

npx agentmarket install skill/alessandrobrunoh-db-maintenance

Asks which of your tools to add it to (Claude Code, Codex, Cursor, VS Code, Windsurf, Gemini CLI, Claude Desktop) and shows the change first. See https://agentmart.dev/cli.

Get the weekly diff

The weekly diff: one email a week with new agent tools, notable updates and grade changes, plus security alerts for tools you follow. Double opt-in, one-click unsubscribe.

We use your email only for this newsletter. Privacy

About

Skill for maintaining the health and performance of the Mnemosyne redb-based semantic database and content-addressable storage (CAS).

Use cases: backend, writing

No reviews yet. Installed it? Reviews come from verified installers only. How reviews work

Permissions

What this skill can do and what it asks for, from its SKILL.md. Checked Oct 25, 2026.

Tools
No tools found
Secrets
None asked for
Install scripts
None found

Network hosts it talks to 1

  • codeload.github.com · found in install command

Files it touches

  • ~/.claude/skills/db-maintenance

What's inside

Skill name
db-maintenance
Description
Skill for maintaining the health and performance of the Mnemosyne redb-based semantic database and content-addressable storage (CAS).
License
Apache-2.0
Instructions
20 lines in SKILL.md · view on GitHub

Files (1)

  • SKILL.md

SKILL.md (first lines)

# Database Maintenance Instructions

When this skill is active, you are a "Database Administrator". Your goal is to ensure the long-term integrity and efficiency of Mnemosyne's storage layer.

## Procedures

1. **Health Check**: Use `mnem status --json` to monitor `history_size_bytes` and snapshot/symbol counts.
2. **Optimization**: Use `mnem gc --json` to perform periodic garbage collection and remove orphaned chunks from the CAS.
3. **Consistency**: Verify that all snapshots in the database have corresponding data in the `cas/` filesystem.

## Tools (CLI Commands)
- `mnem gc --keep <count> --json`: Retain a specific number of snapshots while pruning the rest.
- `mnem status --json`: View storage-specific metrics.

## Rules
- Always perform a `mnem gc --dry-run --json` before a real pruning operation to avoid data loss.
- Never prune snapshots from the "Active Branch" of a project unless explicitly requested.
- Prioritize high-frequency pruning for massive project histories.

From alessandrobrunoh/Mnemosyne, Apache-2.0.

Signals

Stars
11
Forks
1
Open issues
0
Last commit (this folder)
Mar 10, 2026 (7 months ago)
Last release
Mar 8, 2026 (7 months ago)

From GitHub (fetched Oct 24, 2026).

Details

License
Apache-2.0
First seen
Oct 24, 2026
Last checked
Oct 24, 2026

More from alessandrobrunoh

Cite this page

db-maintenance skill. Agent Mart. https://agentmart.dev/skills/alessandrobrunoh-db-maintenance (last updated 2026-10-24)