daily_log
Skill3 starsChanged 2 months agoMITView on GitHub
Scans the current conversation thread and updates a project work log. Useful for tracking progress and generating release notes.
1 other project uses a version of this, 1 of them edited.
Adopted by
Most recently taken up by
- krishnakanthb13/antigravity_global_skillsedited, first seen Jul 4, 2026
Other versions1 project uses a version of this.
Word for word · 0
None found.
Edited · 1
- krishnakanthb13/antigravity_global_skills★ 50100% same
Wrote their own version · 0
None found.
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 repository46 other files it gives its agents.
- agy-customizationsSkill
- antigravity-guideSkill
- api-and-interface-designSkill
- browser-testing-with-devtoolsSkill
- ci-cd-and-automationSkill
- code-review-and-qualitySkill
- code_reviewSkill
- code-simplificationSkill
- context-engineeringSkill
- create_launcherSkill
- create_skillSkill
- debugging-and-error-recoverySkill
- debug_issueSkill
- deprecation-and-migrationSkill
- document_apiSkill
- documentation-and-adrsSkill
- enhance_uiSkill
- frontend_designSkill
- frontend-ui-engineeringSkill
- generate_release_imageSkill
- git-workflow-and-versioningSkill
- idea-refineSkill
- idea_to_actionSkill
- impeccableSkill
- incremental-implementationSkill
- list_featuresSkill
- open_source_prepSkill
- optimize_codebaseSkill
- performance-optimizationSkill
- permissioned-githubSkill
- planning-and-task-breakdownSkill
- release_helperSkill
- repo_infographicSkill
- scaffold_testsSkill
- security-and-hardeningSkill
- security_auditSkill
- shipping-and-launchSkill
- software_architectureSkill
- spec-driven-developmentSkill
- test-driven-developmentSkill
- test_runnerSkill
- ui_ux_pro_maxSkill
- update_docsSkill
- using-agent-skillsSkill
- using-ui-stackSkill
- web_performance_optimizationSkill
The file
We split this skill into the rules it gives an agent
7 rules. About 0 are common, 2 are distinctive, and 5 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈2
Distinctive · estimate
This author's own choices. Worth a look.
5
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 8
Use this skill to capture the work done in a session/thread and append it to a persistent log file.
- Very specific: line 17
Use list_dir to find the work_log folder.
- Very specific: line 18
Use write_to_file to create the new log entry.
- Distinctive: line 32
Create a markdown entry containing not just what was done, but the context around it:
- Very specific: line 52
Directory: Create or utilize a work_log folder in the project's current working directory.
- Very specific: line 53
Filename: Add the entry to a unique log file named with the format yyyymmdd-hhmmss.log (e.g., 20260125-005255.log).
- Very specific: line 54
Action: Use write_to_file to create the new log file within the work_log folder.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Daily Log
Use this skill to capture the work done in a session/thread and append it to a persistent log file.
Inputs
- Scope: The current session context (messages, tools used).
- Work Log Directory:
work_log(default).
Tooling Strategy
- Use
list_dirto find thework_logfolder. - Use
write_to_fileto create the new log entry.
Workflow
1. Identify Target
- Folder: Target the
work_logfolder in the project's base directory. - Context: Scan the current conversation thread to identify:
- Features implemented.
- Bugs fixed.
- Decisions made.
2. Format Entry
Create a markdown entry containing not just what was done, but the context around it:
## [Date] - [Thread/Topic Name]
- **Summary**: [One line summary]
- **Details (The 'What')**:
- [Detailed bullet point]
- [Detailed bullet point]
- **Decisions (The 'Why')**:
- [Why a specific approach was chosen over alternatives]
- **Blockers & Open Questions**:
- [Any lingering issues or technical debt introduced]
- **Next Steps**:
- [Actionable items for the next session]
- **Link**: [Markdown Link to Thread/Conversation if available]3. Save Log Entry
- Directory: Create or utilize a
work_logfolder in the project's current working directory. - Filename: Add the entry to a unique log file named with the format
yyyymmdd-hhmmss.log(e.g.,20260125-005255.log). - Action: Use
write_to_fileto create the new log file within thework_logfolder.
4. Output
- Confirmation: Give explicit confirmation to the user that the log entry has been created and mention the filename and path.
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.