Team Work Log for Claude Code

    1

    Ask "where did we leave off?", "what did Alice do yesterday?" or "what changed in auth this week?" and get an answer from a few hundred lines of log.

    Free

    1 useSecurity scanned

    Works with the AI Agents you already use

    Claude CodeClaude CodeCursorCursorCodex CLICodex CLIDeepSeekDeepSeekMuseMuse+22 more

    Team Work Log for Claude Code

    Example session with this skill installed

    Set up the work log for this repo. Then tell me what Alice worked on yesterday and where she left off on the auth module.

    • Read your context and instructions
    • Compiled the team work log

    Summary

    The work-log hook is now installed: I added one Stop hook to .claude/settings.json and kept your existing settings. From your next turn on, each turn is logged to work-log/<date>/<your git name>.md.

    Yesterday Alice had 6 turns on the auth module. She added rate limiting to login, and stopped while fixing a failing test.

    What the log shows (work-log/2026-11-09/alice.md)

    TimeAskedFiles changedAlso
    10:12Add rate limiting to the login endpointapi/auth.py, api/limits.py
    10:40Write tests for the limitertests/test_auth.py
    11:05Why does test_lockout fail on CI?tests/test_auth.py
    14:20Use Redis for the limiter in prod, memory in testsapi/limits.py, config/settings.pycommitted
    15:02Add an env var for the Redis URL, key is [redacted]config/settings.py
    16:45test_lockout still flaky, look at the clock mockingtests/test_auth.py

    The 15:02 entry contained an API key in the prompt. The hook replaced it with [redacted] before writing.

    Where she left off

    • The Redis-backed limiter is committed (14:20).
    • test_lockout is still flaky. Her last turn points at clock mocking in tests/test_auth.py, and nothing after it was committed.

    Next steps

    1. Open only tests/test_auth.py and api/limits.py, the two files the last turns touched, and check the clock mocking in test_lockout.
    2. Run pytest tests/test_auth.py -k lockout to confirm the failure before changing anything.

    (Example project. Entry format and redaction are exactly what the hook writes.)

    Connects securely to your tools. The creator never sees your data.

    About this skill

    What it does

    Every time Claude Code finishes a turn, a Stop hook appends a short entry to work-log/<YYYY-MM-DD>/<user>.md:

    • Asked: what you asked Claude to do
    • Files changed: every file touched, including changes made by shell commands (found by comparing git status between turns)
    • Also: commits, pushes and skills that ran
    • Claude replied: the start of Claude's answer

    Each person gets their own file per day (named from git config user.name), so a team can commit the log with no merge conflicts.

    Why use it

    A new session usually spends thousands of tokens re-reading code and git history to work out where you left off. With this skill, Claude reads the last day or two of the log first, then opens only the files it points to. Ask "where did we leave off?", "what did Alice do yesterday?" or "what changed in auth this week?" and get an answer from a few hundred lines of log.

    Setup

    Ask Claude: "set up the work log". It adds one Stop hook to .claude/settings.json (keeping your existing settings) and the log starts with the next turn. Optional settings: WORKLOG_USER to override the name, WORKLOG_DIR to change the folder.

    Safety

    • Key-shaped text (API keys, bearer tokens, password=..., long mixed tokens) is replaced with [redacted] before anything is written.
    • Prompts are cut at 500 characters, replies at 700.
    • Standard library Python only. No network calls.
    • The hook never fails or slows a turn: every error is caught and it always exits 0.

    Limits

    • Claude Code only, because it uses Claude Code hooks.
    • Needs Python 3.9+ and git (git is used to detect files changed by shell commands).
    • Redaction is pattern-based, so do not paste secrets on purpose.
    • If you do not want the log in your repo, add work-log/ to .gitignore.

    Find more skills like this on the Claude Skills Marketplace, the Codex Skills Marketplace and the Gemini Skills Marketplace, or browse Claude Skills for Agents & Orchestration.

    Requires Python 3.9+ and a Git repository. Redaction uses pattern matching and is not exhaustive. Prompt and reply lengths are capped at 500 and 700 characters respectively.

    How to use

    1. 1

      Connect your agent to the Agensi MCP

      Copy the prompt and paste it into Claude, ChatGPT, Cursor or any agent that supports MCP. It sets up the connection for you. Manual setup

    2. 2

      Sign in to Agensi

      Your agent shows a sign-in link. Sign in and click Allow.

    3. 3

      Ask for what you need

      Your agent loads this skill and uses it on your task. It always asks before buying a skill.

    Reviews

    No reviews yet

    Be one of the first to try it. Every listed skill goes through the trust checks below.

    Security scanned

    Checked by our 8-point scan before listing

    1 use

    Times used to date

    Free to use

    No account required to browse

    Trust & safety

    Security scan

    Security scan passed 7 days ago

    • Free with an Agensi account

    Software
    Python 3.9+Git repository

    Permissions

    Terminal / Shell
    Read Files
    Write Files
    Environment Variables

    Shell: runs read-only git commands (status, diff, rev-parse, config user.name) to find changed files and the user's name. Read files: reads the current Claude Code transcript. Write files: appends to work-log/<date>/<user>.md and a small state file inside .git/. Environment variables: reads only WORKLOG_USER, WORKLOG_DIR and USER. No network access.

    Listed7 days ago

    What's inside

    Frequently Asked Questions

    This skill automates the tracking of developer activity by recording prompts, file changes, and responses into organized Markdown logs, eliminating the need for manual status updates and reducing token usage during session handovers.

    The skill is specifically designed for Claude Code and requires a Python 3.9+ environment and a Git repository to function; it integrates directly via a native hook in your Claude settings.

    Log files are stored locally in a 'work-log/' directory within your project and are separated by Git username to prevent merge conflicts when multiple developers contribute to the same repository.

    The skill includes a built-in redaction engine that automatically filters out common patterns for API keys, bearer tokens, and passwords before any data is written to the log files.

    You will receive the Python-based hook scripts, configuration files for Claude Code integration, and comprehensive documentation for installation and local deployment.

    Yes, since the logs are stored as standard Markdown files, you can prompt Claude to read and summarize them to quickly catch up on a teammate's progress or resume your own work after a break.

    New in Agents & Orchestration

    Free