Agent skill

Log Work

by pchalasani in pchalasani/claude-code-tools

Log the work segment that you did after the last work log until now in a log file at WORKLOG/YYYYMMDD.md where YYYYMMDD is based on today's date.

MITAuto-check passed

Install Log Work

skills CLI
$ npx skills add pchalasani/claude-code-tools --skill log-work -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install pchalasani/claude-code-tools log-work --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/pchalasani/claude-code-tools.git skills-src && mkdir -p .claude/skills && cp -r skills-src/plugins/workflow/skills/log-work .claude/skills/log-work && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
log-work
GitHub stars
2k
Token cost
~323 tokens
SKILL.md length
113 words
Files
1
Skills in repo
17
Repo updated
First seen
Licence
MIT

At a glance

Log the work segment that you did after the last work log until now in a log file at WORKLOG/YYYYMMDD.md where YYYYMMDD is based on today's date.

  • Works in 3 steps: create the file WORKLOG/YYYYMMDD.md if… → if the file exists, append a new… → When you add a section, follow this…
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Log Work is an agent skill from pchalasani/claude-code-tools. Log the work segment that you did after the last work log until now in a log file at WORKLOG/YYYYMMDD.md where YYYYMMDD is based on today's date. The intent of this worklog is not to be exhaustive and super detailed. It is meant more as a very concise description plus, importantly, REFERENCES to more detailed documents such as code files or markdown documents, etc. This allows humans as well as AI agents to only refer to these additional documents if they want details. This is the progressive disclosure principle.

Its SKILL.md is about 320 tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

The repository describes itself as: Practical productivity tools for Claude Code, Codex-CLI, and similar CLI coding agents. The licence is MIT.

Example prompts

  • “/log-work”

Workflow steps

3 steps, taken from the first numbered list in SKILL.md.

  1. create the file WORKLOG/YYYYMMDD.md if it doesn't already exist.
  2. if the file exists, append a new TOP-LEVEL markdown section to it.
  3. When you add a section, follow this format for the section header, so it has

What it can do on your machine

Read from SKILL.md and the folder at commit 0ca7320. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md (its code samples are markdown).

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Log Work loads about 323 tokens when it runs. Until then it costs about 132 tokens; SKILL.md has 113 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~132
When it runs · the whole SKILL.md, loaded when a task matches
~323

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from pchalasani/claude-code-tools at commit 0ca7320, republished under its MIT licence (© pchalasani). 113 words, ~323 tokens.

