daily-note-writer
Skill1 starsChanged 6 months agoMITView on GitHub
Create today's Daily Note in 01 - Daily Notes/ with frontmatter, top-3 prompt, and anti-todo section. Use when Andy says start the day, daily note, today's note, what should I work on today.
In this repository28 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- auditSkill
- brainstormSkill
- commit-message-writerSkill
- compile-topicSkill
- course-builderSkill
- deck-builderSkill
- diagnoseSkill
- drift-fixSkill
- forgeSkill
- git-bootstrapSkill
- grill-with-docsSkill
- handoffSkill
- improve-codebase-architectureSkill
- lesson-content-writerSkill
- project-scaffolderSkill
- prototypeSkill
- retroSkill
- reviveSkill
- setup-pre-commitSkill
- specialist-creatorSkill
- sweep-inboxSkill
- tddSkill
- to-issuesSkill
- to-prdSkill
- triageSkill
- workflow-authorSkill
- zoom-outSkill
The file
We split this skill into the rules it gives an agent
3 rules. About 0 are common, 3 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈3
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 49
Don't auto-fill Top 3 - that's Andy's choice
- Distinctive: line 50
Don't add task-management formality (no priorities, no labels) - it's intentionally minimal
- Distinctive: line 51
Don't pad with extra sections - the four above are it
≈ “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 Note Writer
When to use
Triggers: daily note, today's note, start the day, morning kickoff, anti-todo.
Create
File: 01 - Daily Notes/<YYYY-MM-DD>.md (today's date in ISO).
Template
---
type: daily-note
created: <YYYY-MM-DD>
tags: [daily]
---
# <Day name, Month Day Year>
## Top 3
1.
2.
3.
## Anti-todo
> Things you actually got done today (write here as you go - low-friction capture).
-
## Captures
> Ideas, links, quotes - anything worth keeping.
-
## Tomorrow
> One thing to seed tomorrow.
-After creating
Open the file. Don't fill in Top 3 yourself - leave for Andy. Suggest he reads the previous day's note (if it exists) for context.
Don't
- Don't auto-fill Top 3 - that's Andy's choice
- Don't add task-management formality (no priorities, no labels) - it's intentionally minimal
- Don't pad with extra sections - the four above are it
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.