Skip to content
Back to search

claude-worklog

MarketplaceWorks with Claude CodeGitHub

Worklog skill for Claude Code: a daily record of your work across all sessions, as a standup report, a Discord update and a Google Sheet dashboard.

Safety scan

A static text scan, not a guarantee. Select the badge to see what was scanned and every finding.

Checked today

Check it deeper on your machine

It has changed since its scan on 20 Nov 2026.

As a Claude Code plugin, install it and then ask Claude Code:

/plugin marketplace add keithmackay/mackayi/plugin install scanskillsafety@mackayiDo a deep scan of https://github.com/rishavkr08/claude-worklog with scanskillsafety

Or from a terminal, clone it and run it:

git clone https://github.com/keithmackay/scanskillsafety-skill ~/.claude/skills/scanskillsafetynode ~/.claude/skills/scanskillsafety/cli.cjs --deep 'https://github.com/rishavkr08/claude-worklog'

It checks the exact commit: every file, its packages against OSV (api.osv.dev), how it compares with this page's scan (findsafeskills.com receives the repository's address), and, if you agree, Claude reading every file with your own Claude subscription. It never runs the code.

Badge for your README
findsafeskills safety rating

Markdown

[![findsafeskills safety rating](/api/listings/rishavkr08--claude-worklog/badge.svg)](/listings/rishavkr08--claude-worklog)

HTML

<a href="/listings/rishavkr08--claude-worklog"><img src="/api/listings/rishavkr08--claude-worklog/badge.svg" alt="findsafeskills safety rating" /></a>

Install

Install instructions from the README

As written by the repo's author. findsafeskills has not verified these steps.

In Claude Code:

/plugin marketplace add rishavkr08/claude-worklog
/plugin install worklog@claude-worklog

Or copy `plugins/worklog/skills/worklog/` into `~/.claude/skills/`.

What was scanned

The files the safety scan read, as written by the repository's author and shown as plain text. Lines with a finding are marked.

.claude-plugin/marketplace.json · Manifest · 16 lines
  1. {
  2. "name": "claude-worklog",
  3. "owner": {
  4. "name": "Rishav Kumar"
  5. },
  6. "metadata": {
  7. "description": "Worklog skill for Claude Code: a daily record of your work across all sessions."
  8. },
  9. "plugins": [
  10. {
  11. "name": "worklog",
  12. "source": "./plugins/worklog",
  13. "description": "Daily worklog from your Claude Code sessions: tickets, PRs, analysis and time, as a standup report, a Discord update and an optional Google Sheet dashboard."
  14. }
  15. ]
  16. }
