원클릭으로
situate-daily-notes
Situate yourself by generating a 1-page situation report and maintaining Obsidian-style daily summary notes.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
메뉴
Situate yourself by generating a 1-page situation report and maintaining Obsidian-style daily summary notes.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
| name | situate-daily-notes |
| description | Situate yourself by generating a 1-page situation report and maintaining Obsidian-style daily summary notes. |
| distribution | private |
Use this on demand when the user asks you to catch up, or as the required daily-notes phase of close-of-day.
Do not run it automatically at session start.
situate.ts — full situation report + rolling memory refresh + note status checkdaily-notes.ts — generate or refresh daily-note skeletons onlybun run /workspace/.pi/skills/situate-daily-notes/situate.ts
This:
notes/memory/For web:* scopes, all web session trees are included and labelled so parallel branches stay distinguishable.
Notes live at notes/daily/YYYY-MM-DD.md and begin with YAML front matter like:
---
date: 2026-03-04
summarised_until: 2026-03-04T17:55:35.286Z
messages_total: 25
messages_user: 10
messages_assistant: 15
session_trees: 2
session_chats: 4
first_message: 2026-03-04T12:31:03.860Z
last_message: 2026-03-04T17:55:17.309Z
scope_mode: all-web-session-trees
scope_anchor: web:default
---
Rolling memory outputs live under notes/memory/:
notes/memory/current-state.mdnotes/memory/recent-context.mdnotes/memory/MEMORY.mdDaily notes summarise activity. The message database is the source of truth for the full transcript.
When situate.ts or daily-notes.ts reports notes that need summary work:
messages tool as the primary transcript source<!-- NEEDS_SUMMARY --> or the update markersummarised_until to the last covered message timestampIf a note is only partially behind, append a short update section and advance the watermark rather than rewriting the whole note.
Keep the prose terse, dense, and matter-of-fact. Preserve existing real summaries; only fill placeholders or append updates.
| Flag | Default | Description |
|---|---|---|
--days <n> | 7 | How many days of history to include |
--out <path> | /workspace/exports/situation.md | Situation report output path |
--update-notes | off | Refresh note metadata and memory outputs while generating the report |
bun run /workspace/.pi/skills/situate-daily-notes/daily-notes.ts [--days <n>] [--force]
For daily-note writing, prefer the messages tool over a separate full-transcript export unless you specifically need a transcript artifact.
ARCHIVED — project work items are tracked in GitHub Issues and GitHub Projects. Use the github-issues skill when installed, or use gh directly.
Diagnose and fix piclaw extension issues (imports, DB init errors, watcher perms), update skel, and restart safely.
Search the web via SearXNG (or DuckDuckGo fallback) and optionally fetch result pages as raw Markdown content.
Search via SearXNG (or DuckDuckGo fallback), fetch top results, and return sentence-level summaries plus optional converted page content.
Fetch a user's recent tweets (tweets, replies, retweets) using Playwright + Nitter fallbacks and produce compact JSON/Markdown summaries.
Write and review concise technical documentation using a plain-English voice guide and anti-trope filter. Use for READMEs, design notes, runbooks, API documentation, release notes, and pull-request text.