Download SKILL.mdSave it as .claude/skills/log-work/SKILL.md (or your agent's skills folder).
name
log-work
description
Log the work segment that you did after the last work log until now in a log file at WORKLOG/YYYYMMDD.md where YYYYMMDD is based on today's date. The intent of this worklog is not to be exhaustive and super detailed. It is meant more as a very concise description plus, importantly, REFERENCES to more detailed documents such as code files or markdown documents, etc. This allows humans as well as AI agents to only refer to these additional documents if they want details. This is the progressive disclosure principle.

log-work

  1. create the file WORKLOG/YYYYMMDD.md if it doesn't already exist.
  2. if the file exists, append a new TOP-LEVEL markdown section to it.
  3. When you add a section, follow this format for the section header, so it has HH:MM timestamp followed by suitable concise topic
markdown
# 13:45 Added feature xyz

In the log section include a CONCISE set of items such as the following (Not all may apply to all situations, use your judgement):

  • the session_id of the current session
  • any text/md file(s) you CREATED and their purpose
  • any text/md file(s) you READ as part of the current task
  • short description of what you just did, including any results you got
  • which code files were created/changed

© pchalasani, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in plugins/workflow/skills/log-work of pchalasani/claude-code-tools.

Open the folder on GitHubat commit 0ca7320

Compare with similar skills

Log Work next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Log Work compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Log Work this skillpchalasani/claude-code-tools2k—~323Automated safety check: PassMIT
Growth Logaffaan-m/ECC275k1 repos~1.7kAutomated safety check: PassMIT
Clickhouse Logs Queriessupabase/supabase111k—~2.4kAutomated safety check: PassApache-2.0
Investigating LogsPostHog/posthog40k—~2.1kAutomated safety check: PassCustom licence
Homelab Vlan Segmentationaffaan-m/ECC275k1 repos~2.5kAutomated safety check: PassMIT
Logging and Error Reporting for Warpwarpdotdev/warp65k1 repos~5.6kAutomated safety check: PassAGPL-3.0

Similar skills

  • Growth Log

    affaan-m/ECC

    Write growth log entries that extract reusable patterns from completed work — root cause, transferable rule, and a recognizable signal — instead of diary-style event narration, with a 4-8 sentence…

    275k GitHub starsUsed in 1 repo~1.7k tokens
    DevelopmentAuto-check passed
  • Clickhouse Logs Queries

    supabase/supabase

    Official

    Write, review, and migrate Supabase logs queries against the ClickHouse-backed logs table (the logs.all.otel analytics endpoint).

    111k GitHub stars~2.4k tokensUpdated today
    DatabasesAuto-check passed
  • Investigating Logs

    PostHog/posthog

    Official

    Investigate logs in a PostHog project: verify a service or deployment is healthy, explain an error spike, triage an incident, or understand what a log stream is saying.

    40k GitHub stars~2.1k tokensUpdated today
    DatabasesAuto-check passed
  • Segmenting home networks into VLANs for IoT, guest, trusted, and server traffic using UniFi, pfSense/OPNsense, and MikroTik — including switch trunk config, firewall rules, and wireless SSID mapping.

    275k GitHub starsUsed in 1 repo~2.5k tokens
    DevOps & CloudAuto-check passed
  • Guides log level choices and when to raise a structured Sentry event instead of a plain log line in the Warp Rust codebase, keeping secrets out of logs.

    65k GitHub starsUsed in 1 repo~5.6k tokens
    DevelopmentAuto-check passed
  • Analyze Logs

    activepieces/activepieces

    Analyze application logs from the .evlog/logs/ directory. An agent skill from activepieces/activepieces.

    25k GitHub starsUsed in 1 repo~1.6k tokens
    DevelopmentAuto-check passed

More from pchalasani/claude-code-tools

All 17 skills in this repo
  • Remove AI Patterns

    pchalasani/claude-code-tools

    Remove AI-writing patterns ("AI-isms") from text using the avoid-ai-writing catalog (conorbronsdon/avoid-ai-writing).

    2k GitHub stars~1.4k tokensUpdated 3 days ago
    Auto-check passed
  • Dynamic Workflow

    pchalasani/claude-code-tools

    Create, review, run, inspect, pause, resume, and cancel durable JavaScript workflows that coordinate multiple headless Codex agents.

    2k GitHub stars~5.3k tokensUpdated 3 days ago
    Auto-check passed
  • Voxtype Install

    pchalasani/claude-code-tools

    Guide the user through installing, configuring, and launching voxtype — local on-device voice dictation (speech-to-text that types wherever the cursor is).

    2k GitHub stars~857 tokensUpdated 3 days ago
    Auto-check: notes
  • Agent Style

    pchalasani/claude-code-tools

    Literature-backed English technical-prose writing rules (agent-style, 21 rules).

    2k GitHub stars~1.4k tokensUpdated 3 days ago
    Auto-check passed
  • Msg

    pchalasani/claude-code-tools

    Inter-agent communication via the msg CLI. An agent skill from pchalasani/claude-code-tools.

    2k GitHub stars~362 tokensUpdated 3 days ago
    Auto-check passed
  • Tmux CLI

    pchalasani/claude-code-tools

    CLI utility to communicate with other CLI Agents or Scripts in other tmux panes; use it only when user asks you to communicate with other CLI Agents or Scripts in other tmux panes.

    2k GitHub stars~324 tokensUpdated 3 days ago
    Auto-check passed

Questions about Log Work

What does Log Work do?

Log the work segment that you did after the last work log until now in a log file at WORKLOG/YYYYMMDD.md where YYYYMMDD is based on today's date. Log Work is an agent skill from pchalasani/claude-code-tools.md where YYYYMMDD is based on today's date.

How do I install Log Work in Claude Code?

Run `npx skills add pchalasani/claude-code-tools --skill log-work -a claude-code`. Or copy the skill folder (plugins/workflow/skills/log-work in pchalasani/claude-code-tools) into .claude/skills/log-work in your project. Claude Code loads it when a task matches its description.

How do I install Log Work in Codex?

Run `npx skills add pchalasani/claude-code-tools --skill log-work -a codex`. Or copy the skill folder (plugins/workflow/skills/log-work in pchalasani/claude-code-tools) into .agents/skills/log-work in your project. Codex loads it when a task matches its description.

Can I use Log Work in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add pchalasani/claude-code-tools --skill log-work -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/log-work, .gemini/skills/log-work, .github/skills/log-work and .opencode/skills/log-work in your project.

What does Log Work need to run?

SKILL.md names no scripts, command-line tools or credentials: Log Work is instructions for the agent only.

Does Log Work access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Log Work safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Log Work use?

Log Work is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Log Work use?

About 323 tokens (SKILL.md is roughly 1.3k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Log Work?

Skills that share tags, products or a category with Log Work: Growth Log (affaan-m/ECC, 275k stars), Clickhouse Logs Queries (supabase/supabase, 111k stars), Investigating Logs (PostHog/posthog, 40k stars) and Homelab Vlan Segmentation (affaan-m/ECC, 275k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Log Work?

pchalasani (a GitHub user) maintains it in pchalasani/claude-code-tools, which has 2,010 GitHub stars. The repository holds 17 skills in this directory. The repository was last updated on October 5, 2026.

Source: pchalasani/claude-code-tools on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.