End Of Day Wrap Up

Automates the transition from deep work to reflection by synthesizing workspace activity and user notes into a cohesive summary.

Install
cmdop skills install agensi-end-of-day-wrap-up

End Of Day Wrap Up is a skill published by agensi that automates the creation of daily progress reports by pulling together workspace activity, files modified during the session, and user-supplied notes. Rather than relying on memory or a blank page, it synthesizes that evidence into a cohesive summary that separates work done with AI assistance from work completed manually — a distinction described as a strict quality gate in the skill’s own documentation.

The skill applies carry-forward logic to identify unfinished tasks and blockers, so the next session starts with continuity rather than confusion. It enforces selection of exactly one top priority for the following day, preventing the morning paralysis that comes from an undifferentiated task list.

Output is produced in two formats: clean Markdown suited for documentation systems or commit logs, and a self-contained, mobile-responsive HTML file designed for sharing with managers or teammates without requiring them to have any specific tooling. The HTML artifact can be saved locally or forwarded directly.

The skill is aimed at developers and project leads who want structured, evidence-based reporting without manual overhead. It does not require environment variables or additional configuration. Because it has no exposed tools, it operates as a guided workflow rather than a direct API integration — making it appropriate when the goal is structured reflection and reporting rather than programmatic data retrieval.

Use cases

  • Generate a structured end-of-day progress report from workspace file activity and session notes
  • Automatically separate AI-assisted work from manually completed tasks in a daily summary
  • Identify unfinished tasks and blockers to carry forward into the next working session
  • Produce a mobile-responsive HTML report to share with a manager or team
  • Force selection of a single top priority for the following day to focus planning
  • Create Markdown summaries suitable for commit messages, wikis, or project logs

When to use it

  • When a developer or project lead needs a daily report grounded in actual workspace activity rather than recalled progress
  • When maintaining clear attribution between AI-assisted and manual work is a governance or reporting requirement
  • When the output needs to be shareable as a standalone HTML file without requiring downstream tooling
  • When carry-forward visibility on blockers and incomplete tasks is needed between sessions

When not to use it

  • When programmatic, real-time database or API queries are needed — this skill exposes no tools for data retrieval
  • When reports must be pushed automatically to an external system such as a project tracker or ticketing platform
  • When the workflow requires environment-variable-driven configuration or credentials
  • When the user needs summaries across multiple users or repositories rather than a single workspace session