worklog
Skill1 starsChanged 35 days agoNo licenceView on GitHub
Record what was actually done in a working session into the current project's worklog.md — shipped commits, work in flight, dead ends, blockers, and the next action — then close out the matching Notion tasks. Auto-invoke when Ania is wrapping up and says something like 'log this session', 'what did we get done', 'wrap up', 'end of day', or 'write that up before I forget'. Also invoked directly as /worklog. This skill records work that WENT OUT of the session — things Ania and Claude did. It is NOT for information coming IN from outside (a follow-up email, a spec change, a stakeholder decision, a new dataset) — that is `work-update`, and if both could apply, split the material and say which half went where. Do not invoke for a passing thought to stash (`nb`), or to start a new project (`work-intake`).
14 other projects use a version of this.
Adopted by
Most recently taken up by
- JibranMachiavelli/claude-worklogtheir own version, first seen Nov 8, 2026
- Vinay-R/vibe-engineering-templatetheir own version, first seen Nov 1, 2026
- Srltas/claude-skillstheir own version, first seen Oct 31, 2026
- rynbol/claude-skillstheir own version, first seen Oct 13, 2026
- BespokeWoodcraftStudio/claude-worklog-skilltheir own version, first seen Oct 11, 2026
- dgilford/ai-science-toolkittheir own version, first seen Oct 1, 2026
Other versions14 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 14
- revfactory/skills★ 160same name
- dgilford/ai-science-toolkit★ 82same name
- tae0y/python-project-template★ 14same name
- BespokeWoodcraftStudio/claude-worklog-skill★ 1same name
- bpappin/skills★ 1same name
- f-ewald/claude-skills★ 1same name
- ingeun92/claude-code-configs★ 1same name
- renicsemenov/claude-code-skills★ 1same name
- Hyosun-byte/worklog★ 0same name
- JibranMachiavelli/claude-worklog★ 0same name
4 more not listed
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository6 other files it gives its agents.
- air-fryerSkill
- grocery-price-checkSkill
- grocery-weekly-adSkill
- nbSkill
- work-intakeSkill
- work-updateSkill
The file
Show its rules and text
We split this skill into the rules it gives an agent
14 rules. 0 are common, 5 are distinctive, and 9 are very specific to this project.
0
Common
Most of the 12 edited versions we read keep these.
5
Distinctive
This author's own choices. Worth a look.
9
Very specific
Tied to their project's names, files or tools. Probably skip.
No licence file, so all rights are reserved — read it at the source. We count its rules but don't quote them. Read them on GitHub.
“Common” is measured: kept by at least 6 in 10 of the 12 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.