project-lit-map

To generate a literature map, the skill reads markdown paper notes from your sources directory, groups them by themed categories using project frontmatter tags, and writes a structured literature-map.md file into your project folder.

Frontmatter filtering works by reading the project ID assigned in each paper note's frontmatter metadata, matching those tags against the target project, and organizing the matched papers into coherent thematic groups within the literature map.

Yes, you can update an existing literature map without duplicates by running an incremental update workflow that scans for newly added papers and appends them to the existing themes, preserving your current project-specific annotations.

You need a vault folder structure with a 20-Sources/papers directory containing your markdown paper notes and a 10-Projects directory where the generated project-scoped literature-map.md file will be created or updated.

The best way to organize research papers by theme is to tag paper notes with a project ID in their frontmatter, allowing the automation to extract metadata like authors and year, group them thematically, and link them directly to the project folder.

No, the literature map generation does not overwrite existing project annotations because the incremental update workflow is designed to add new papers to the map while preserving the annotations and links already present in the file.