IronScribe

Problem

IronScribe addresses scattered personal notes, inconsistent folder placement, unfaithful summaries, and the risk of accidental deletion. It does not invent new facts; it organizes user input into archivable Obsidian Markdown and confirms type, tags, and classification before writing.

How It Works

The skill uses master.json as the index entry point and loads modules/ on demand based on commands. The core workflow includes:

• Writing: extract the source text, generate a faithful summary, recommend a directory, and update the index;
• Querying: list, search, and complete parameters from recent-operation context;
• Editing: modify, delete, undo, and merge entries, with a trash flow to reduce deletion risk;
• Chunking: split, reorganize, and relink long documents;
• Audit: validate data, repair statistics, and rebuild the master index.

Cross-module operations run as a pipeline, attempt reverse rollback on failure, and return results through a unified JSON status contract.

Boundaries

It relies on local files and a defined directory layout, so it is not a fit for remote databases or complex permission systems. Unclear tags or classifications are marked as pending, and some commands are unavailable in pure JSON mode. Users must accept its constraints of no fabrication, faithful summarization, and mandatory confirmation.