← ClaudeAtlas

moldavite-forgeslisted

Navigate and safely edit Moldavite Forge directories, including daily, weekly, standalone, nested, image, template, locked, and app-managed paths. Use when an agent has filesystem access to a Moldavite Forge, needs to choose a note path, or must edit notes without MCP.
mauropereiira/moldavite-skills · ★ 1 · Data & Documents · score 80
Install: claude install-skill mauropereiira/moldavite-skills
# Moldavite Forges A Forge is a user-owned directory of Markdown notes. Prefer Moldavite MCP tools when connected because they enforce Forge paths, locks, and write permissions. Use direct files only when MCP is unavailable or the task explicitly requires filesystem work. ## Discover the Forge 1. Use the Forge path supplied by the user or current project context. 2. Default roots commonly live under `~/Documents/Moldavite/<Forge name>/`. 3. If multiple Forges could match, ask which one to use. Do not infer from note titles. 4. Read root `AGENTS.md` before reading or changing notes. Its privacy, naming, and content rules take precedence. ## Layout ```text <Forge>/ |-- AGENTS.md |-- daily/ # YYYY-MM-DD.md |-- weekly/ # YYYY-Www.md |-- notes/ # standalone notes; nested folders allowed |-- templates/ # Moldavite-managed JSON templates |-- images/ # note attachments |-- .trash/ # app-managed |-- .plugins/ # app-managed `-- .index/ # derived semantic index ``` Use full Forge-relative paths when discussing or using MCP notes: ```text daily/2026-07-27.md weekly/2026-W31.md notes/project-plan.md notes/Projects/project-plan.md ``` Daily and weekly notes stay flat. Nest only under `notes/`. ## Safety Rules - Never read or edit `*.md.locked` files. Their plaintext is intentionally unavailable. - Never edit `.trash/`, `.plugins/`, `.index/`, hidden files, or tempo