Framework for creating end-of-day summary documents. Use when user says "daily summary", "generate summary", or similar at end of day. Provides structured markdown template with date verification, filename patterns, and formatting guidelines. Extend with personal metrics and domain-specific content.
The 'daily-summary-base' skill provides a framework for creating structured session summary documents. It solves the problem of summarizing and capturing conversations or sessions with detailed accuracy. This skill ensures that summaries reflect the actual content and time span of the session, whether it spans a single day or crosses calendar boundaries. By using a structured markdown template, it makes it easy for users to organize and generate summaries that are both clear and consistent. It also takes care of critical date and time verification to avoid confusion and ensure correct session documentation.
Key features include support for both single-day and multi-day session ranges, customizable context tags, and strict filename generation rules that adhere to a specific template. The summary documents follow a strict markdown structure, allowing users to capture ground truth data, key decisions, metrics, and insights. The generated summary is easy to use, and the framework also provides essential guidelines like date verification, emoji limitations, and formatting rules. Target users are individuals or teams who need a simple yet effective way to track and summarize session data, such as in project management, team collaboration, or training sessions.
You must first verify the current date and time in the user's timezone using the provided command: `TZ='America/New_York' date '+%A, %B %d, %Y - %I:%M %p %Z'`. This ensures there is no confusion about the dates used in the summary.
Yes, the framework supports summaries that span calendar boundaries. When this happens, the filename will reflect the exact dates and the day names will be abbreviated in the range format (e.g., 'Mon-to-Tue').
Emojis should be avoided in data sections such as tables or timestamps, as they can interfere with machine readability. Emojis can be used sparingly in narrative sections if they add meaningful context, but it's recommended to use plain text when in doubt.
Quick Setup:
.claude/skills/Repository
ZachBeta/claude-as-coach