work-log-reporter

Log per-session work entries and email formatted HTML reports with PDF attachments over SMTP.

2|Updated Jul 28, 2026
One-click install
npx skills add https://github.com/mbadali25/useful-claude-add-ons --skill work-log-reporter-mbadali25
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: work-log-reporter
Source: https://github.com/mbadali25/useful-claude-add-ons/tree/main/skills/work-log-reporter
Command: npx skills add https://github.com/mbadali25/useful-claude-add-ons --skill work-log-reporter-mbadali25

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires reportlab, and includes scripts (resource) and references (resource) and assets (resource) components.

What problem does it solve? Keeping an accurate record of what was done during a work session is tedious, and reconstructing it later from memory or diffs produces vague, unreliable summaries. This Skill maintains a committed per-session work log in the repository and turns it into a professional email report with a detailed PDF attachment, sent over SMTP. ## Core Features & Use Cases - Structured session logging: Start, log, and end work sessions via a single CLI, capturing summaries, detail prose, code files, systems, databases, tables, commands, and ticket references per entry. - Batched email reporting: Generate an HTML email with a high-level summary plus a full-detail PDF attachment, covering everything since the last report, a single session, today, or all history. - Safe delivery controls: Dry-run previews, config validation, environment-variable-only SMTP credentials, and auto-email that is off by default. - Use Case: At the end of a day spent fixing a production incident, run one command to email your manager a report covering all sessions, with the root-cause narrative in the body and exact commands and tables touched in the attached PDF. ## Quick Start Ask the AI to start a work log session for your current task, log each completed piece of work as you go, and send the end-of-day report when you are done.

Frequently Asked Questions about work-log-reporter

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

FAQPage Schema
How do I send a daily work report email from the command line?

Run the worklog CLI's send command after logging sessions throughout the day. It batches every session since the last report into one HTML email with a PDF attachment and delivers it via your configured SMTP server, then marks those sessions as reported.

How do I configure SMTP for sending work log reports?

Edit work-log/worklog.config.json with your SMTP server, port, and security mode: 587 with starttls, 465 with ssl, or 25 with none for an internal relay. The password is never stored in the file; export it as the environment variable named in smtp.auth.password_env.

Can I preview the report email before sending it?

Yes. The report command builds the HTML and PDF without touching SMTP, and send with the dry-run flag additionally prints the exact subject line and recipient list. Both are read-only and never update the reported-sessions state.

Why does the report send without a PDF attachment?

PDF generation requires the reportlab Python package. If it is not installed, the email still sends with the HTML body only and a warning is printed; install it with pip install reportlab to restore the attachment.

What happens to unsent sessions if a report fails to send?

Sessions are only marked as reported after SMTP accepts the message. A failed send leaves them pending, so the next send automatically includes them along with any newer sessions, and retrying sends the same content.