AgentStack
Browse Sign in
Browse Why AgentStack Sell Docs
Sign in
SKILL verified MIT Self-run

Managing Daily Notes

skill-sawyer-middeleer-dot-claude-managing-daily-notes · by Sawyer-Middeleer

Manages daily notes in a second-brain markdown knowledge base (a folder with a conventions.md or KB-declaring CLAUDE.md) - finding, creating, reading, and updating them, including task carryover with provenance. Trigger on "my daily note", "create today's daily note", "carry over my tasks", "close out the day" when working in such a knowledge base.

No reviews yet
0 installs
36 views
0.0% view→install

Install

$ agentstack add skill-sawyer-middeleer-dot-claude-managing-daily-notes

✓ scanned · ✓ verified, works with Claude Code, Cursor, and more.

Security review

✓ Passed

No issues found. Passed automated security review. · v0.1.0 How review works →

  • Prompt-injection patterns
  • Secret / credential exfiltration
  • Dangerous shell & filesystem operations
  • Untrusted network calls
  • Known-malicious package signatures

What it can access

  • Network access No
  • Filesystem access No
  • Shell / process execution No
  • Environment & secrets No
  • Dynamic code execution No

From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.

View the full security report →

Verified badge

Passed review? Show it. Paste this badge into your README, it links to the public security report.

AgentStack Verified badge Links to your public security report.
[![AgentStack Verified](https://agentstack.voostack.com/badges/verified.svg)](https://agentstack.voostack.com/security/report/skill-sawyer-middeleer-dot-claude-managing-daily-notes)

Reliability & compatibility

Security review passed
0 installs to date
no reviews yet
3mo ago

Declared compatibility

Claude CodeClaude Desktop

Compatibility is declared by the source manifest. End-to-end runtime verification is coming, see below.

Preview Execution monitoring

We're building live execution health for every listing: tool-call success rate, median latency, uptime, and last-checked timestamps, measured, not self-reported. It isn't live yet, so we don't show numbers we can't stand behind.

How agent discovery & health will work →
Are you the author of Managing Daily Notes? Claim this listing to set pricing, connect Stripe payouts, and keep 70% of every sale.
Sign up to claim

About

Managing Daily Notes

Daily notes live at _daily/YYYY/MM/YYYY-MM-DD.md (or wherever the knowledge base's conventions.md says). Not every day has a note; gaps are normal.

Finding

  • Today / a specific date: search for the full path (_daily/**/YYYY-MM-DD.md) — never by bare filename, which can match elsewhere
  • Most recent: highest year folder → highest month folder → highest date file
  • Reading a daily note never needs permission — read freely

Creating

  1. Determine the target date; create the YYYY/MM/ folders if missing
  2. Structure: frontmatter (type: daily, created/modified = the date), a ## Tasks section, a ## Notes section — or the KB's own daily template if one exists in its templates folder
  3. Carry over tasks: find the most recent prior note, copy every incomplete task (- [ ]) into the new note's Tasks section, preserving order. Stamp each carried task with provenance the first time it moves forward — append (since YYYY-MM-DD) using the date of the note you're carrying from (preserve an existing (since …) rather than overwriting). This makes staleness computable later. If more than ~15 tasks would carry over, don't blindly copy them all — surface the count and ask the user whether to carry, drop, or defer the backlog; an unbounded carry compounds daily into noise.

Updating

Tasks:

  • Mark complete (- [ ]- [x]) or reopen — no permission needed, just do it
  • New tasks: tasks are ordered by priority top-to-bottom; ask where a new one ranks, or place it sensibly and say where
  • Don't reorder existing tasks unless asked

Notes section: end-of-day summaries, work-in-progress context too verbose for a task line, and links to the notes touched today (per the KB's link style — daily notes are the spine the rest of the base hangs off).

End-of-day pass (when asked to "close out the day")

  1. Mark finished tasks; flag stale ones — using each task's (since YYYY-MM-DD) stamp, anything carried more than ~5 days — and ask whether to drop, defer, or keep them
  2. Summarize the day's work in the Notes section, linking the relevant notes
  3. Anything durable that surfaced today → offer /second-brain:capturing-knowledge rather than letting it die in the daily note

Source & license

This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.

Install and usage instructions live in the source repository linked above.

Reviews

No reviews yet, be the first.

Versions

  • v0.1.0 Imported from the upstream source.