What is the primary function of the log skill?

It creates a structured, chronological record of work sessions and external events in both a local Markdown file (log.md) and a remote Supabase database.

What happens if my database connection is offline?

The skill includes a graceful fallback mechanism that writes to the local log.md file and notifies the user that the database write was skipped.

Does this skill support multi-project workflows?

Yes, the skill automatically determines the correct target project using session context or explicit arguments, ensuring logs are stored in the specific project's directory.

How does the 'refresh' mode pull in external events?

It uses a project's 'Timeline Playbook' defined in the context-map.md to execute SQL queries or API calls that find new events since the last log entry.

Project Activity Logger

Name: Project Activity Logger
Author: MattVOLTA

byMattVOLTA

•

Productivity & Workflow

Automates the recording of project sessions and external timeline events into a unified Markdown and database-backed log system.

The Project Activity Logger is a core utility for Outwork OS that streamlines project documentation by capturing working session accomplishments and external events. It features a dual-write architecture that synchronizes updates to both a local log.md file and a Supabase database via MCP tools. By analyzing session context, modified files, and tool usage, it generates structured summaries that include artifact links, decisions made, and follow-up tasks, ensuring a high-fidelity chronological record of project evolution across multiple workspaces.

Key Features

01Legacy migration support for merging existing timeline and update files

02Refresh mode for pulling external events from APIs and data sources

03Dual-write synchronization to local Markdown files and Supabase DB

04Smart project targeting for cross-project logging within a hub environment

05Automated session summarization based on real-time tool and file activity

062 GitHub stars

Use Cases

01Synchronizing project timelines between multiple devices via database-first storage

02Creating a permanent, searchable audit trail of daily coding progress and decisions

03Consolidating external event data from GitHub, calendars, and tasks into one unified log

Key Features

01Legacy migration support for merging existing timeline and update files

02Refresh mode for pulling external events from APIs and data sources

03Dual-write synchronization to local Markdown files and Supabase DB

04Smart project targeting for cross-project logging within a hub environment

05Automated session summarization based on real-time tool and file activity

062 GitHub stars

Use Cases

01Synchronizing project timelines between multiple devices via database-first storage

02Creating a permanent, searchable audit trail of daily coding progress and decisions

03Consolidating external event data from GitHub, calendars, and tasks into one unified log