personal memory agent
support: clarify TOS path, add Invoke via Bash + Gotchas, reformat TRIGGER
Clarify that tos.txt lives at <journal_root>/apps/support/portal/tos.txt
(resolved via journal app storage) to remove any ambiguity about source
tree vs. runtime location. Reformat TRIGGER into playbook style with
task-intent dash prefix + literal command list. Add Invoke via Bash line
and a Gotchas section (KB-first on create, --product default, diagnostic
leakage, attachment ordering).
Part of skills audit req_loq3e2lk pass 1+2.
+16
-4
+16
-4
apps/support/talent/support/SKILL.md
+16
-4
apps/support/talent/support/SKILL.md
···
5
5
sol pbc. Manage open tickets, attach files, check announcements, and run
6
6
local diagnostics. Use when the owner needs help with solstone, wants to
7
7
report a bug, request a feature, check for known issues, or give feedback.
8
-
TRIGGER: support, bug report, feature request, feedback, help, knowledge
9
-
base, file a ticket, known issues, announcements, diagnostics.
8
+
TRIGGER: any support task — filing bug reports, requesting features,
9
+
submitting feedback, searching the knowledge base, checking announcements,
10
+
managing open tickets, running local diagnostics. Commands:
11
+
sol call support create, sol call support search, sol call support article,
12
+
sol call support attach, sol call support feedback, sol call support list,
13
+
sol call support show, sol call support reply, sol call support announcements,
14
+
sol call support diagnose.
10
15
---
11
16
12
17
# sol support
13
18
14
-
CLI for filing support tickets, searching the knowledge base, and submitting feedback to sol pbc.
19
+
File tickets, search the knowledge base, and submit feedback. Invoke via Bash: `sol call support <command> [flags]`.
15
20
16
21
## Before You Start
17
22
18
-
1. **Read the TOS first.** A local copy is cached at the portal storage directory after first registration. Check `apps/support/portal/tos.txt` in the journal's app storage. If it doesn't exist, run `sol call support register` to fetch and cache it.
23
+
1. **Read the TOS first.** The TOS is cached locally at `<journal_root>/apps/support/portal/tos.txt` after first registration (the actual path resolves via the journal's app storage). If it doesn't exist yet, run `sol call support register` to fetch and cache it.
19
24
20
25
2. **Always search the KB before filing a ticket.** Run `sol call support search "your question"` first. Many common issues are already documented. Only file a ticket if the KB doesn't answer the question.
21
26
···
178
183
# Quick system health check
179
184
sol call support diagnose
180
185
```
186
+
187
+
## Gotchas
188
+
189
+
- **KB-first is automatic on `create`.** The `create` command always searches the KB and shows matches for owner review before filing. Pass `--skip-kb` only if the issue is clearly unique — it's there for edge cases, not as a speed-up.
190
+
- **`--product` defaults to solstone.** Support handles other sol pbc products too. Confirm with the owner before filing a non-solstone ticket; don't assume the default.
191
+
- **Diagnostics can leak configuration.** The auto-collector strips secrets, but the full diagnostic payload is shown at the consent gate — review before approving.
192
+
- **Attachments follow ticket creation.** Create first, then `attach` — attachments can't be included in the initial create call.