sno-ai/sno-station / packages/memory/skills/extract-atomic-memory
extract-atomic-memory
VerifiedRead one conversation window and return every independently mutable claim it states, one record each, with who or what it is about, whether it happened or stands, and the words that carry its time. Used by the memory extraction model on every conversation window; the engine resolves dates, validates keys, and repairs format.
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 20.5 KB |
| references/account-for-turns.md | markdown | 583 B |
| references/calendar-meaning.md | markdown | 5.0 KB |
| references/capture-work.md | markdown | 4.9 KB |
| references/capture.md | markdown | 8.6 KB |
| references/enrichment.md | markdown | 6.7 KB |
| references/missing-durable-half.md | markdown | 335 B |
| references/progress-classification.md | markdown | 1.5 KB |
| references/resolve-subject.md | markdown | 1.2 KB |
| references/surrounding-context.md | markdown | 599 B |
| references/user-subject-guard.md | markdown | 2.0 KB |
references/calendar-meaning.md
View on GitHub# Understand time; delegate arithmetic
Read the complete conversation and the claim before deciding its time. A word by itself does
not say whether something is past, future, ongoing, hypothetical, quoted, or about another event.
Return one structured calendar instruction in `time`, and another in `ended_time` only for an
ending. Copy the supporting words into `temporal_phrase` / `ended_at_phrase`. Keep the claim
wording and its duration. Do not calculate a year, a date, a weekday offset, or an epoch yourself.
Not knowing when an event happened does not erase that event: keep its record with `unresolved`.
- `none`: a standing fact with no temporal assertion. An undated historical event is instead
`unresolved`. Do not label an event as happening now merely because the speaker reports it now.
- `unresolved`: the event time or its reference cannot be established from the supplied context.
This includes a duration with no known endpoint. Keep the fact and its uncertainty.
- `absolute`: copy the calendar components stated by the speaker into `year`, `month`, `day`,
`hour`, `minute` as applicable. A missing year may use the session year only when the context
establishes that year. Never fill an unknown month or day.
- `relative`: give the signed `amount` and `unit` relative to the session. Negative means before,
positive means after. The code adds or subtracts. For "I've known them for four years, since I
moved", the start/move is `amount: -4, unit: year`, not a future event. For a future four-year
course, distinguish its start from its end; a four-year duration alone does not date either.
When the statement links the start of a duration to another event, both events share that
start. In the friendship-and-move example, both the friendship start and the move receive
the same negative four-year instruction; the move is not undated. Judge that relationship
from the whole statement, not from whether each split claim repeats the time words.
The amount is a number the words state. "Recently", "lately", "a while ago", "a few weeks
ago", "the other day" and "soon" state none: they are `unresolved`, never a guessed number.
- `weekday`: give `day_name` as the English day name in lowercase (`monday` through `sunday`)
and `direction` (`previous` or `next`) for a strictly preceding/following occurrence: "last
Friday" is `{"kind": "weekday", "day_name": "friday", "direction": "previous", "precision":
"day"}`. Read abbreviations, spelling, language and the speaker's intended reference in
context, then name that day; never a number. The code finds that weekday; do not count days.
For resolved instructions give `precision`: `year`, `month`, `week`, `day`, or `minute`.
Preserve what is actually known. "Four years ago" normally supplies a year, not an anniversary
day. A named weekday supplies a day. A dated event with a stated clock supplies a minute.
`relative` amount 0 is available when the text establishes the event as current. Use `hour` and
`minute` for a stated clock on a relative day or weekday. Use `timezone` only when the source
names it; otherwise the code uses the session zone. The timezone field is a valid IANA zone
identifier or a fixed offset written as `+HH:MM` or `-HH:MM`, never an abbreviation. Interpret
an abbreviation from its context into that identifier or offset, and keep the stated hour and
minute unchanged. The code converts between zones. If the abbreviation is ambiguous in context,
return `unresolved`. For an unknown clock do not choose noon.
Resolve references from the full context, but do not borrow another event's time merely because
it is nearby. An explicit date for this same event supplies its date; an adjacent event keeps
its own. If the intended reference cannot be expressed by the supplied operations, use
`unresolved` rather than calculating an answer or inventing a new field.
For example, "That exhibition inspired me. Today I shared its photo" dates the sharing today,
not the inspiration. Without words dating the inspiration, keep its time unresolved. If an
earlier turn explicitly dates that same exhibition to last Friday, retain the weekday
instruction for the exhibition; never replace it with a guessed number of days. Copy the
actual dating words into `temporal_phrase`, not a clause that merely names the experience.
A weekend is a span, not an exact Saturday or Sunday, and no precision names it: date it by
the week that holds it. "Last weekend" is `relative`, `amount: -1`, `unit: week`,
`precision: week`; "this weekend" is `amount: 0`. Do not narrow a weekend to a single weekday
and do not leave it unresolved. "Last week" is the same instruction, `amount: -1`,
`unit: week`, `precision: week`; the code turns that into the week's date range. The amount
counts the stated unit, so "last week" is one week, never seven.
"Today", "tonight", "this morning" and "earlier today" are `relative`, `amount: 0`,
`unit: day`, `precision: day`; "yesterday" and "last night" are `amount: -1`; "tomorrow" is
`amount: 1`. A photo or message the speaker shares today is dated today.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| slack-gif-creatoranthropics/skillsKnowledge and utilities for creating animated GIFs optimized for Slack. Provides constraints, validation tools, and animation concepts. Use when users request animated GIFs for Slack like "make me a GIF of X doing Y for Slack." | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |
| ponytailDietrichGebert/ponytailLazy senior dev mode for any coding task: the smallest change that fully solves it, and a reply a busy human understands in one read. | Stars: 194k | Updated | Claude CodeCodex | Verified | Install |
| ponytail-debtDietrichGebert/ponytailHarvest every shortcut: comment into one debt ledger, so deferrals get tracked instead of forgotten. One-shot report. | Stars: 194k | Updated | Claude CodeCodex | Verified | Install |
| ponytail-debtDietrichGebert/ponytailList every `shortcut:` comment (and older `ponytail:` ones) as a debt ledger. One-shot report, changes nothing. Use for "ponytail debt", "what did ponytail defer", "list the shortcuts", /ponytail-debt. | Stars: 194k | Updated | Claude CodeCodex | Verified | Install |