log

Record project events and session outcomes to Supabase and log.md.

4|1|Updated Mar 14, 2026
One-click install
npx skills add https://github.com/MattVOLTA/outworkos_diy --skill log-mattvolta
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: log
Source: https://github.com/MattVOLTA/outworkos_diy/tree/main/skills/log
Command: npx skills add https://github.com/MattVOLTA/outworkos_diy --skill log-mattvolta

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Records project events and working sessions to log.md. Default mode captures end-of-session accomplishments. 'refresh' mode queries data sources for external events. Use at end of session, when user says 'log this', or to pull in external timeline events.

Core Features & Use Cases

  • Logs project activity to log.md and the project timeline.
  • Supports a refresh mode to pull external timeline events from connected data sources.
  • Ensures context is preserved across sessions by centralizing records in log.md and the database.

Quick Start

Say 'log this' at the end of a session to record progress into log.md.

Frequently Asked Questions about log

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

FAQPage Schema
How do I record project session outcomes to a centralized log?

To record project session outcomes to a centralized log, use the default mode at the end of a working session or say 'log this' to capture accomplishments and persist them to log.md and a Supabase database.

What is the best way to pull external timeline events into project documentation?

The best way to pull external timeline events into project documentation is using refresh mode, which queries connected data sources to retrieve and persist external activity directly into your project log.

Does this project logging method require a Supabase database setup?

Yes, this project logging method requires Supabase because it enforces a DB-first model using the current session context to write records to the database, while also maintaining a local log.md file.

How are log entries structured for retrieval in project management tracking?

Log entries for project management tracking are structured by date, which enforces a newest-first retrieval order to ensure recent session outcomes and project events are immediately accessible.

Can I use this session tracking approach to preserve context across multiple project workflows?

Yes, you can use this session tracking approach across per-project workflows because it centralizes records in log.md and the database, ensuring context is preserved across separate working sessions.