daily-review

Summarize yesterday's conversations and usage data into a daily work review.

1|2|Updated Feb 28, 2026
One-click install
npx skills add https://github.com/zhangdszq/vk-skills --skill daily-review-zhangdszq
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: daily-review
Source: https://github.com/zhangdszq/vk-skills/tree/main/daily-review
Command: npx skills add https://github.com/zhangdszq/vk-skills --skill daily-review-zhangdszq

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Daily-review assistant condenses yesterday's work conversations and usage data into a concise, actionable report, saving time and guiding next steps.

Core Features & Use Cases

  • Automatic daily recap of conversations across workspaces with key metrics
  • Detection of missed items and follow-up recommendations
  • Global and per-workspace insights into usage patterns and resource allocation

Quick Start

Provide yesterday's structured JSON data to generate the daily review report.

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 work summary from conversation and usage data?

To generate a daily work summary, provide yesterday's structured JSON data containing conversations and usage metrics. The system outputs global summaries, per-workspace analyses, and actionable recommendations.

What is the best way to analyze per-project activity across multi-workspace teams?

Analyzing multi-workspace teams requires processing structured JSON input to extract discussion highlights and resource usage. This identifies focus areas and bottlenecks, outputting per-workspace analyses and actionable insights.

Can I detect missed work items and follow-up recommendations from yesterday's conversations?

You can detect missed work items by feeding conversation data into the daily review. It identifies missed items and outputs specific follow-up recommendations and code suggestions to guide next steps.

Does the daily review process require a specific JSON format for worklog and usage analysis?

Daily review requires structured JSON input containing worklog and usage data. Without structured JSON formatting, the system cannot parse conversations and usage patterns to generate actionable work reviews.

What limitations exist when summarizing conversations across multiple workspaces?

Summarizing conversations across multiple workspaces depends entirely on receiving complete structured JSON data. It cannot extract data automatically and is limited to analyzing only the per-project activity provided in the input.