Skip to content
Back to search

claude-adhd-skills

SkillWorks with Claude CodeGitHub

Claude Code skills and hooks for staying organized with AI agents.

Safety scan

A static text scan, not a guarantee. Select the badge to see what was scanned and every finding.

Checked today
Badge for your README
findsafeskills safety rating

Markdown

[![findsafeskills safety rating](/api/listings/ravila4--claude-adhd-skills/badge.svg)](/listings/ravila4--claude-adhd-skills)

HTML

<a href="/listings/ravila4--claude-adhd-skills"><img src="/api/listings/ravila4--claude-adhd-skills/badge.svg" alt="findsafeskills safety rating" /></a>

Install

i

Install instructions from the README

As written by the repo's author. findsafeskills has not verified these steps.

1. Copy skills to your Claude Code config

# Clone the repo
git clone https://github.com/ravila4/claude-adhd-skills.git
cd claude-adhd-skills

# Copy skills into your Claude Code skills directory
cp -r skills/* ~/.claude/skills/

# Copy hooks
cp hooks/* ~/.claude/hooks/

2. Wire up the hooks

Copy the hook configuration into your Claude Code settings. The settings file is at `~/.claude/settings.json` (global) or `~/.claude/settings.local.json` (local/private).

See `settings.json.example` for the full config. The key hooks are:

- **UserPromptSubmit**: Runs on every prompt. Shows current time and any due nudges.

{
  "hooks": {
    "UserPromptSubmit": [
      {
        "type": "command",
        "command": "echo \"Today is $(date '+%A, %B %d, %Y'). Time: $(date '+%H:%M')\"",
        "timeout": 5000
      },
      {
        "type": "command",
        "command": "python3 ~/.claude/hooks/check_alerts.py",
        "timeout": 5000
      }
    ]
  }
}

3. Set up your CLAUDE.md

Copy `CLAUDE.md` to `~/.claude/CLAUDE.md` and fill in the `{PLACEHOLDERS}`:

cp CLAUDE.md ~/.claude/CLAUDE.md

Edit the file and replace: - `{YOUR_NAME}`: your name - `{YOUR_ROLE}`: your job title or role - `{WHAT_YOU_DO}`: brief description of your work - `{YOUR_PLATFORM}`: your machine/OS (e.g., "MacBook Pro, macOS") - `{YOUR_WORK_DOMAIN}`: your work domain (e.g., "web development", "data engineering")

4. Customize the Obsidian vault skill

The obsidian-vault skill needs to know your vault path. Edit `~/.claude/skills/obsidian-vault/SKILL.md` and add your vault path to the description:

# Before:
description: Manage Obsidian vault operations. Handles markdown formatting...
# After:
description: Manage Obsidian vault operations for my vault at ~/path/to/your/vault. Handles markdown formatting...

Then customize `references/vault_structure.md` to match your actual folder hierarchy. The default is minimal (Programming, Projects, Daily Log, Templates). Add your own topic folders.

5. Customize tags

Both the obsidian-vault and daily-journal skills use tags. Look for `` comments in the reference files and add tags relevant to your work.

What was scanned

The files the safety scan read, as written by the repository's author and shown as plain text. Lines with a finding are marked.

README.md · README · 134 lines

View this file on GitHub (read at the repository's current version: the scan did not record which commit it read)

  1. # claude-adhd-skills
  2. (No ADHD required!)
  3. A set of Claude Code skills and hooks I use daily as scaffolding for staying organized while developing with AI agents. The key pieces are time awareness (so Claude knows when to tell me to stop), Obsidian integration (so I can store research and reconstruct what I was doing yesterday), and a nudge system (so promises to "wrap up in 30 minutes" actually stick).
  4. [Obsidian](https://obsidian.md/) is central to the workflow. It's where daily logs, meeting notes, research and ideas land, and because agents can read and write to the vault, it becomes a shared memory between sessions. I can point a new Claude instance at yesterday's journal entry and ask the agent to catch up instead of re-explaining context. Ideas get dumped into notes, marinate, and only the ones that survive get built. [obsidian-semantic](https://github.com/ravila4/obsidian-semantic-search) closes the loop, letting agents search notes by meaning, not just filenames.
  5. ## What's in the box
  6. ### Skills
  7. | Skill | What it does |
  8. |-------|-------------|
  9. | **daily-journal** | Conversational daily journaling. Asks you about your day instead of generating reports from commit logs. Writes to Obsidian. ([examples](examples/daily-log/)) |
  10. | **obsidian-vault** | Vault-aware note management: folder hierarchy, naming conventions, frontmatter, internal linking. |
  11. | **nudge** | Time-based reminders that fire on prompt submission. "Stop me at 11" or "remind me about standup in 30m". |
  12. | **test-driven-development** | Logic Gate + Iron Rule (based on obra's original Red/Green TDD skill): triage what needs tests, then strict test-first for anything with logic. (Just good general development practices, but mentioned in my CLAUDE.md) |
  13. ### Hooks
  14. | Hook | What it does |
  15. |------|-------------|
  16. | **date hook** | Injects current date and time into every prompt so Claude knows when it is. Enables time-aware journaling (morning/evening modes) |
  17. | **check_alerts.py** | Checks for due nudges on every prompt submission. |
  18. | **add_alert.py** | Adds a new timed nudge (`+30m`, `23:00`, etc.). |
  19. | **ack_alert.py** | Dismisses a fired nudge. |
  20. ### CLAUDE.md
  21. A starting point for your own `CLAUDE.md`. I have found that the following ADHD-specific patterns help me: break suggestions, pacing, focus tracking, and a working relationship that prioritizes asking over assuming.
  22. ## Installation
  23. ### 1. Copy skills to your Claude Code config
  24. ```bash
  25. # Clone the repo
  26. git clone https://github.com/ravila4/claude-adhd-skills.git
  27. cd claude-adhd-skills
  28. # Copy skills into your Claude Code skills directory
  29. cp -r skills/* ~/.claude/skills/
  30. # Copy hooks
  31. cp hooks/* ~/.claude/hooks/
  32. ```
  33. ### 2. Wire up the hooks
  34. Copy the hook configuration into your Claude Code settings. The settings file is at `~/.claude/settings.json` (global) or `~/.claude/settings.local.json` (local/private).
  35. See `settings.json.example` for the full config. The key hooks are:
  36. - **UserPromptSubmit**: Runs on every prompt. Shows current time and any due nudges.
  37. ```json
  38. {
  39. "hooks": {
  40. "UserPromptSubmit": [
  41. {
  42. "type": "command",
  43. "command": "echo \"Today is $(date '+%A, %B %d, %Y'). Time: $(date '+%H:%M')\"",
  44. "timeout": 5000
  45. },
  46. {
  47. "type": "command",
  48. "command": "python3 ~/.claude/hooks/check_alerts.py",
  49. "timeout": 5000
  50. }
  51. ]
  52. }
  53. }
  54. ```
  55. ### 3. Set up your CLAUDE.md
  56. Copy `CLAUDE.md` to `~/.claude/CLAUDE.md` and fill in the `{PLACEHOLDERS}`:
  57. ```bash
  58. cp CLAUDE.md ~/.claude/CLAUDE.md
  59. ```
  60. Edit the file and replace:
  61. - `{YOUR_NAME}`: your name
  62. - `{YOUR_ROLE}`: your job title or role
  63. - `{WHAT_YOU_DO}`: brief description of your work
  64. - `{YOUR_PLATFORM}`: your machine/OS (e.g., "MacBook Pro, macOS")
  65. - `{YOUR_WORK_DOMAIN}`: your work domain (e.g., "web development", "data engineering")
  66. ### 4. Customize the Obsidian vault skill
  67. The obsidian-vault skill needs to know your vault path. Edit `~/.claude/skills/obsidian-vault/SKILL.md` and add your vault path to the description:
  68. ```yaml
  69. # Before:
  70. description: Manage Obsidian vault operations. Handles markdown formatting...
  71. # After:
  72. description: Manage Obsidian vault operations for my vault at ~/path/to/your/vault. Handles markdown formatting...
  73. ```
  74. Then customize `references/vault_structure.md` to match your actual folder hierarchy. The default is minimal (Programming, Projects, Daily Log, Templates). Add your own topic folders.
  75. ### 5. Customize tags
  76. Both the obsidian-vault and daily-journal skills use tags. Look for `<!-- Add your own ... -->` comments in the reference files and add tags relevant to your work.
  77. ## Customization
  78. ### Adding domain-specific knowledge
  79. The `CLAUDE.md` has a "Technical Knowledge" section. Add your own domain expertise here: books, frameworks, tools. This shapes how Claude approaches problems with you.
  80. ### Extending the vault structure
  81. Add folders to `vault_structure.md` for your own knowledge domains. The skill uses this as a decision tree for where to place notes.
  82. ### Custom tags
  83. Tags live in `vault_structure.md` and `markdown_formatting.md`. Add your domain-specific tags to the taxonomy.
  84. ## Requirements
  85. - [Claude Code](https://docs.anthropic.com/en/docs/claude-code) CLI
  86. - Python 3.10+
  87. - [Obsidian](https://obsidian.md/) (for the vault and journal skills)
  88. - SQLite3 (usually pre-installed)
  89. - [obsidian-semantic](https://github.com/ravila4/obsidian-semantic-search) (optional, for semantic search in the obsidian-vault skill)
  90. ## License
  91. MIT

Ratings and comments

Sign in to rate this skill.

Sign in

Free to use. If it’s helped, pass it on.