agentleFS
chuckplayerchuckplayer/claude-agent-pack/skills/obsidian-recap/SKILL.md

obsidian-recap

Skill8 starsChanged 35 days agoMITView on GitHub

Synthesize a daily recap of Claude activity for the current project and write it to the Obsidian vault. Reads the day's auto-logged session notes, git history, and current-state note, then produces a narrative "what happened today" rollup that the link-only daily note lacks. Use when someone says "recap today", "daily recap", "write a recap", "summarize today's work", "obsidian recap", "wrap up the day", "end-of-day summary". Defaults to today; accepts a date argument (YYYY-MM-DD). Requires OBSIDIAN_VAULT_PATH to be set.

The file

Show its rules and text

We split this skill into the rules it gives an agent

15 rules. About 0 are common, 11 are distinctive, and 4 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈11

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 4

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Read OBSIDIAN_VAULT_PATH from the environment:

    line 30
  2. Distinctive:

    If empty, stop and tell the user:

    line 34
  3. Very specific:

    Target date: default to today (YYYY-MM-DD).

    line 50
  4. Very specific:

    Session notes for the date: Use Glob on <project_base>/sessions/<YYYY-MM-DD>-*.md and read each.

    line 67
  5. Distinctive:

    If not a git repo, skip silently.

    line 80
  6. Distinctive:

    If no session notes and no commits exist for the date, stop gracefully:

    line 82
  7. Distinctive:

    Do not invent content or widen the date range on your own.

    line 86
  8. Distinctive:

    Write a narrative recap in this format.

    line 90
  9. Distinctive:

    Every "What shipped" bullet must trace to a real commit or changed file — do not claim work that has no artifact.

    line 123
  10. Distinctive:

    Do not attempt the REST API here.

    line 145
  11. Distinctive:

    Synthesis, not transcription: If you find yourself copying prompt text verbatim, stop and summarize instead.

    line 160
  12. Distinctive:

    Ground every claim in an artifact: No commit or changed file → no "What shipped" bullet.

    line 162
  13. Very specific:

    Read-only against source notes: Only the recap file and the daily note are written.

    line 167
  14. Distinctive:

    Do not widen the date range: If the target date has no activity, say so and stop — do not silently recap a different day.

    line 169
  15. Distinctive:

    If not in a git repo, skip the git step and build the recap from session notes alone.

    line 171

≈ “Common” is an estimate: at least 1 in 5 of the 364,980 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.

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

Obsidian Recap

Produce a synthesized, narrative daily recap for the current project and persist it to the vault. The Stop hook already writes one session note per session and a link-only daily note; those are raw artifacts. This skill reads those artifacts and turns them into prose a human can skim weeks later.

This is synthesis, not transcription. The recap explains what was accomplished and why, collapsing many sessions into a coherent story. It is the LLM's job precisely because a hook cannot summarize.

Recaps land in <projects_folder>/<repo>/recaps/<YYYY-MM-DD>.md (or Claude/Projects/<repo>/recaps/ if no projects folder is configured) and are linked into that day's daily note automatically.

Step 1 — Check configuration

Read OBSIDIAN_VAULT_PATH from the environment:

  • Bash: bash -c 'echo $OBSIDIAN_VAULT_PATH'
  • PowerShell: $env:OBSIDIAN_VAULT_PATH

If empty, stop and tell the user:

"OBSIDIAN_VAULT_PATH is not set. Re-run install.sh and provide your vault path when prompted, or add it manually to ~/.claude/settings.json under the env key."

Also read:

  • OBSIDIAN_PROJECTS_FOLDER (empty string if unset)
  • CLAUDE_PROJECT_DIR (or fall back to current working directory)

You do not need the REST API variables — obsidian-writer owns the transport chain (CLI → REST API → filesystem) and reads them from the environment itself. Never pass the API key to an agent; it would land in the dispatch payload and the transcript.

Step 2 — Determine date and scope

Target date: default to today (YYYY-MM-DD). If the user passed a date argument (e.g., /obsidian-recap 2026-06-30), use that instead. Reject anything that is not a valid YYYY-MM-DD string and ask for the correct format.

Project slug: basename of CLAUDE_PROJECT_DIR (or cwd), lowercased, non-alphanumeric characters replaced with hyphens, max 30 characters.

