Agent skill
pkm:daily-review
Complete the Daily Review section for end-of-day reflection in Obsidian
Install this agent skill to your Project
npx add-skill https://github.com/devkade/collaborator/tree/main/skills/pkm-framework/skills/temporal/daily-review
SKILL.md
Daily Review Skill
This skill helps you close out your day by completing the π Daily Review section with tasks completed, time usage, insights, and tomorrow's priorities.
Purpose
Automatically complete the π Daily Review section with:
- Tasks completed today
- Time usage from Google Calendar and pomodoro tracking
- Key insights and learnings
- Suggestions for tomorrow's work
Context
- Daily notes location:
20_Notes/Journal/YYYY/Mnn/YYYY-MM-DD.md - Obsidian vault:
~/Obsidian/Altellus - Date logic: If current time is before 04:00 AM, use previous day's date for the review
- Example: 2025-11-19 02:30 AM β review 2025-11-18
- Example: 2025-11-19 05:00 AM β review 2025-11-19
- TaskNotes data: Pomodoro tracking may be in YAML frontmatter (
pomodorosfield)
Workflow
1. Determine target date
- Check current time
- If before 04:00 AM, use previous day's date
- Otherwise, use today's date
2. Check Google Calendar
- Use the
/pkm:gcal-todaycommand to fetch events - TaskNotes already has Google Calendar ICS subscriptions configured
- Extract scheduled meetings, appointments, and time blocks
3. Read target date's daily note (TaskNotes format)
- Extract completed tasks in TaskNotes format:
- [x] [[Task Name]] β YYYY-MM-DD - Check YAML frontmatter
pomodorosarray for time tracking data - Review content added during the day
4. Fill "μ€λ μλ£" (Tasks Completed) section - TaskNotes format
- List all completed tasks:
- [x] [[Task Name]] β YYYY-MM-DD - Search in "μ€λ μ΄μ΄μ ν μΌ" section and Notes section
- If no tasks completed, note what was worked on instead
5. Fill "μκ° μ¬μ©" (Time Usage) section - TaskNotes Pomodoro format
- Count total pomodoros from YAML
pomodorosarray length - Group by taskPath and display as:
Task Name - π π π : 3 - Show total with tomato emoji count:
μ΄ π π π π π π : 6 pomodoros - List calendar events from Google Calendar:
- HH:MM-HH:MM: Event Title
6. Fill "μΈμ¬μ΄νΈ" (Insights) section
- Extract key learnings, discoveries, or patterns from today's notes
- What worked well? What didn't?
- Any blockers or important realizations?
- Consider how calendar events aligned with planned work
7. Fill "λ΄μΌ μ μ" (Tomorrow's Suggestions) section - TaskNotes format
- Based on incomplete tasks and insights, suggest priorities for tomorrow
- Format as
- [ ] [[Task Name]](TaskNotes wikilink format) - Connect to blockers or unfinished work
- Prioritize incomplete tasks from today
Output Format
Provide only the "π Daily Review" section content to update in today's note.
Important:
- DO NOT modify the "## Retro" section (user fills this manually)
- DO NOT modify other sections
- Preserve all frontmatter and existing content
Usage
This skill is called via the /pkm:daily-review command, typically at the end of the workday or before bed.
Integration
- Uses the gcal-review skill for Google Calendar integration
- Reads YAML frontmatter for pomodoro tracking
- Works with Periodic Notes plugin in Obsidian
- Respects the early-morning edge case (reviews previous day if before 4 AM)
Example
Input: User runs /pkm:daily-review on 2025-11-19 at 10:00 PM
Process:
- Determine target date: 2025-11-19 (after 4 AM)
- Fetch calendar events for 2025-11-19 using
gcal-review - Read
~/Obsidian/Altellus/20_Notes/Journal/2025/M11/2025-11-19.md - Extract completed tasks marked with
[x] - Calculate time usage from calendar + pomodoros in YAML
- Generate insights from note content
- Suggest tomorrow's priorities based on incomplete work
Output: Updated "π Daily Review" section with all subsections filled.
Recommended Agent Skills
Expand your agent's capabilities with these related and highly-rated skills.
example-plugin
Brief description of what this plugin does and when to use it
example:feature-1
Description of feature 1 and when to use it
example:feature-2
Description of feature 2 and when to use it
deep-reading-framework
Three-pass critical reading framework for systematic document analysis. Supports tech blogs, retrospectives, technical documentation, personal writing, and academic papers. Primary focus on Third Pass critical analysis, context validation, and actionable reconstruction. Use when analyzing complex documents, performing critical reading, extracting actionable insights, or conducting deep analysis. Triggers include Third Pass, λΉνμ λΆμ, critique, κΉμ΄ μ½κΈ°, μ¬μΈ΅ λΆμ.
oss-contribution-framework
Systematic framework for contributing to open source projects. Guides through issue discovery, integrated analysis with code exploration, implementation, and PR creation. Use when starting OSS contributions, analyzing issues, or creating pull requests. Includes modular sub-skills for each contribution phase.
oss:issue-analysis
Phase 2 of OSS contribution - Deep analysis combining issue requirements with codebase exploration. Extracts requirements, explores code structure, identifies exact code locations to fix, traces execution paths, and maps code-level changes needed. Use when starting work on selected issue.
Didn't find tool you were looking for?