daily-review

Convert structured daily work JSON into a markdown retrospective report.

333|83|Updated Jan 9, 2026
One-click install
npx skills add https://github.com/SpaceZephyr/myskill --skill daily-review-spacezephyr
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: daily-review
Source: https://github.com/SpaceZephyr/myskill/tree/main/daily-review
Command: npx skills add https://github.com/SpaceZephyr/myskill --skill daily-review-spacezephyr

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill turns structured daily work data into a clear retrospective, helping users quickly understand what happened yesterday, what needs follow-up, and where time was spent.

Core Features & Use Cases

  • Global Overview: Summarizes the overall work pattern in one sentence and shows how time was distributed across projects.
  • Workspace Analysis: Extracts key discussion points, decisions, unfinished threads, and project-specific recommendations for each active workspace.
  • Usage Insights: Evaluates model choice, token consumption, and tool usage to spot inefficiencies or unusual patterns.
  • Cross-Project Reflection: Highlights shared technical themes, missed priorities, and whether the current workflow is focused more on debugging, building, or planning.

Quick Start

Provide yesterday's work summary data as structured JSON and ask for a concise markdown review report with insights, follow-ups, and cross-project observations.

Frequently Asked Questions about daily-review

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I generate a daily review report from my work logs?

To generate a daily review report, provide your structured daily work data as JSON, including dates, workspaces, and global statistics. The system then transforms this input into a concise markdown summary with actionable insights and missed-item detection.

What is cross-project productivity analysis and how does it work?

Cross-project productivity analysis evaluates your time distribution and shared technical themes across multiple workspaces. It identifies whether your workflow focuses on debugging, building, or planning, and highlights missed priorities to improve overall efficiency.

Can I analyze token consumption and model usage from my daily workspace summaries?

Yes, you can analyze token consumption and model usage by including usage statistics in your JSON input. The system evaluates these metrics to spot inefficiencies, unusual patterns, and tool usage within your daily work records.

How do I detect unfinished discussions and missed items from yesterday's work?

Detecting unfinished discussions requires feeding workspace conversation summaries into the system. It automatically extracts unresolved threads and missed items, providing specific follow-up recommendations in the resulting markdown retrospective.

What is the best way to structure JSON input for a work summary retrospective?

The best way to structure JSON for a work summary retrospective is to include date, workspaces, and global statistics. This structured format allows the system to accurately parse project-specific discussions and generate cross-project observations.

Does daily review reporting work without predefined global statistics?

Daily review reporting requires global statistics within the JSON input to summarize overall work patterns. Without these metrics, the system cannot accurately evaluate time distribution or generate comprehensive cross-project insights.