Organize raw notes into structured format using the standard template. Use when user wants to clean up, reorganize, or format notes and manage task workflows.
This skill automatically organizes raw notes into a structured format using the standard note template. It analyzes unstructured note content and reorganizes it into clean, properly formatted notes while managing task workflows across daily, weekly, and task files.
Transform unorganized note content into well-structured markdown files that follow the standard note template format, while maintaining a unified task management system that consolidates completed tasks in daily and weekly notes rather than a separate completed file.
tasks.md and propagates them to daily and weekly notes20-notes/21-tasks/tasks.md: Unified task file containing both active and completed tasks
- [ ] Task description- [X] Task description- [ ] in appropriate category in tasks.md- [X] in tasks.md20-notes/22-daily/YYYY-MM-DD.md) in "What I Did Today" section20-notes/23-weekly/YYYY-MM-DD.md) in appropriate section as a summarized entry with a date reference to the daily notecompleted.md fileWhen you receive a note that needs to be organized, analyze its content and restructure it according to the standard template format. When completing tasks, ensure they are:
tasks.mdInput Analysis: Review the raw note content provided
Content Categorization: Sort the content into appropriate template sections:
Template Formatting: Apply the standard note template structure with proper markdown formatting
Section Removal: Remove any sections that don't have content
Date and Tags: Extract date from context and organize tags appropriately
Task Extraction: Detect and extract tasks that need to be added to the task management system
task [text] or task: [text] in the note content20-notes/21-tasks/tasks.md in the appropriate category- [ ] in the task fileTask Completion: When marking a task as completed
- [X] in 20-notes/21-tasks/tasks.md20-notes/22-daily/YYYY-MM-DD.md) in the "What I Did Today" section with a clear, descriptive description20-notes/23-weekly/YYYY-MM-DD.md) in the appropriate section (e.g., Contributions, What I Did This Week, etc.) as a summarized entry using the format:
Task summary (see [YYYY-MM-DD](../22-daily/YYYY-MM-DD.md) for details)File Naming:
YYYY-MM-DD.md (e.g., 2026-02-19.md)YYYY-MM-DD.md (e.g., 2026-02-20.md for the week ending Thursday, February 20)YYYY-MM-DD-meeting-name.mdCross-File Synchronization: Every time content is added to daily notes:
- [ ] for uncompleted action items and - [X] for completed items[text](url) for referencestask or task:), add them to 20-notes/21-tasks/tasks.md under the appropriate category (default to "Onboarding" if unclear)completed.md fileInput: "task completed: Check PRU usage"
Output:
1. Mark in `20-notes/21-tasks/tasks.md`:
- [X] Check PRU usage
2. Add to today's daily note `20-notes/22-daily/2026-02-20.md` in "What I Did Today":
- Checked PRU usage
3. Add to today's weekly note with reference:
- Checked PRU usage (see [2026-02-20](../22-daily/2026-02-20.md) for details)
Input: "task: Follow up with engineering team about API limits"
Output:
1. Added to `20-notes/21-tasks/tasks.md`:
- [ ] Follow up with engineering team about API limits
Input Daily Note: "Created a skill to automatically download Change Log as PPT with robust template, multi-page RSS fetching..."
Output:
1. Mark in `20-notes/21-tasks/tasks.md`:
- [X] Create skill to automatically download Change Log as PPT
2. In daily note (full detailed explanation):
- Created skill to automatically download Change Log as PPT with robust template, multi-page RSS fetching, native Japanese translation, and visual categorization
3. In weekly note (summarized with reference):
- Created skill to automatically download Change Log as PPT with robust template, multi-page RSS fetching, native Japanese translation, and visual categorization (see [2026-02-20](../22-daily/2026-02-20.md) for details)
completed.md file is no longer used. All task completion history is maintained through daily and weekly notes.(see [YYYY-MM-DD](../22-daily/YYYY-MM-DD.md) for details) to link to daily notes with full explanations.20-notes/21-tasks/, 20-notes/22-daily/, 20-notes/23-weekly/All knowledge documents in 40-presentations/ are maintained in both English and Japanese using paired subfolders:
40-presentations/
├── 41-Copilot/
│ ├── 41.01-english/ # English originals
│ └── 41.02-japanese/ # Japanese translations
├── 42-Actions/
│ ├── 42.01-english/
│ └── 42.02-japanese/
├── 43-GHAS/
│ ├── 43.01-english/
│ └── 43.02-japanese/
└── 44-Admin/
├── 44.01-english/
└── 44.02-japanese/
Whenever an English knowledge document is created or updated, the note-organizer must automatically create or update the corresponding Japanese translation:
*.01-english/ folder in 40-presentations/, trigger translation.*.02-japanese/ folder with the same filename.
41-Copilot/41.01-english/github-copilot-cli.md → 41-Copilot/41.02-japanese/github-copilot-cli.mdUses the standard template from the standard note template which includes: