Agent-Skills.md

Agent Skills: Journal Manager Skill

Creates and manages Obsidian work journals. Automatically writes journals after experiments, analyses, and key decisions. Periodically reviews, consolidates, archives, and promotes journal entries to permanent documentation.

UncategorizedID: fubira/claude-code-settings/journal-manager
1

Install this agent skill to your local

pnpm dlx add-skill https://github.com/fubira/claude-code-settings/tree/HEAD/skills/journal-manager

Skill Files

Browse the full folder contents for journal-manager.

Download Skill

Loading file tree…

skills/journal-manager/SKILL.md

Skill Metadata

Name
journal-manager
Description
Writes and maintains work journals under WORK/ in the Obsidian vault. Use after an experiment or analysis produces measured results worth carrying across sessions, and when consolidating or archiving existing journals. Do not use for ordinary implementation work or as a progress log.

Journal Manager Skill

Create and manage Obsidian work journals. Record "what I thought at this point" as thinking logs.

Activation Triggers

Create (proactive): After experiments/analyses, decisions, incident responses, comparisons, or user request Organize: /journal-review, /journal-cleanup, auto-suggest when active files > 20

Journal Location

  • Path: WORK/{ORG}_{PROJECT}/journal/YYYY-MM-DD_HHmm_topic.md (relative to the Obsidian vault root defined in the global CLAUDE.md "Obsidian" section)
  • Date in JST. Topic in hyphenated English or Japanese (keep short)

auto memory vs Journal

  • auto memory: Technical facts and patterns (long-lived) → .claude/projects/*/memory/
  • Journal: Chronological thinking process (short-to-mid lived) → Obsidian journal/

Part 1: Creating Journals

Templates

Experiment/Analysis: Background → Conditions/Setup → Results (numeric tables) → Findings → Conclusion/Next actions Decision: Context → Options → Judgment and reasoning → Trade-offs → Next actions Incident Response: Situation → Root cause → Actions taken → Prevention measures → Lessons learned Work Log: Tasks done → Design decisions (if any) → TODOs (remaining)

Principles

  • One topic per file (multiple per day OK). Use tables for numeric data
  • Record "what I thought at this point" — valuable even if conclusions change later
  • Place persistent data in the parent directory of journal/
  • Do NOT record: code diffs (Git handles that), trivial task logs, technical facts suited for auto memory

Part 2: Review and Organization

Runs only on /journal-review / /journal-cleanup (or when suggesting organization at 20+ active files). Read references/review.md for the 3-phase procedure (Review → Organize → Promotion Check) before starting.

Directory Structure

{project}/journal/
├── *.md              # Active
├── archives/         # Consolidated/obsolete originals
└── deferred/         # Future research topics

Important Notes

  • Archive means move, not delete (originals kept in archives/)
  • Never drop data during consolidation (faithfully copy numeric tables)
  • When in doubt, keep. Create aggressively, organize cautiously
  • Deferred entries must state concrete resume conditions (not just "someday")