README.md · README · 120 lines
  1. # Worklog for Claude Code
  2. Ask Claude "what did I do yesterday?" and get a real answer, built from every Claude Code session you ran, across all your repos.
  3. If you work in several sessions a day, the record of what you did is scattered across them. This skill reads the session transcripts Claude Code already keeps on your computer and turns them into:
  4. - **A standup report**: tickets and PRs with their live review status, reviews you did, analysis and investigations, ops work, automated runs (and which ones failed), time spent, and open threads.
  5. - **A chat update** ready to paste into Discord, one block per ticket:
  6. ```md
  7. **ABC-123 - Carousel posts**
  8. * Done: posts can now be carousels of photos and videos in the admin, the API and the public viewer
  9. * Staging: deployed and tested ✅
  10. * Status: Ready for review — [api#412](<https://github.com/acme/api/pull/412>)
  11. **Data analysis report**
  12. * Payment failures for one merchant: their gateway has been switched off since 5 Jun
  13. ```
  14. - **A Google Sheet dashboard** (optional): one row per item per day, with a timeline view, animated day switching, and a "Copy Discord message" button.
  15. ## Install
  16. In Claude Code:
  17. ```
  18. /plugin marketplace add rishavkr08/claude-worklog
  19. /plugin install worklog@claude-worklog
  20. ```
  21. Or copy `plugins/worklog/skills/worklog/` into `~/.claude/skills/`.
  22. ## Use
  23. Just ask:
  24. - "What did I do today?"
  25. - "Standup for yesterday"
  26. - "Worklog for this week"
  27. The first time, Claude offers to save your settings (ticket prefix, staging branch names).
  28. ## Requirements
  29. - **Claude Code on your own computer.** The skill reads `~/.claude/projects/`, so it sees the sessions run on that machine. Cloud sessions leave no transcripts there.
  30. - **Python 3** (any recent version; no packages needed).
  31. - **`gh`** signed in, if you want live PR status. Without it, status is reported as "not checked".
  32. - **For the sheet:** a Google account and a Google Drive tool in Claude that can create a file in a folder (for example the Google Drive connector).
  33. ## Settings
  34. `~/.claude/worklog/config.json`, all optional:
  35. ```json
  36. {
  37. "ticket_pattern": "ABC-\\d+",
  38. "staging_branches": ["staging"],
  39. "chat": "discord",
  40. "sheet_url": "",
  41. "inbox_folder_id": ""
  42. }
  43. ```
  44. | Key | What it does |
  45. |---|---|
  46. | `ticket_pattern` | Regex for your ticket keys. Unset, any Jira-style key (`ABC-123`) counts. Setting it also picks up keys from branch names like `fix/abc-123-login`. |
  47. | `staging_branches` | Branches that mean "on staging" when pushed or merged into. |
  48. | `chat` | `discord` for markdown links, `plain` for bare URLs. |
  49. | `sheet_url`, `inbox_folder_id` | The Google Sheet dashboard, below. Leave empty to skip it. |
  50. ## Google Sheet dashboard (optional)
  51. Claude's Drive tools can create files but can't edit cells in an existing sheet. So each run drops a small CSV into a Drive folder, and a script inside your sheet imports it.
  52. 1. Create a new Google Sheet.
  53. 2. Open **Extensions → Apps Script**, replace `Code.gs` with [`apps-script/Code.gs`](plugins/worklog/skills/worklog/apps-script/Code.gs), and save.
  54. 3. Reload the sheet and choose **Worklog → Set up (first time)**. Approve the Google permission prompt. It creates a "Worklog inbox" folder next to the sheet, turns on an hourly import, and shows the folder ID.
  55. 4. Give Claude the folder ID and the sheet URL ("save these as my worklog sheet settings").
  56. After the next worklog, choose **Worklog → Open dashboard**. Re-running a day replaces that day's rows, so reruns don't duplicate.
  57. The script only touches the sheet it lives in and the inbox folder it created. Google's permission prompt is broader than that because Apps Script has no narrower permission for reading a folder.
  58. ## Run it every morning
  59. Ask Claude to schedule it, for example: "Every weekday at 9:30, write my worklog for the previous working day; on Mondays cover Friday to Sunday." The run has to start on your own computer, because that's where the transcripts are.
  60. ## Privacy
  61. - The digest script only reads local files and makes no network calls.
  62. - Your work leaves your computer only through steps you can see: `gh` asks GitHub for PR status, and the optional sheet step uploads a CSV to your own Google Drive.
  63. - Session transcripts can contain anything you typed or pasted. The report is written from them, so read it before you share it.
  64. ## How it works
  65. `worklog.py` scans the transcripts changed in the date window and prints, for each session: its title, repos and branches, active minutes, ticket keys, PRs, commits, pushes, your prompts, end-of-turn summaries, and anything the session produced (Drive files, published pages, files sent to you). `SKILL.md` tells Claude how to group that by work item, check PR status, and write the report, the chat update and the sheet rows.
  66. ```bash
  67. python3 plugins/worklog/skills/worklog/worklog.py --date yesterday
  68. python3 plugins/worklog/skills/worklog/worklog.py --date today --days 7 --json
  69. ```
  70. ## Limits
  71. - Active minutes are an estimate: gaps over 5 minutes between messages count as idle.
  72. - Staging and review status in the sheet are a snapshot from the day of the run.
  73. - End-of-turn summaries are richest in the Claude desktop app. In the terminal, the skill falls back to each session's last reply.
  74. - The dashboard's copy button writes Discord-style markdown.
  75. ## Development
  76. ```bash
  77. node tests/run.js
  78. ```
  79. runs the sheet script and the dashboard's page script against stand-ins for the Google services, using the fictional day in `tests/sample.csv`.
  80. ## License
  81. MIT

Ratings and comments

Sign in to rate this skill.

Sign in

Free to use. If it’s helped, pass it on.