work-ledger-sync

Updates the public work_ledger via Supabase MCP with status, timestamps, and notes.

Updated Feb 3, 2026

Search Tags:#automation #supabase #notes #sessions #workflows #tracking #ledger

Ready to run

npx skills add https://github.com/BedaBeda-Growth/bedabeda-growth-site --skill work-ledger-sync

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: work-ledger-sync
Source: https://github.com/BedaBeda-Growth/bedabeda-growth-site/tree/main/skills/work-ledger-sync
Command: npx skills add https://github.com/BedaBeda-Growth/bedabeda-growth-site --skill work-ledger-sync

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Keeps a real-time, universal ledger of all work across planning, execution, review, and dispatch to prevent untracked work and miscommunication.

Core Features & Use Cases

Three mandatory ledger touches: session start, milestone updates, and session end to ensure comprehensive tracking.
Append notes, update statuses, and timestamps in the public work_ledger to provide a single source of truth for teams.
Supports ad-hoc tasks and cross-repo work by documenting context and what happened during each session.

Quick Start

Begin a session and log your work to auto-update the universal work ledger.

Frequently Asked Questions about work-ledger-sync

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

FAQPage Schema

How do I track work progress across multiple sessions in Supabase?▼

A universal work ledger tracks work across sessions by applying three mandatory ledger touches: session start, milestone updates, and session end. It utilizes Supabase MCP to insert and update entries in the public.work_ledger, ensuring real-time status transitions, timestamping, and notes for comprehensive tracking.

What is a universal work ledger and how does it prevent untracked work?▼

A universal work ledger is a real-time record of all work across planning, execution, review, and dispatch phases. It prevents untracked work and miscommunication by requiring entries at session start, milestones, and session end, creating a single source of truth for teams.

Does the work ledger sync require Supabase MCP for status transitions?▼

Yes, the work ledger sync requires Supabase MCP to apply proper status transitions, timestamping, and notes when inserting or updating the public.work_ledger. This ensures entries are accurately reflected as work progresses and milestones occur.

How do I log ad-hoc tasks and cross-repo work to a Supabase ledger?▼

You log ad-hoc tasks and cross-repo work to a Supabase ledger by documenting the context and events of each session. The ledger supports appending notes and updating statuses for ad-hoc tasks, ensuring all activities are captured in the universal work ledger.

Are there guardrails to prevent stale or duplicate entries in the work ledger?▼

Yes, the work ledger includes guardrails designed to prevent stale or duplicate entries. These guardrails operate alongside the Supabase MCP inserts and updates to ensure the public.work_ledger maintains accurate, real-time records without redundant data.