prepforreset

Name: prepforreset
Author: cobibean

20stars0forks

How to install prepforreset?

cobibean/agent-memory-wiki/prepforreset

$npx -y skills add cobibean/agent-memory-wiki --skill prepforreset

Installs into the current project.

Summary

Use when the user says “prep for reset”, “prep for a context window”, “prepare for a context window”, or invokes /prepforreset. Create curated Obsidian Daily Log and Session Log notes, then return a lean copy/paste handoff.

Files · 1

View on GitHub

SKILL.md

1	# Prep for Reset
2
3	## Overview
4
5	Use this skill to preserve session or day nuance before a context reset, at the end of a work block, or whenever the user asks the agent to “prep for reset.”
6
7	The primary artifact is a curated Obsidian memory-wiki update: a standalone-useful Daily Log plus a deeper Session Log. The secondary artifact is a short copy/paste handoff in chat so the next context can restart smoothly.
8
9	This is not transcript dumping. Distill what future humans and agents need: what happened, why it mattered, decisions, rejected options when important, lessons/gotchas, artifacts, open loops, routing candidates, and source references.
10
11	## When to Use
12
13	Use when:
14
15	- the user says “prep for reset”
16	- the user says “prepare for a context window”
17	- the user says “prep for a context window”
18	- the user invokes `/prepforreset`
19	- the user asks for an end-of-session or end-of-day Obsidian memory/wiki log
20	- a context reset is likely and durable notes should be written first
21
22	Do not use for raw transcript archival, ordinary short-term memory writes, secret storage, or mutation of non-Obsidian stores unless separately requested.
23
24	## Required Companion Skill
25
26	Before writing any vault file, load and follow the `obsidian` skill. It owns vault resolution and low-level vault conventions.
27
28	If the vault path is missing or ambiguous, ask for it instead of writing elsewhere. Resolve canonical paths before writing and refuse any write whose final resolved path is outside the resolved vault root.
29
30	## Slash Command Discovery
31
32	Hermes automatically exposes installed skills as slash commands by normalizing the skill `name` from frontmatter. Because this skill is named `prepforreset`, it is invoked as:
33
34	```text
35	/prepforreset
36	```
37
38	after the gateway or CLI skill command cache has reloaded. There is no separate plugin required for Hermes.
39
40	For other agent runtimes, create a command alias that loads and follows this skill.
41
42	## Folder and Filename Conventions
43
44	Default folders, relative to the Obsidian vault:
45
46	```text
47	Daily Logs/
48	Session Logs/
49	Janitor Reports/
50	```
51
52	Daily log:
53
54	```text
55	Daily Logs/YYYY-MM-DD.md
56	```
57
58	Session log:
59
60	```text
61	Session Logs/YYYY-MM-DD-<auto-short-title>.md
62	```
63
64	Slug rules:
65
66	- Always prefix with the local date: `YYYY-MM-DD-`.
67	- Generate a concise lowercase slug from the real topic.
68	- Prefer 3–6 words.
69	- Include project or agent names when obvious.
70	- Avoid generic slugs such as `daily-work`, `session-notes`, or `context-reset`.
71	- If a note already exists, append `-2`, `-3`, etc. rather than overwriting.
72
73	## Minimal Frontmatter
74
75	Daily log:
76
77	```yaml
78	---
79	type: daily-log
80	date: YYYY-MM-DD
81	agent: <agent-name>
82	profile: <profile-name>
83	tags:
84	- daily-log
85	---
86	```
87
88	Session log:
89
90	```yaml
91	---
92	type: session-log
93	date: YYYY-MM-DD
94	title: <Human Title>
95	agent: <agent-name>
96	profile: <profile-name>
97	trigger: prepforreset
98	tags:
99	- session-log
100	- context-reset
101	---
102	```
103
104	Add `review-needed` only when the note contains review candidates or uncertainty. Include `agent` and `profile` when known; omit unknown fields rather than inventing metadata.
105
106	## Daily Log Shape
107
108	Daily logs should be standalone useful, not merely indexes. Create the note if missing; otherwise append/update conservatively.
109
110	Before appending a Session Log link, check whether the same target link already exists in the Daily Log. If it exists, update the one-line outcome only when clearly beneficial; do not create duplicate links on rerun.
111
112	Recommended sections:
113
114	```md
115	# Daily Log — YYYY-MM-DD
116
117	## Day summary
118
119	## Sessions
120	- [[Session Logs/YYYY-MM-DD-topic\|Topic]] — one-line outcome.
121
122	## Decisions
123
124	## Lessons / gotchas
125
126	## Open loops
127
128	### Explicit
129
130	### Inferred
131
132	## Routing candidates
133
134	## Artifacts
135
136	## Janitor reports
137	```
138
139	## Session Log Shape
140
141	Recommended sections:
142
143	```md
144	# Session Log — YYYY-MM-DD — Topic
145
146	## Summary
147
148	## Context
149
150	## Decisions
151
152	## Alternatives considered
153
154	## Lessons / gotchas
155
156	## Artifacts touched
157
158	## Open loops
159
160	### Explicit
161
162	### Inferred
163
164	## Routing candidates
165
166	## Source references
167	```
168
169	Use concise structured sections with enough narrative to preserve nuance. Do not write stiff “AI retrieval optimized” prose; optimize through stable headings, specific entities, dates, wikilinks, artifact paths, source references, and explicit rationale.
170
171	## Decisions and Alternatives
172
173	Preserve rejected alternatives based on importance:
174
175	- Minor operational choice: final decision only, maybe one-line rationale.
176	- Medium choice: final decision plus brief rejected alternatives.
177	- Strategic or likely-to-be-revisited choice: include m

