Vault
meain/dotfiles
Manage the Obsidian vault at ~/.local/share/sbdb -- backlog tasks, meeting notes, journal entries, task notes, and general vault lookups.
Draft, organize, or update development journal entries. An agent skill from ravila4/claude-adhd-skills.
$ npx skills add ravila4/claude-adhd-skills --skill daily-journal -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install ravila4/claude-adhd-skills daily-journal --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/ravila4/claude-adhd-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/daily-journal .claude/skills/daily-journal && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "daily-journal" agent skill from https://github.com/ravila4/claude-adhd-skills/tree/main/skills/daily-journal into .claude/skills/daily-journal/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "daily-journal", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/ravila4/claude-adhd-skills/tree/main/skills/daily-journalType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add ravila4/claude-adhd-skills --skill daily-journal -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install ravila4/claude-adhd-skills daily-journal --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/ravila4/claude-adhd-skills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/daily-journal .agents/skills/daily-journal && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "daily-journal" agent skill from https://github.com/ravila4/claude-adhd-skills/tree/main/skills/daily-journal into .agents/skills/daily-journal/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "daily-journal", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add ravila4/claude-adhd-skills --skill daily-journal -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install ravila4/claude-adhd-skills daily-journal --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/ravila4/claude-adhd-skills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/daily-journal .cursor/skills/daily-journal && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "daily-journal" agent skill from https://github.com/ravila4/claude-adhd-skills/tree/main/skills/daily-journal into .cursor/skills/daily-journal/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "daily-journal", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/ravila4/claude-adhd-skills.git --path skills/daily-journal--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add ravila4/claude-adhd-skills --skill daily-journal -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install ravila4/claude-adhd-skills daily-journal --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/ravila4/claude-adhd-skills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/daily-journal .gemini/skills/daily-journal && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "daily-journal" agent skill from https://github.com/ravila4/claude-adhd-skills/tree/main/skills/daily-journal into .gemini/skills/daily-journal/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "daily-journal", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install ravila4/claude-adhd-skills daily-journalInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add ravila4/claude-adhd-skills --skill daily-journal -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/ravila4/claude-adhd-skills.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/daily-journal .github/skills/daily-journal && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "daily-journal" agent skill from https://github.com/ravila4/claude-adhd-skills/tree/main/skills/daily-journal into .github/skills/daily-journal/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "daily-journal", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add ravila4/claude-adhd-skills --skill daily-journal -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install ravila4/claude-adhd-skills daily-journal --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/ravila4/claude-adhd-skills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/daily-journal .opencode/skills/daily-journal && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "daily-journal" agent skill from https://github.com/ravila4/claude-adhd-skills/tree/main/skills/daily-journal into .opencode/skills/daily-journal/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "daily-journal", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
daily-journalDraft, organize, or update development journal entries. An agent skill from ravila4/claude-adhd-skills.
Daily Journal is an agent skill from ravila4/claude-adhd-skills. Draft, organize, or update development journal entries. Use when user requests daily journal generation, work review, standup preparation, or asks "what did I work on today/this week?"
Its SKILL.md is about 2.5k tokens, which your agent loads only when the skill is triggered. The skill folder holds 14 other files, including scripts and reference files (for example `references/callout-conventions.md`, `references/high-signal-patterns.md` and `references/limitations-caveats.md`).
It sits in Productivity & Automation, covering Journaling and reflection, Meeting notes and agendas and Accounting and bookkeeping. It works with Obsidian. The repository describes itself as: Claude Code skills and hooks for staying organized with AI agents. The licence is MIT.
8 steps, taken from the first numbered list in SKILL.md.
Read from SKILL.md and the folder at commit f99e0a3. It shows what the files ask for, not the result of running them.
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Ships 1 file in scripts/ (Python), which the agent can run.
Shell commands in SKILL.md call:
uvFrom the folder's file list and the shell code blocks in SKILL.md.
No URLs in SKILL.md. Its commands use uv, which can reach the network depending on how they are called.
From URLs in SKILL.md, links to its own repository left out.
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Daily Journal loads about 2.5k tokens when it runs, and up to ~14k if it reads all its reference files. Until then it costs about 50 tokens; SKILL.md has 841 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); the scripts in this folder are not scanned.
The full file from ravila4/claude-adhd-skills at commit f99e0a3, republished under its MIT licence (© ravila4). 841 words, ~2,544 tokens.
.claude/skills/daily-journal/SKILL.md (or your agent's skills folder). This skill also uses 11 other files; get the full folder from GitHub.An interactive, conversational skill for creating meaningful daily journal entries. Conversation first, data second.
Commits are not what matters. They're often mechanical, LLM-generated, or busywork. A journal should capture:
Conversation first, data second. Ask the user about their day. Use collected data (git, sessions) only as a memory jogger for days when they can't remember what they did.
Context matters. Weekends are different from workdays. Mornings are different from evenings. Hobby projects are valid. Tooling optimization is valid.
flowchart TD
Start([/daily-journal]) --> CheckTime{What time is it?}
CheckTime -->|Morning| MorningFlow
CheckTime -->|Afternoon/Evening| EveningFlow
subgraph MorningFlow[Morning: Planning Mode]
M1[Read yesterday's entry] --> M2[Show yesterday's open questions]
M2 --> M3{Ask: What's your focus today?}
M3 --> M4{Ask: Any carryover from yesterday?}
M4 --> M5[Create/update today's entry with intentions]
end
subgraph EveningFlow[Afternoon/Evening: Reflection Mode]
E1{Ask: What did you work on?} --> E2{Ask: How did it go?}
E2 --> E3{Ask: What's still open?}
E3 --> E4[Offer data as memory aid]
E4 --> E5{Anything else to add?}
E5 --> E6[Synthesize journal from conversation]
end
subgraph DataAid[Data as Memory Aid]
D1[Run collect_day_data.py] --> D2[Show: I see activity in X...]
D2 --> D3{Worth mentioning?}
D3 -->|Yes| D4[User describes in their words]
D3 -->|No| D5[Skip]
end
E4 --> DataAid
DataAid --> E5
MorningFlow --> Save
EveningFlow --> Save
Save[Save to Obsidian] --> End([Done])
style MorningFlow fill:#e8f4e8
style EveningFlow fill:#e8e8f4
style DataAid fill:#f4f4e8Check the current time before starting. Different times trigger different modes:
| Time | Mode | Primary Questions |
|---|---|---|
| Before noon | Planning | What's your focus? Carryover from yesterday? |
| Afternoon (12-5pm) | Mid-day check | How's the day going? Stuck on anything? |
| Evening (after 5pm) | Reflection | What did you work on? How did it go? |
| Weekend | Lighter touch | What did you tinker with? Any hobby wins? |
How to check:
# Get current time
date "+%H:%M %A" # e.g., "14:32 Saturday"Use this to:
weekend tag, lighter expectationsStart with open questions - don't assume anything from data:
Offer data as memory aid (only after user has shared):
Ask about tomorrow:
weekend tag automaticallyThe collect_day_data.py script is a secondary tool, not the primary input.
When to use it:
How to present it:
I see some activity that might jog your memory:
- 3 commits in my-project
- 45 sessions in data-pipeline
- Files touched in config skill
Any of these worth mentioning in your own words?Running the script:
uv run ~/.claude/skills/daily-journal/scripts/collect_day_data.py [--date YYYY-MM-DD] [--skip-sessions]Clearly differentiate personal voice from LLM context using Obsidian-compatible markdown:
Use blockquotes for the user's own words and feelings:
> Spent most of the morning yak-shaving on my dev tools again.
> It felt productive in the moment but I'm not sure it was the best use of time.
> The API debugging is getting frustrating - every fix reveals another issue.Use regular text or callouts for factual context:
> [!info] Context
> Continued from [[2026-01-23]] - API authentication debugging.
> Related to the data pipeline project.Use collapsible sections for technical details that shouldn't dominate:
<details>
<summary>Technical: Auth token fix</summary>
The issue was that refresh tokens were expiring before the batch job completed.
Fixed with: token rotation middleware.
</details>| Callout | Role | Example titles |
|---|---|---|
[!info] | Context, continuity, collapsible references | "Context", "Reference URLs" |
[!success] | Wins, milestones, progress | "Win", "Big day", "Progress" |
[!warning] | Concerns, friction, blockers | "Blocker", "Growing Pain" |
[!question] | Open loops, things still thinking about | "Still thinking about..." |
[!bug] | Bugs discovered | "Script Bug Found" |
[!note] | Observations, non-actionable insights | "Observation: ..." |
Use the collapsible variant ([!info]-) for bulky reference material (URLs, log snippets).
See callout-conventions.md for detailed examples and placement guidance.
The final journal should feel personal, not mechanical:
---
date: {date}
tags:
- daily-log
- {weekend if applicable}
- {project tags from conversation}
---
## {date} - {day of week}
> {User's summary of the day in their own words - from conversation}
### What I Worked On
> {User's description of their focus, in their voice}
> [!info] Context
> {Any relevant background - continued from yesterday, etc.}
### How It Went
> {User's reflection on the experience - what felt good, what was frustrating}
### Open Loops
> [!question] Still thinking about...
> - {Open questions from conversation}
> - {Blockers mentioned}
### Tomorrow
> {User's stated intentions for tomorrow}
---
*{Day character} - {One-line takeaway}*
## Related
- [[{relevant links}]]| Flag | Description |
|---|---|
--date YYYY-MM-DD | Target date (default: today) |
--quick | Skip interactive questions, just use data (not recommended) |
Never delete historical context. Journal entries are a record of thinking over time - even wrong thinking has value.
~~Outdated info~~~~Thought X caused the bug~~ Turned out to be a race conditionExamples:
### Open Loops
> [!question] Still thinking about...
> - ~~Should I re-run step 1 after the config change?~~ No, step 2 handles it
> - ~~Investigate flaky test in pipeline~~ Was a CI caching issue, fixed 2026-01-25
> - New question that replaced the old oneEvery entry ends with a footer: a horizontal rule followed by an italicized one-liner that captures the overall character of the day. This goes after the last content section and before the Related links.
Format: *{Day character} - {One-line takeaway}*
The "day character" is a brief descriptor of the day's shape -- how long, what kind of energy. The takeaway summarizes the arc.
---
*Full day - Auth system working, merged feature branches, but blocked on deploy permissions for live testing*Guidelines:
Don't:
Do:
© ravila4, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
SKILL.md and 11 other files (scripts, references) in skills/daily-journal of ravila4/claude-adhd-skills.
Open the folder on GitHubat commit f99e0a3
Daily Journal next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Daily Journal this skillravila4/claude-adhd-skills | 158 | — | ~2.5k | Automated safety check: Pass | MIT | |
| Vaultmeain/dotfiles | 285 | — | ~1.3k | Automated safety check: Pass | MIT | |
| GranolaArtemXTech/claude-code-obsidian-starter | 225 | — | ~905 | Automated safety check: Pass | None | |
| Daily UpdateAr9av/obsidian-wiki | 3.5k | — | ~2.4k | Automated safety check: Notes | MIT | |
| Summarize Meetingsharperreed/dotfiles | 334 | — | ~3.3k | Automated safety check: Pass | None | |
| Obsidian Research Logbrycewang-stanford/Auto-Empirical-Research-Skills | 4.6k | — | ~378 | Automated safety check: Pass | Custom licence |
meain/dotfiles
Manage the Obsidian vault at ~/.local/share/sbdb -- backlog tasks, meeting notes, journal entries, task notes, and general vault lookups.
ArtemXTech/claude-code-obsidian-starter
Query and sync Granola meetings to Obsidian vault. An agent skill from ArtemXTech/claude-code-obsidian-starter.
Ar9av/obsidian-wiki
Run or configure the daily wiki maintenance cycle: check source freshness, refresh the index and hot.md, and manage its scheduled 9 AM launchd/systemd/cron reminder.
harperreed/dotfiles
A skill your agent uses when processing, summarizing, or extracting insights from meeting notes in the Obsidian vault.
brycewang-stanford/Auto-Empirical-Research-Skills
A skill your agent uses when the user is discussing daily research work, TODOs, plans, standups, meetings, milestones, or general project progress that should be reflected in Obsidian daily notes…
LeoYeAI/openclaw-master-skills
AI-powered diary generation for agents - creates rich, reflective journal entries (400-600 words) with Quote Hall of Fame, Curiosity Backlog, Decision Archaeology, Relationship Evolution, mood…
ravila4/claude-adhd-skills
Manage Obsidian vault operations. An agent skill from ravila4/claude-adhd-skills.
ravila4/claude-adhd-skills
(TDD) Use when implementing any feature or bugfix. An agent skill from ravila4/claude-adhd-skills.
ravila4/claude-adhd-skills
Nudge the user with time-based reminders (stopping times, meetings, break suggestions).
Works with
Draft, organize, or update development journal entries. An agent skill from ravila4/claude-adhd-skills. Daily Journal is an agent skill from ravila4/claude-adhd-skills. Draft, organize, or update development journal entries.
Daily Journal fits situations like: user requests daily journal generation; standup preparation; asks what did I work on today/this week?.
Run `npx skills add ravila4/claude-adhd-skills --skill daily-journal -a claude-code`. Or copy the skill folder (skills/daily-journal in ravila4/claude-adhd-skills) into .claude/skills/daily-journal in your project. Claude Code loads it when a task matches its description.
Run `npx skills add ravila4/claude-adhd-skills --skill daily-journal -a codex`. Or copy the skill folder (skills/daily-journal in ravila4/claude-adhd-skills) into .agents/skills/daily-journal in your project. Codex loads it when a task matches its description.
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add ravila4/claude-adhd-skills --skill daily-journal -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/daily-journal, .gemini/skills/daily-journal, .github/skills/daily-journal and .opencode/skills/daily-journal in your project.
Going by SKILL.md and its folder, Daily Journal needs Python for the scripts in its folder and the command-line tools its instructions call (uv). Our summary lists: Python 3.
SKILL.md contains no URLs. Its commands use uv, which can reach the network depending on how they are called. This is read from the text; nothing was executed.
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. The check reads SKILL.md only: the scripts in the folder are not scanned, so read them before running anything.
Daily Journal is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
About 2.5k tokens (SKILL.md is roughly 10k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 11k tokens, read only when the agent opens those files.
Skills that share tags, products or a category with Daily Journal: Vault (meain/dotfiles, 285 stars), Granola (ArtemXTech/claude-code-obsidian-starter, 225 stars), Daily Update (Ar9av/obsidian-wiki, 3.5k stars) and Summarize Meetings (harperreed/dotfiles, 334 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
ravila4 (a GitHub user) maintains it in ravila4/claude-adhd-skills, which has 158 GitHub stars. The repository holds 4 skills in this directory. The repository was last updated on March 1, 2026.
Source: ravila4/claude-adhd-skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.