Log the work segment that you did after the last work log until now in a
Scanned 2/12/2026
Install to Claude Code
npx -y skills add majiayu000/claude-skill-registry --skill log-work --agent claude-codeInstalls into .claude/skills of the current project.
Are you the author of Log Work?
Add the live security badge to your README — it updates automatically with every re-scan.
[](https://www.skillsdirectory.com/skills/majiayu000-log-work)More formats (shields.io, HTML) on the badges page.
---
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
Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.
No comments yet. Be the first to comment!
Create Mermaid diagrams for flowcharts, sequences, ERDs, and
Draft release notes and changelog entries from git history or merged PRs between two refs (tags/SHAs/branches), including breaking changes, migrations, and upgrade steps. Use when the user asks for release notes, changelog updates, or a GitHub Release draft.
Understand the components, mechanics, and constraints of context in agent systems. Use when designing agent architectures, debugging context-related failures, or optimizing context usage.
Explain how claude-mem captures observations, when memory injection kicks in, and where data lives. Use when the user asks "how does claude-mem work?" or "what is this thing doing?".
Review a pull request or contribution deeply, explain it tutorial-style for a maintainer, and produce a polished report artifact such as HTML or Markdown. Use when asked to analyze a PR, explain a contributor's design decisions, compare it with similar systems, or prepare a merge recommendation.