Use this skill whenever the user wants to process, refine, or organize their quick notes. This includes: batch processing today's (or any date's) quick notes, refining rough notes into polished permanent notes, deciding where notes should be routed in the vault, splitting multi-topic notes for atomicity, archiving originals, generating daily processing summaries, or checking if any notes warrant new projects (calls elevatio). Activate for /purgatio. Also activate when users mention 'quick notes' (퀵 노트) needing processing, refinement, or organization — in any language including Korean (e.g., '퀵 노트 처리해줘', '오늘 노트 정리'). Key signals: 'process notes', 'refine notes', 'quick notes', 'daily summary', 'daily processing', or any request involving tidying up rough/raw notes captured throughout the day.
Purgatio (Latin): purification, cleansing, refinement
Skill for processing daily quick notes into permanent assets.
| Type | Characteristic | Processing | Latin Callouts |
|---|---|---|---|
| User-written | No callouts | purgatio (context parsing) | Not needed |
| AI/External-based | Latin callouts | purgatio detects → commentatio | Required |
Flow: indagatio output → user adds Latin callouts → purgatio detects → calls commentatio
Batch (all notes for date):
/purgatio, /purgatio 2025-10-15Interactive (user selects):
/purgatio --selectSingle note:
/purgatio "keyword", /purgatio 새 스킬| Mode | Trigger | Flow |
|---|---|---|
| A: Full Processing | User direct (/purgatio) | Quick notes → Refinement → Archive → Daily Note |
| B: Report-Only | Other skills (elevatio, unio, memorio, commentatio) | Receive data → Append to Daily Note Activity Log |
See references/skill-report-format.md for report format.
Detect Latin callouts ([!quaero], [!emendo], [!disco], [!facio], [!moneo], [!cogito]) during quick note processing.
Regex: >\s*\[!(quaero|emendo|disco|facio|moneo|cogito)\]
Rule: ANY single Latin callout → call commentatio → include synthesis in Daily Note report.
Mixed content: Note can have regular content AND Latin callouts. Purgatio processes entire note, commentatio extracts callouts separately. Standard Obsidian callouts ([!note], [!warning], etc.) do NOT trigger.
Edge cases: Empty callout still triggers (ask user to clarify). Nested callouts both processed. Callout inside code block NOT detected.
See ../_common/references/vault-structure.md for full structure.
See ../_common/references/frontmatter-standard.md for status taxonomy and field standards.
Key Paths:
00. INBOX/01. Quick Notes/notes/00. INBOX/01. Quick Notes/archive/50. PROJECTS/51. Active/60. JOURNAL/61. Daily Reviews/70. CREATIONS/72. Essays/Always use date "+%Y-%m-%d %H:%M" — never guess time.
Run BEFORE any note processing. Never skip.
61. Daily Reviews/YYYY/MM/YYYY-MM-DD.md
references/daily-summary-format.md)- [ ] tasks
references/task-carry-over.md)### 🔄 Carried Over section> [!info] No incomplete tasks from yesterday- [ ] #task/hobby Purgatio 처리This step takes <30 seconds. No excuse to skip.
Filename pattern: 2026.01.04-14h30m Title
| Mode | Trigger | Behavior |
|---|---|---|
| Batch (default) | /purgatio, /purgatio 2025-10-20 | All notes for date |
| Interactive | /purgatio --select | User selects from numbered list |
| Single | /purgatio "keyword" | Filter by keyword, ask if ambiguous |
Optimization: Parallel Read all selected notes in one message. For incremental runs, skip already-archived files.
See references/staleness-detection.md for full logic.
Action words trigger detection → AI extracts context → Search activity logs → User confirms (Skip/Process/Review). On skip: archive with superseded: true.
See references/atomicity-check.md for detailed criteria.
Detection patterns: Topic transition signals ("and", "also"), mixed projects Action: If split needed, confirm with user before splitting
Title Rules:
r{##}. {Content Title} format
r = refined prefix{##} = sequential number (01, 02, 03...)2026-01-04 Arduino LogArduino Log 01 (no prefix)r01. Arduino Setup Guider02. Work and Hobby BoundariesProject Folder Structure:
project/
├── README.md
├── notes/ ← Reference materials, guides (things to READ)
├── refined/ ← Processed thoughts → outputs (my WRITINGS)
├── logs/ ← Simple records (what I DID)
└── scripts/ ← Code files
Location Decision:
See references/destination-guide.md for full routing logic and destination map.
Quick Reference:
{project}/refined/70. CREATIONS/72. Essays/20. LITERATURE/30. KNOWLEDGE/{domain}/ (see vault-structure.md for domain classification)10. INCUBATING/11. Ideas/When to call elevatio (new project creation):
New Project Criteria (should meet most):
용어 영어 병기: 한국어 작성 시 기술 용어에 용어 (English term) 형식 적용 (see CLAUDE.md Foreign Term Notation).
Common Processing:
Difficulty Assessment (during refinement):
When creating the refined version, assess and set difficulty: 1-10:
difficulty: → inherit (adjust ±1 if refinement changes complexity)Add difficulty: {value} to refined note frontmatter.
Image Detection (auto):
See references/image-detection.md for keywords and format.
[!image-needed] placeholderMeeting Notes → Route based on project association
See references/meeting-brief-format.md for detailed format and structure.
| Meeting Type | Destination | Examples |
|---|---|---|
| Project-specific | {project}/refined/ | 프로젝트 피드백, 기술 미팅 |
| Series/recurring | 65. Meeting Records/post/ | 팀 정기회의, All Hands |
| No project yet | 65. Meeting Records/post/ | 외부 미팅, 아키텍처 리뷰 |
| Pre-meeting prep | 65. Meeting Records/pre/ | 미팅 브리프, 준비 자료 |
Key rules:
refined/ folder (follow rXX naming)65. Meeting Records/post/## 🏠 Project Home) + README 역링크logs/meetings-index.md (master), logs/{series}.md (recurring)Bidirectional linking required:
## Source\n- Original: [[original title]]## Purgatio\n- Refined: [[refined title]]Cross-project linking: Keep note in primary project (whose capability is exercised), add bidirectional wikilinks to related projects' READMEs. If ambiguous → ask user.
See references/verification-checklist.md. Runs AFTER refinement, BEFORE archiving.
3 phases: A. Duplicate Check → B. Fact Check → C. Correction. Intensity: opinion=Light, technical=Standard, indagatio=Deep, meeting=Light. Always check: similar note exists? wikilinks valid?
Move (never delete) to archive/. Process: patch status: archived → append Purgatio section → move. See references/archive-format.md.
6a. Project-Related: Create in refined/ (NOT notes/). Reflect actionable ideas back into project notes/README (methodology→phase note, prerequisites→README curriculum, references→wikilinks). Raw reasoning stays only in refined/.
6b. Reflection/Personal: Refine to essay → 70. CREATIONS/72. Essays/. See references/destination-guide.md.
7a. Mark purgatio task complete:
- [x] #task/hobby Purgatio 처리 — N건 처리 완료
7b. Add Processing Summary to ## 📊 Daily Processing Summary section.
See references/daily-summary-format.md for format.
7c. Add Key Insights to ## 🧠 Thoughts & Ideas section.
Extract 1-3 insights per refined note created.
Central Log: Record processing details in 90. SYSTEM/96. Data/Log-00-Processing.md
Location-Based Log: Additionally log to destination-specific location:
| Destination | Log Location |
|---|---|
50. PROJECTS/51. Active/{project}/ | {project}/logs/activity.md |
10. INCUBATING/ | 90. SYSTEM/96. Data/Log-10-Incubating.md |
20. LITERATURE/ | 90. SYSTEM/96. Data/Log-20-Literature.md |
30. KNOWLEDGE/ | 90. SYSTEM/96. Data/Log-30-Knowledge.md |
70. CREATIONS/ | 90. SYSTEM/96. Data/Log-70-Creations.md |
Create log file if not exists (see ../_common/references/logging-standard.md).
See references/log-format.md for format.
Important: Do NOT delete. Move to Archive only.
All skill activities flow through purgatio (report-only mode) to Daily Note:
Any Skill → purgatio(report_only) → Daily Note Activity Log
references/destination-guide.md - Routing logic and destination mapreferences/log-format.md - Global and per-project log formatreferences/daily-summary-format.md - Daily note summary formatreferences/staleness-detection.md - Stale note detection logicreferences/atomicity-check.md - Atomicity validation criteriareferences/meeting-brief-format.md - Meeting document formatreferences/archive-format.md - Archive formatreferences/verification-checklist.md - Duplicate & fact-check workflow (Step 4b)references/task-carry-over.md - Task carry-over logic../_common/references/vault-structure.md - Vault structure../_common/references/frontmatter-standard.md - Frontmatter standards../_common/references/logging-standard.md - Unified logging standard (v1.3.0)