telegram-daily-log

Summarize verified daily accomplishments from git, GitHub, and shell history into a Telegram post.

Updated Aug 6, 2026
One-click install
npx skills add https://github.com/wkentaro/skills --skill telegram-daily-log-wkentaro
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: telegram-daily-log
Source: https://github.com/wkentaro/skills/tree/main/skills/in-progress/telegram-daily-log
Command: npx skills add https://github.com/wkentaro/skills --skill telegram-daily-log-wkentaro

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Reconstructing what you actually accomplished today requires digging through scattered evidence across Claude and Codex transcripts, GitHub activity, local git commits, and shell history, then verifying claims against real output before writing a daily log. ## Core Features & Use Cases - Multi-source evidence gathering: Inspects Codex and Claude transcripts, GitHub activity via gh, local git repos under ~/ghq, and Zsh history to reconstruct the day. - Verification-first summarization: Treats prompts, commands, and commit messages as claims and confirms them against files, refs, PR state, and releases before including them. - Telegram-ready output: Produces a plain-text post with exactly three grouped items, optional small wins and output counts, then copies it to the macOS clipboard with pbcopy. - Use Case: At the end of a workday, ask for your daily log and receive a verified, clipboard-ready Telegram post summarizing shipped work without manually reviewing every terminal session. ## Quick Start Use the telegram-daily-log skill to summarize today's verified accomplishments and copy the Telegram-ready post to my clipboard.

Frequently Asked Questions about telegram-daily-log

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

FAQPage Schema
How do I generate a daily work log from git and GitHub activity?▼

Invoke the skill and it inspects local git repositories under ~/ghq, GitHub activity through the gh CLI, and shell history to reconstruct the day. It verifies each claim against actual files, commits, and PR state before writing the summary.

How to summarize Claude or Codex session transcripts into a daily report?▼

The skill reads Claude and Codex histories and transcripts as evidence streams, attributing work by working directory and timestamp when prompts are unreadable. It searches transcripts for published work like posted URLs that leave no trace in git or the shell.

Does the daily log include work done outside git repositories?▼

Yes, it searches the day's transcripts for evidence of externally published work, such as the user pasting a URL or saying they posted, sent, or submitted something. Shell commands are attributed to the session working in that repository at that hour.

Can the daily log leak credentials from shell history?▼

The skill filters history before printing tool output, never emits raw histories, and omits secrets from the post. When a credential is found, it warns separately without repeating the value, keeping warnings outside the clipboard content.

What format does the Telegram daily log output use?▼

The output is Telegram-safe plain text with a dated title, exactly three numbered items grouped by effort, optional small wins, and verified output counts. It avoids Markdown link syntax and decorative formatting that render inconsistently in Telegram.