end-week

Survey ObsidianPersonal vault activity and autonomously advance the highest-leverage project.

Updated Aug 14, 2012
One-click install
npx skills add https://github.com/dakotahp/dotfiles --skill end-week
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: end-week
Source: https://github.com/dakotahp/dotfiles/tree/main/dot_config/claude/skills/end-week
Command: npx skills add https://github.com/dakotahp/dotfiles --skill end-week

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Helps a vault-based knowledge worker run a concise weekly review that surveys recent activity, selects the highest-leverage project, and produces focused work and a weekly summary without ongoing user interaction.

Core Features & Use Cases

  • Autonomous survey of the past week's daily distillations, strategic Life Domains, Avoidance Radar, project Index files, and inbox stubs to build a complete picture of activity and neglect.
  • Project scoring and selection using strategic priority, neglect duration, idea-stub signals, and phase readiness, including archive-flagging for long-silent projects.
  • Depth dive and work product creation that reads project context, performs research as needed, creates agent-work notes with an empty ## Feedback section, and appends a "Last worked" entry to the project's Index.md.
  • Weekly output note that summarizes the week, domain gaps, project focus, produced work, decisions needed, and archive candidates.
  • Use case: Run after a week ends to let the agent choose one project to advance, create structured notes or decision briefs, and record a weekly summary in the ObsidianPersonal vault.

Quick Start

Run the end-week skill to review the most recently completed Sunday-to-Sunday week in your ObsidianPersonal vault, pick a project, produce work notes tagged agent-work, and write the weekly summary.

Frequently Asked Questions about end-week

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automate a weekly review in Obsidian to prioritize projects?

Automating an Obsidian weekly review involves surveying daily distillations, project Index files, and inbox stubs to score and select the highest-leverage project. The end-week skill autonomously reads vault activity, creates agent-work notes, and updates weekly archive notes without ongoing interaction.

What is project prioritization based on neglect duration in knowledge management?

Project prioritization via neglect duration scores projects by how long they have been silent alongside strategic priority and phase readiness. This knowledge management technique flags archive candidates for long-silent projects and selects the most high-leverage task to advance during a weekly review.

Can I use an autonomous agent to create work notes in an Obsidian vault?

Yes, an autonomous agent can create work notes in an Obsidian vault by reading project context and performing optional web research. The agent creates structured Markdown notes tagged agent-work with an empty Feedback section and appends a Last worked entry to the project Index.md file.

Does the weekly review workflow require manual selection of projects to advance?

No, the weekly review workflow does not require manual project selection. An autonomous agent surveys past vault activity, scores projects using strategic priority and neglect signals, and independently selects the highest-leverage project to produce focused work notes and decision briefs.

What do I need in my ObsidianPersonal vault to run an autonomous weekly review?

Running an autonomous weekly review requires an ObsidianPersonal vault with daily distillations, strategic Life Domains, an Avoidance Radar, project Index files, and inbox stubs. The agent needs read and write access, file modification timestamps for velocity signals, and Markdown note creation capabilities.

What happens to long-silent projects during an automated knowledge management review?

During an automated knowledge management review, long-silent projects are identified through neglect duration scoring and flagged as archive candidates. The weekly output note summarizes these domain gaps, archive candidates, and decisions needed so neglected projects are systematically surfaced.