daysactivity-format

Format DaysActivity.md entries with reverse-chronological prepending and HH:MM timestamps.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/justSteve/GasTownOperations --skill daysactivity-format
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: daysactivity-format
Source: https://github.com/justSteve/GasTownOperations/tree/main/.claude/skills/daysactivity-format
Command: npx skills add https://github.com/justSteve/GasTownOperations --skill daysactivity-format

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This document standardizes how team members record sessions, handoffs, hourly summaries, and notes in DaysActivity.md so logs are consistent, scannable, and safe to automate.

Core Features & Use Cases

  • Standardized templates and formatting rules for session handoffs, hourly summaries, and manual notes.
  • Reverse-chronological prepending and 24-hour HH:MM timestamps to ensure predictable ordering.
  • Clear file-listing and single-line summary conventions to support both human readers and automated parsing.
  • Use case: prepare an end-of-shift session handoff that lists state, summary, and open work items.

Quick Start

Use these conventions when adding or updating today's /root/projects/gtOps/DaysActivity.md entry to create a correct session handoff or hourly summary.

Frequently Asked Questions about daysactivity-format

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

FAQPage Schema
What is the standard format for daily activity log entries?

Daily activity log entries require reverse-chronological prepending, 24-hour HH:MM timestamps, single-line summaries, and separate file listing lines to ensure predictable ordering and support both human readability and automated parsing.

How do I format a session handoff for a daily log?

To format a session handoff in a daily log, prepend the entry in reverse-chronological order with a 24-hour HH:MM timestamp, include a single-line summary, and list open work items or state changes on separate lines for clear team transitions.

Why use reverse-chronological order and 24-hour timestamps in daily logs?

Reverse-chronological order and 24-hour HH:MM timestamps in daily logs ensure predictable entry ordering and unambiguous time tracking, which supports automated parsing and maintains consistency across manual notes and hourly summaries.

Can I use this daily log format for hourly summaries and manual notes?

Yes, the daily log formatting rules apply to session handoffs, hourly summaries, and manual notes within the DaysActivity.md file, enforcing single-line summaries and separate file listing lines for all day-to-day activity capture.

Does daily log formatting support automated parsing?

Daily log formatting supports automated parsing by enforcing strict conventions like 24-hour HH:MM timestamps, single-line summaries, and separate file listing lines, making the log entries scannable and safe to automate.

What are the limitations of standardized daily log formatting?

Standardized daily log formatting is limited to entries within the DaysActivity.md file and requires strict adherence to single-line summaries and separate file listing lines, meaning multi-line paragraphs are not supported for automated parsing.