agentleFS
Sign inStart free
natscho-hhnatscho-hh/ai-secondbrain-stack/skills/daily-note/SKILL.md

daily-note

Skill2 starsChanged 4 months agoMITView on GitHub

Create or update today's daily note as the session log.

7 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use implement-spec, to-questionnaire and 10 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • AWSSkill

    implement-spec

    Implement the result of /to-spec and /to-tickets in code.

    Also in 3 projects that use this

  • AWSSkill

    to-questionnaire

    Turn a decision you can't fully answer into a questionnaire for someone else to fill in.

    Also in 3 projects that use this

  • GoogleSkill

    wayfinder

    Plan a huge chunk of work — more than one agent session can hold — as a shared map of decision tickets on your issue tracker, and resolve them one at a time until the way to the destination is clear.

    Also in 4 projects that use this

  • GoogleSkill

    to-tickets

    Break a plan, spec, or the current conversation into a set of tracer-bullet tickets, each declaring its blocking edges, published to the configured tracker — edges as text in one file per ticket locally, or native blocking links on a real tracker.

    Also in 4 projects that use this

  • MicrosoftSkill

    writing-for-agents

    Writing documents for agents. Use when creating or editing skills, or modifying AGENTS.md or CLAUDE.md.

    Also in 3 projects that use this

  • +5 more from google
  • +2 more from aws

The file

We split this skill into the rules it gives an agent

6 rules. 0 are common, 5 are distinctive, and 1 is very specific to this project.

  • 0

    Common

    Most of the 4 edited versions we read keep these.

  • 5

    Distinctive

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Check whether that file already exists.

    line 13
  2. Distinctive:

    If it exists, append new content to the existing sections instead of overwriting anything already there.

    line 14
  3. Very specific:

    If it does not exist, create it from the 99 Templates/Daily Note.md template: YAML frontmatter containing tags: [daily] and date: …

    line 15
  4. Distinctive:

    Commit the change with a short, descriptive message and push.

    line 17
  5. Distinctive:

    Never delete or overwrite existing content in a daily note — always append.

    line 21
  6. Distinctive:

    Keep entries factual and dated.

    line 22

“Common” is measured: kept by at least 6 in 10 of the 4 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.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

When to use

Use this skill at the start of a session to log what's about to happen, during a session to record something worth remembering, or at the end of a session to summarize decisions and open threads — any time the day's activity needs a durable, dated record.

Steps

  1. Compute today's date and the target path: 05 Daily Notes/YYYY-MM-DD.md.
  2. Check whether that file already exists.
  3. If it exists, append new content to the existing sections instead of overwriting anything already there.
  4. If it does not exist, create it from the 99 Templates/Daily Note.md template: YAML frontmatter containing tags: [daily] and date: YYYY-MM-DD (daily notes don't carry a status field), followed by three sections: ## What happened, ## Decisions, ## Open threads.
  5. Fill in each section from the current session's context: what was done, what was decided (and why), and what's left open or unresolved for next time.
  6. Commit the change with a short, descriptive message and push.

Rules

  • Never delete or overwrite existing content in a daily note — always append.
  • Keep entries factual and dated; a daily note is a log, not a place for open-ended brainstorming (link out to a project or resource note for that).
  • One daily note per calendar day — never create a second file for the same date.

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.

Check your setup, free