People who liked this also viewed

6 picks

Type

prepforreset

20stars0forks

View on GitHub

How to install prepforreset?

cobibean/agent-memory-wiki/prepforreset

$npx -y skills add cobibean/agent-memory-wiki --skill prepforreset

Installs into the current project.

Summary

Files · 1

View on GitHub

SKILL.md

1	# Prep for Reset
2
3	## Overview
4
5	Use this skill to preserve session or day nuance before a context reset, at the end of a work block, or whenever the user asks the agent to “prep for reset.”
6
7	The primary artifact is a curated Obsidian memory-wiki update: a standalone-useful Daily Log plus a deeper Session Log. The secondary artifact is a short copy/paste handoff in chat so the next context can restart smoothly.
8
9	This is not transcript dumping. Distill what future humans and agents need: what happened, why it mattered, decisions, rejected options when important, lessons/gotchas, artifacts, open loops, routing candidates, and source references.
10
11	## When to Use
12
13	Use when:
14
15	- the user says “prep for reset”
16	- the user says “prepare for a context window”
17	- the user says “prep for a context window”
18	- the user invokes `/prepforreset`
19	- the user asks for an end-of-session or end-of-day Obsidian memory/wiki log
20	- a context reset is likely and durable notes should be written first
21
22	Do not use for raw transcript archival, ordinary short-term memory writes, secret storage, or mutation of non-Obsidian stores unless separately requested.
23
24	## Required Companion Skill
25
26	Before writing any vault file, load and follow the `obsidian` skill. It owns vault resolution and low-level vault conventions.
27
28	If the vault path is missing or ambiguous, ask for it instead of writing elsewhere. Resolve canonical paths before writing and refuse any write whose final resolved path is outside the resolved vault root.
29
30	## Slash Command Discovery
31
32	Hermes automatically exposes installed skills as slash commands by normalizing the skill `name` from frontmatter. Because this skill is named `prepforreset`, it is invoked as:
33
34	```text
35	/prepforreset
36	```
37
38	after the gateway or CLI skill command cache has reloaded. There is no separate plugin required for Hermes.
39
40	For other agent runtimes, create a command alias that loads and follows this skill.
41
42	## Folder and Filename Conventions
43
44	Default folders, relative to the Obsidian vault:
45
46	```text
47	Daily Logs/
48	Session Logs/
49	Janitor Reports/
50	```
51
52	Daily log:
53
54	```text
55	Daily Logs/YYYY-MM-DD.md
56	```
57
58	Session log:
59
60	```text
61	Session Logs/YYYY-MM-DD-<auto-short-title>.md
62	```
63
64	Slug rules:
65
66	- Always prefix with the local date: `YYYY-MM-DD-`.
67	- Generate a concise lowercase slug from the real topic.
68	- Prefer 3–6 words.
69	- Include project or agent names when obvious.
70	- Avoid generic slugs such as `daily-work`, `session-notes`, or `context-reset`.
71	- If a note already exists, append `-2`, `-3`, etc. rather than overwriting.
72
73	## Minimal Frontmatter
74
75	Daily log:
76
77	```yaml
78	---
79	type: daily-log
80	date: YYYY-MM-DD
81	agent: <agent-name>
82	profile: <profile-name>
83	tags:
84	- daily-log
85	---
86	```
87
88	Session log:
89
90	```yaml
91	---
92	type: session-log
93	date: YYYY-MM-DD
94	title: <Human Title>
95	agent: <agent-name>
96	profile: <profile-name>
97	trigger: prepforreset
98	tags:
99	- session-log
100	- context-reset
101	---
102	```
103
104	Add `review-needed` only when the note contains review candidates or uncertainty. Include `agent` and `profile` when known; omit unknown fields rather than inventing metadata.
105
106	## Daily Log Shape
107
108	Daily logs should be standalone useful, not merely indexes. Create the note if missing; otherwise append/update conservatively.
109
110	Before appending a Session Log link, check whether the same target link already exists in the Daily Log. If it exists, update the one-line outcome only when clearly beneficial; do not create duplicate links on rerun.
111
112	Recommended sections:
113
114	```md
115	# Daily Log — YYYY-MM-DD
116
117	## Day summary
118
119	## Sessions
120	- [[Session Logs/YYYY-MM-DD-topic\|Topic]] — one-line outcome.
121
122	## Decisions
123
124	## Lessons / gotchas
125
126	## Open loops
127
128	### Explicit
129
130	### Inferred
131
132	## Routing candidates
133
134	## Artifacts
135
136	## Janitor reports
137	```
138
139	## Session Log Shape
140
141	Recommended sections:
142
143	```md
144	# Session Log — YYYY-MM-DD — Topic
145
146	## Summary
147
148	## Context
149
150	## Decisions
151
152	## Alternatives considered
153
154	## Lessons / gotchas
155
156	## Artifacts touched
157
158	## Open loops
159
160	### Explicit
161
162	### Inferred
163
164	## Routing candidates
165
166	## Source references
167	```
168
169	Use concise structured sections with enough narrative to preserve nuance. Do not write stiff “AI retrieval optimized” prose; optimize through stable headings, specific entities, dates, wikilinks, artifact paths, source references, and explicit rationale.
170
171	## Decisions and Alternatives
172
173	Preserve rejected alternatives based on importance:
174
175	- Minor operational choice: final decision only, maybe one-line rationale.
176	- Medium choice: final decision plus brief rejected alternatives.
177	- Strategic or likely-to-be-revisited choice: include m

People who liked this also viewed

6 picks

Type