agentleFS
Sign inStart free
chipoto69chipoto69/claude-skills/vaultage-daily/SKILL.md

vaultage-daily

Skill2 starsChanged 10 months agoMITView on GitHub

End-of-day reflection workflow for the Obsidian vault. Set your vault path via environment variable:

The file

We split this skill into the rules it gives an agent

1 rule. About 0 are common, 1 is distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Create daily review note at:

    line 26

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

Vaultage Daily Review Skill

End-of-day reflection workflow for the Obsidian vault.

Configuration

Set your vault path via environment variable:

export VAULTAGE_PATH="$HOME/Documents/Vaultage"  # Customize to your vault location

Trigger Phrases

  • "daily review"
  • "end of day review"
  • "what did I work on today"

Process

  1. Find today's modified notes:
find "$VAULTAGE_PATH" -name "*.md" -mtime 0 -type f 2>/dev/null | grep -v ".obsidian" | grep -v ".trash"
  1. Analyze progress and insights from modified notes
  2. Create daily review note at:
$VAULTAGE_PATH/06_Metadata/Daily/YYYY-MM-DD - Daily Review.md

Output Format

---
date: {{date}}
type: daily-review
---

# Daily Review - {{date}}

## Accomplished
- [What was completed]

## Progress Made
- [Incremental progress on ongoing work]

## Insights Captured
- [New learnings or realizations]

## Blocked On
- [Obstacles encountered]

## Questions Raised
- [New questions that emerged]

## Tomorrow's Focus
1. [Priority 1]
2. [Priority 2]
3. [Priority 3]

## Open Loops
- [Unfinished threads to revisit]

PARA Structure

  • 00_Inbox: Unprocessed items
  • 01_Projects: Active projects with deadlines
  • 02_Areas: Ongoing responsibilities
  • 03_Resources: Reference materials
  • 04_Archive: Completed/inactive items
  • 06_Metadata: System files, daily reviews, templates

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.

Check your setup, free