personal memory agent
feat: add solstone user-wide skill for cross-project journal queries
New SKILL.md installs via `npx skills add` to ~/.claude/skills/solstone/,
giving any AI agent outside the solstone project a read-only query interface
to the journal — recall, who, today, transcript, people, and status.
Makefile updated to include user-wide skill install in `make install`.
Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
+190
+4
Makefile
+4
Makefile
···
50
50
echo "Done! (worktree detected, skipping ~/.local/bin/sol symlink)"; \
51
51
fi
52
52
@$(MAKE) --no-print-directory skills
53
+
@if [ -d .git ] && [ -f skills/solstone/SKILL.md ]; then \
54
+
echo "Installing solstone skill user-wide..."; \
55
+
npx skills add ./skills/solstone -g -a claude-code -y; \
56
+
fi
53
57
@touch .installed
54
58
55
59
# Generate lock file if missing
+186
skills/solstone/SKILL.md
+186
skills/solstone/SKILL.md
···
1
+
---
2
+
name: solstone
3
+
version: 1.0.0
4
+
description: >
5
+
Query your solstone journal — search memories, look up people and relationships,
6
+
check today's events and todos, read meeting transcripts, and get relationship
7
+
briefings from your co-brain. Requires solstone to be installed with the sol CLI
8
+
on PATH (~/.local/bin/sol).
9
+
TRIGGER: solstone, my journal, what happened, who is, meeting with, search my
10
+
memory, what do I know about, entity, co-brain, look up, recall, remember,
11
+
transcript, relationship, who have I been talking to, what's on my plate.
12
+
---
13
+
14
+
# solstone — journal query interface
15
+
16
+
Read-only query interface to your solstone journal. Use this skill to search memories, look up people, check today's events, read transcripts, and get relationship briefings — all from any project context.
17
+
18
+
## Prerequisites
19
+
20
+
The `sol` CLI must be on PATH. Quick check:
21
+
22
+
```bash
23
+
sol help
24
+
```
25
+
26
+
If this fails, solstone is not installed. Install it from the solstone project: `make install`.
27
+
28
+
## Capabilities
29
+
30
+
### recall — search your memory
31
+
32
+
Search the journal index for anything matching a query.
33
+
34
+
```bash
35
+
sol call journal search "<query>"
36
+
sol call journal search "<query>" --day 20260327
37
+
sol call journal search "<query>" --facet work
38
+
sol call journal search "<query>" --day-from 20260320 --day-to 20260327
39
+
```
40
+
41
+
Dates use `YYYYMMDD` format. Omit `--day` to search all days. Omit `--facet` to search all facets.
42
+
43
+
### who — entity intelligence
44
+
45
+
Look up what the journal knows about a person, company, or project.
46
+
47
+
```bash
48
+
# Full intelligence briefing for a named entity
49
+
sol call entities intelligence "<name>"
50
+
51
+
# Search for entities by text, type, or activity
52
+
sol call entities search --query "<query>"
53
+
54
+
# See observations recorded for an entity (requires facet)
55
+
sol call entities observations "<entity_name>" --facet "<facet>"
56
+
```
57
+
58
+
`intelligence` gives the richest answer — use it first, then `search` if the entity isn't attached.
59
+
60
+
### today — what's happening now
61
+
62
+
Combine these commands to get a full picture of the current day:
63
+
64
+
```bash
65
+
# Today's events (imports, captures, activity)
66
+
sol call journal events
67
+
68
+
# Upcoming todos
69
+
sol call todos upcoming
70
+
71
+
# Calendar events for today
72
+
sol call calendar list
73
+
74
+
# Latest facet news
75
+
sol call journal news "<facet>"
76
+
```
77
+
78
+
### transcript — meeting transcripts
79
+
80
+
Read what was said during meetings or any recorded time.
81
+
82
+
```bash
83
+
# List transcript coverage ranges for a day
84
+
sol call transcripts scan
85
+
sol call transcripts scan 20260327
86
+
87
+
# Read transcript content for a specific time range
88
+
sol call transcripts read
89
+
sol call transcripts read 20260327
90
+
sol call transcripts read 20260327 --start 14 --length 2
91
+
92
+
# Transcript stats for a month
93
+
sol call transcripts stats
94
+
```
95
+
96
+
`scan` first to see what's available, then `read` with `--start` (hour, 24h format) and `--length` (hours) to narrow down.
97
+
98
+
### people — relationship strength
99
+
100
+
See who the strongest relationships are, or who's been active recently.
101
+
102
+
```bash
103
+
# Overall relationship strength ranking
104
+
sol call entities strength
105
+
106
+
# Strength since a specific date
107
+
sol call entities strength --since 20260320
108
+
109
+
# Strength within a facet
110
+
sol call entities strength --facet work
111
+
```
112
+
113
+
### status — system health
114
+
115
+
Check if solstone is running and how much data exists.
116
+
117
+
```bash
118
+
# Journal storage summary (days, facets, size)
119
+
sol call journal storage-summary
120
+
121
+
# Local diagnostics (no network)
122
+
sol call support diagnose
123
+
```
124
+
125
+
## Environment
126
+
127
+
The `sol` CLI uses three environment variables that default sensibly:
128
+
129
+
- `SOL_DAY` — defaults to today (`YYYYMMDD`)
130
+
- `SOL_FACET` — defaults to all facets
131
+
- `SOL_SEGMENT` — defaults to no segment
132
+
133
+
External callers should never need to set these. The commands above use explicit flags (`--day`, `--facet`) when narrowing scope is needed.
134
+
135
+
## Composing queries
136
+
137
+
For richer answers, combine multiple commands:
138
+
139
+
**"Brief me on today"** — events + todos + calendar + recent entity strength:
140
+
```bash
141
+
sol call journal events
142
+
sol call todos upcoming
143
+
sol call calendar list
144
+
sol call entities strength --since $(date +%Y%m%d)
145
+
```
146
+
147
+
**"Prep me for a meeting with X"** — entity intelligence + recent transcript mentions + relationship strength:
148
+
```bash
149
+
sol call entities intelligence "<name>"
150
+
sol call journal search "<name>" --day-from 20260320
151
+
sol call entities strength --since 20260301
152
+
```
153
+
154
+
**"What did I miss yesterday?"** — yesterday's events + transcripts + news:
155
+
```bash
156
+
sol call journal events --day 20260326
157
+
sol call transcripts scan 20260326
158
+
sol call journal news "<facet>" --day 20260326
159
+
```
160
+
161
+
## Output format
162
+
163
+
Most commands output plain text by default. Many support `--json` for structured output. Prefer plain text for human-readable answers; use `--json` when you need to process the data further.
164
+
165
+
## What you cannot do
166
+
167
+
This is a **read-only** interface. The journal is the person's private space. You cannot:
168
+
169
+
- Create, delete, or modify facets
170
+
- Add or complete todos
171
+
- Attach or modify entities
172
+
- Write news or observations
173
+
- Run pipeline operations (dream, indexer, transcribe)
174
+
- Access internal agent state or orchestration
175
+
176
+
If a task requires writing to the journal, it must be done from within the solstone project context using sol's internal skills.
177
+
178
+
## Error handling
179
+
180
+
If `sol` is not found on PATH or returns an error:
181
+
182
+
- **"command not found: sol"** — solstone is not installed. The user needs to run `make install` in their solstone project.
183
+
- **"journal not found"** or empty output — the journal directory doesn't exist or has no data yet. solstone may be installed but not yet initialized.
184
+
- **Connection errors from `sol call support`** — `diagnose` is local-only and should always work. Other support commands (`search`, `article`) contact the support portal and may fail if offline.
185
+
186
+
Do not retry failed commands. Report the error clearly so the user can investigate.