Daily Report Public

Generate structured daily reports for the user, summarizing completed tasks, ongoing work, pending items, and notable notes. Use when user asks for daily rep...

Security Scan

The skill's instructions mostly match its stated purpose (generating daily reports) but they reference reading and updating local memory/project files without declaring those config paths or the persistence side effects, which is an unexplained gap you should understand before installing.

Purpose & Capability

The name/description (daily report generation) aligns with the instructions: the skill reads memory and project files and uses conversation history to build reports. Access to local 'memory/YYYY-MM-DD.md', TODO.md, PROJECTS.md is coherent with this purpose.

Instruction Scope

The SKILL.md explicitly instructs the agent to read today's and yesterday's memory files, project files, and recent conversation history and to 'Update memory files with the generated report'. That read/write behavior is a side effect and persistent storage operation that is not declared elsewhere. The instructions do not specify exact paths, permissions required, or safeguards for sensitive data.

Install Mechanism

No install spec and no code files are present (instruction-only), so nothing will be downloaded or written at install time. This is lower risk from an install-execution standpoint.

Credentials

The skill requests no environment variables, credentials, or config paths. That matches there being no external services or binaries required. However, the skill still expects to read/write local files even though no config paths are declared.

Persistence & Privilege

The skill instructs updating memory files (persistent writes) but does not declare required config paths or surface that it will modify stored data. While 'always' is false and autonomous invocation is allowed (the platform default), the persistent write behavior increases impact if the agent is invoked autonomously and should be disclosed.

What to consider before installing

This skill appears to do what it says (generate daily reports) but it reads and writes local 'memory' and project files without declaring the file paths or describing permissions and data-retention behavior. Before installing or enabling it: - Confirm where the agent's memory directory lives and whether the skill will be allowed to write there. Ask the publisher to specify exact paths used and whether writes are atomic/append-only. - If you have sensitive content in memory or project files, consider restricting the skill's file access or disabling autonomous invocation until you review behavior. - Ask whether generated reports will be stored verbatim in memory (could persist sensitive details) and whether there is any rotation, encryption, or export policy. - Because this is instruction-only, there is no external network URL in the spec, which reduces supply-chain risk — but the persistent write behavior is the main concern. Request the publisher to explicitly declare config paths and describe write safeguards; if they can't, treat the skill as higher risk.

Daily Report

Overview

This skill generates structured daily reports that help users:

• Review what was accomplished today
• Track ongoing work and progress
• Identify pending items and blockers
• Maintain a record of daily activities

Report Format

Generate reports in the following structure:

📋 今日完成

• [Task 1] Description + Status (✅/进行中/⏸️)
• [Task 2] Description + Status

⏳ 进行中

• [Task A] Current progress + Estimated completion time
• [Task B] Pending confirmation items + What's needed from user

📝 待办/未完成

• [Todo 1] Reason/Blocker
• [Todo 2] Priority level

💡 备注

• Items needing special attention
• Issues or risks discovered

Data Sources

When generating a daily report, check these sources:

1. Today's memory file (memory/YYYY-MM-DD.md) - Primary source for today's tasks
2. Yesterday's memory file (memory/YYYY-MM-DD.md) - For carryover context
3. Recent conversation history - If needed for clarification
4. Project files (e.g., TODO.md, PROJECTS.md) - If relevant

Generation Process

1. Read today's memory file to identify completed tasks
2. Check for ongoing work and pending items
3. Identify any blockers or areas needing user attention
4. Format according to the report structure above
5. Highlight critical items (deadlines, blockers, user decisions needed)

Customization

Adjust the report format or sections based on user feedback. Common variations:

• Add time tracking (hours spent per task)
• Add next-day priorities
• Include links to relevant files or commits
• Add metrics (tasks completed, tasks in progress, etc.)

Triggers

Generate a daily report when:

• User asks for "日报", "今天干了什么", "daily report", "今日总结", "今天完成了什么"
• User wants to review daily progress
• User asks "what did you do today" or similar
• User requests a status summary

Notes

• Keep reports concise and actionable
• Prioritize highlighting blockers and decisions needed
• Use clear status indicators (✅, 🔄, ⏸️, ❌)
• Update memory files with the generated report for future reference