Importing from a Markdown folder

When to use

The generic fallback for any folder of Markdown + YAML frontmatter that isn't a recognized app — a Zettlr project, a static-site content dir, a hand-rolled export, or the Markdown output of an app's exporter (Bear, Apple Notes, Craft, OneNote). You own it end to end. Read limestone-vault-conventions, working-with-collections, and importing-from-obsidian (the exact same mapping) first.

Run the import (one tool call)

Call limestone_import_notebook(path, collection_name) with the folder (or a .zip of it). Returns the usual summary + unconverted list.

What the tool does

Identical to importing-from-obsidian: each .md → a record; frontmatter created/updated/author/source/aliases → properties; tags: + inline #tags → real tags; ![[...]]/![](...) attachments copied beside the note; [[links]] pass through; any other frontmatter key preserved back into the note's YAML.

Finalizing (your job)

The importing-from-obsidian playbook applies verbatim: promote preserved frontmatter, retype properties, split/rename if one folder holds several record types, and resolve unconverted items (unsupported attachment types, unresolved embeds).

Evolving this skill

If a particular exporter's Markdown recurs with the same problems, consider giving it its own importing-from-<app> skill (and, if the structure needs code, an adapter on importers/markdown_folder.py). Keep skill and importer in sync.