work-log-maintenance

Automate work log maintenance and generate Slack business-day reports.

Updated Apr 18, 2026
One-click install
npx skills add https://github.com/jey3dayo/apm-workspace --skill work-log-maintenance
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: work-log-maintenance
Source: https://github.com/jey3dayo/apm-workspace/tree/main/catalog/skills/work-log-maintenance
Command: npx skills add https://github.com/jey3dayo/apm-workspace --skill work-log-maintenance

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill simplifies the process of maintaining work logs and generating manager-facing Slack reports, focusing on business-day counts and report generation.

Core Features & Use Cases

  • Work Log Maintenance: Organize and update work-log artifacts efficiently.
  • Manager-Facing Reports: Produce Slack-ready business-day summaries and detailed reports.
  • Use Case: For a project manager, this Skill can quickly generate a Slack report showing the work done over the past two weeks, including business-day counts and leave adjustments.

Quick Start

Use the work-log-maintenance skill to generate a report for the past two weeks and send it to your manager via Slack.

Frequently Asked Questions about work-log-maintenance

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

FAQPage Schema
How do I automate Slack report generation from git logs and TODOs?

Slack report generation is automated by extracting evidence from git logs, changelogs, TODOs, and Slack notes to produce manager-facing summaries. This Skill compiles those artifacts into business-day reports with leave adjustments.

Can I generate business-day summaries that account for leave adjustments?

Business-day summaries with leave adjustments are supported natively by this Skill. It processes your structured work logs to calculate accurate working days while factoring in scheduled leave for manager-facing reports.

Do I need a specific file layout to maintain work logs with this approach?

A structured file layout and YAML configuration are required to maintain work logs using this Skill. You must organize your work-log artifacts according to this structure before generating reports.

What's the best way to organize work logs for manager-facing reports?

Organizing work logs for manager-facing reports requires structuring artifacts like git logs and changelogs into a standardized file layout. This Skill then extracts evidence from those sources to create business-day summaries.

Does this work log maintenance approach track evidence from multiple sources?

Work log maintenance tracks evidence from multiple sources including git logs, changelogs, TODOs, and Slack notes. It aggregates these disparate inputs to generate comprehensive business-day summaries.

Are there limitations when sending work log reports via Slack?

Limitations include the requirement for a structured file layout and YAML configuration before report generation. This Skill focuses on manager-facing Slack summaries and business-day counts rather than raw log storage.