Effective folder:

effective_folder = OBSIDIAN_PROJECTS_FOLDER || "Claude/Projects"
project_base     = <OBSIDIAN_VAULT_PATH>/<effective_folder>/<project_slug>

Step 3 — Gather the day's raw material

Collect, in this order (skip any source that is missing — do not fail):

  1. Session notes for the date. Use Glob on <project_base>/sessions/<YYYY-MM-DD>-*.md and read each. These carry the frontmatter, recent commits, changed files, prompts, agents invoked, and (on SessionEnd) captured decisions.
  2. The daily note <project_base>/daily/<YYYY-MM-DD>.md — the link/GUID list of sessions that ran that day (useful to confirm session count).
  3. Current-state note <project_base>/_current.md — the rolling "Where we left off" and "Open threads" (context for framing next steps).
  4. Git history for the date, via the Bash tool from CLAUDE_PROJECT_DIR:
    git log --since="<YYYY-MM-DD> 00:00" --until="<YYYY-MM-DD> 23:59" \
      --pretty=format:'%h %s' --no-merges
    If not a git repo, skip silently.

If no session notes and no commits exist for the date, stop gracefully:

"No Claude activity found for <project_slug> on <date>. Nothing to recap."

Do not invent content or widen the date range on your own.

Step 4 — Synthesize the recap

Write a narrative recap in this format. Keep it tight (under ~300 words of prose, excluding lists). Collapse repetition: if five sessions all advanced one feature, that is one story beat, not five.

---
type: claude/recap
project: <project>
date: <YYYY-MM-DD>
sessions: <count of session notes read>
tags: [claude, recap, daily, project/<project_slug>]
---

# Recap — <project> — <YYYY-MM-DD>

## Summary
<2-4 sentence narrative of what the day was about and what moved forward.>

## What shipped
- <bullet per meaningful change, grounded in commits / changed files>

## Decisions
- <bullet per decision captured in the session notes; omit the section if none>

## Open threads / next
- <bullet per unfinished item, drawn from _current.md open threads and session next-steps>

## Sessions
- [[<vault-relative-session-link-1>]] (<HH:MM>)
- [[<vault-relative-session-link-2>]] (<HH:MM>)

Grounding rules:

  • Every "What shipped" bullet must trace to a real commit or changed file — do not claim work that has no artifact.
  • Pull "Decisions" only from the ## Decisions sections of session notes. Do not manufacture decisions from prompts.
  • Wikilinks are vault-relative: strip the OBSIDIAN_VAULT_PATH prefix, convert backslashes to forward slashes, drop the .md extension.

Step 5 — Dispatch obsidian-writer

Vault-relative recap path: <effective_folder>/<project_slug>/recaps/<YYYY-MM-DD>.md (use forward slashes).

Invoke the obsidian-writer agent with:

  • write_mode: recap
  • vault_path: value of OBSIDIAN_VAULT_PATH
  • projects_folder: value of OBSIDIAN_PROJECTS_FOLDER (empty string if unset)
  • project: basename of CLAUDE_PROJECT_DIR or current working directory
  • date: target date (YYYY-MM-DD)
  • recap_markdown: the full markdown from step 4
  • session_count: number of session notes read

Do not attempt the REST API here. obsidian-writer tries the Obsidian CLI, then the REST API, then the filesystem, and reports which one succeeded.

Step 6 — Confirm

Report the recap path and write method. Example:

"Daily recap written to <vault-folder>/claude-agent-pack/recaps/2026-07-01.md (via Obsidian CLI)"

or:

"Daily recap written to <vault-folder>/claude-agent-pack/recaps/2026-07-01.md (filesystem)"

Gotchas

  • Synthesis, not transcription. If you find yourself copying prompt text verbatim, stop and summarize instead.
  • Ground every claim in an artifact. No commit or changed file → no "What shipped" bullet.
  • Idempotent by design. Re-running for the same date overwrites that date's recap (a single PUT / single Write). This is intentional — the recap reflects the latest reading of the day's notes.
  • Read-only against source notes. Only the recap file and the daily note are written; never modify session notes, _current.md, or captures.
  • Do not widen the date range. If the target date has no activity, say so and stop — do not silently recap a different day.
  • If not in a git repo, skip the git step and build the recap from session notes alone.

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.