personal memory agent
0
fork

Configure Feed

Select the types of activity you want to include in your feed.

refactor(activities): rename talent skill doc and update to new CLI

+154 -130
+154
apps/activities/talent/activities/SKILL.md
··· 1 + --- 2 + name: activities 3 + description: > 4 + Manage completed activity records organized by facet and day. List, inspect, 5 + create, update, mute, and unmute activity spans, including synthetic records 6 + created from the CLI. Use when the owner mentions activities, work sessions, 7 + completed spans, muted activity records, or wants to review or edit an 8 + activity entry. 9 + TRIGGER: activity, activities, work session, completed span, mute activity, 10 + unmute activity, activity record. 11 + --- 12 + 13 + # Activities CLI Skill 14 + 15 + Use these commands to manage completed activity records from the terminal. 16 + 17 + **Environment defaults**: When `SOL_DAY` is set, commands that take `DAY` use it automatically. Same for `SOL_FACET` where `FACET` is accepted. 18 + 19 + Common pattern: 20 + 21 + ```bash 22 + sol call activities <command> [args...] 23 + ``` 24 + 25 + ## list 26 + 27 + ```bash 28 + sol call activities list [-d DAY | --from DAY --to DAY] [-f FACET] [-a ACTIVITY] [--entity ENTITY] [--all] [--json] 29 + ``` 30 + 31 + List activity records for one day or an inclusive day range. 32 + 33 + - `-d, --day`: single day in `YYYYMMDD` (default: `SOL_DAY` env). 34 + - `--from`, `--to`: inclusive day range in `YYYYMMDD`. 35 + - `-f, --facet`: optional facet filter. Omit to include all facets. 36 + - `-a, --activity`: optional activity-type filter. 37 + - `--entity`: optional active-entity filter. 38 + - `--all`: include hidden activity records. 39 + - `--json`: emit raw JSON instead of formatted text. 40 + 41 + Examples: 42 + 43 + ```bash 44 + sol call activities list -d 20260115 -f work 45 + sol call activities list --from 20260101 --to 20260107 -f work --activity coding 46 + sol call activities list -d 20260115 --entity "Alicia Chen" --json 47 + ``` 48 + 49 + ## get 50 + 51 + ```bash 52 + sol call activities get SPAN_ID [-f FACET] [-d DAY] [--json] 53 + ``` 54 + 55 + Fetch one activity record by id. 56 + 57 + - `SPAN_ID`: activity record id. 58 + - `-f, --facet`: facet name (default: `SOL_FACET` env). 59 + - `-d, --day`: day in `YYYYMMDD` (default: `SOL_DAY` env). 60 + - `--json`: emit the raw record. 61 + 62 + Example: 63 + 64 + ```bash 65 + sol call activities get coding_090000_300 -f work -d 20260115 66 + ``` 67 + 68 + ## create 69 + 70 + ```bash 71 + sol call activities create [-f FACET] [-d DAY] [--since-segment SEGMENT] [--source user|cogitate] [--json] 72 + ``` 73 + 74 + Create a new activity record from a JSON object on stdin. 75 + 76 + - `-f, --facet`: facet name (default: `SOL_FACET` env). 77 + - `-d, --day`: day in `YYYYMMDD` (default: `SOL_DAY` env). 78 + - `--since-segment`: optional segment key to anchor a real activity span. 79 + - `--source`: record source label (`user` by default). 80 + - `--json`: emit the created record. 81 + 82 + Stdin JSON requirements: 83 + 84 + - Required: `title`, `activity` 85 + - Optional: `description`, `details` 86 + 87 + Examples: 88 + 89 + ```bash 90 + echo '{"title":"Deep work","activity":"coding"}' | sol call activities create -f work 91 + echo '{"title":"Session review","activity":"coding","details":"Retrospective notes"}' | sol call activities create -f work --since-segment 090000_300 --source cogitate --json 92 + ``` 93 + 94 + ## update 95 + 96 + ```bash 97 + sol call activities update SPAN_ID [-f FACET] [-d DAY] [--note TEXT] [--json] 98 + ``` 99 + 100 + Update one activity record from a JSON patch on stdin. 101 + 102 + - `SPAN_ID`: activity record id. 103 + - `-f, --facet`: facet name (default: `SOL_FACET` env). 104 + - `-d, --day`: day in `YYYYMMDD` (default: `SOL_DAY` env). 105 + - `--note`: optional edit note stored in the record history. 106 + - `--json`: emit the updated record. 107 + 108 + Stdin JSON may include only `title`, `description`, and `details`. 109 + 110 + Example: 111 + 112 + ```bash 113 + echo '{"title":"Focused coding","details":"Closed out CLI edge cases"}' | sol call activities update coding_090000_300 -f work --note "tightened summary" 114 + ``` 115 + 116 + ## mute 117 + 118 + ```bash 119 + sol call activities mute SPAN_ID [-f FACET] [-d DAY] [--reason TEXT] [--json] 120 + ``` 121 + 122 + Hide an activity record without deleting it. 123 + 124 + - `SPAN_ID`: activity record id. 125 + - `-f, --facet`: facet name (default: `SOL_FACET` env). 126 + - `-d, --day`: day in `YYYYMMDD` (default: `SOL_DAY` env). 127 + - `--reason`: optional note stored in the edit history. 128 + - `--json`: emit the updated record. 129 + 130 + Example: 131 + 132 + ```bash 133 + sol call activities mute coding_090000_300 -f work --reason "synthetic duplicate" 134 + ``` 135 + 136 + ## unmute 137 + 138 + ```bash 139 + sol call activities unmute SPAN_ID [-f FACET] [-d DAY] [--reason TEXT] [--json] 140 + ``` 141 + 142 + Restore a muted activity record. 143 + 144 + - `SPAN_ID`: activity record id. 145 + - `-f, --facet`: facet name (default: `SOL_FACET` env). 146 + - `-d, --day`: day in `YYYYMMDD` (default: `SOL_DAY` env). 147 + - `--reason`: optional note stored in the edit history. 148 + - `--json`: emit the updated record. 149 + 150 + Example: 151 + 152 + ```bash 153 + sol call activities unmute coding_090000_300 -f work --reason "keep owner-authored record" 154 + ```
-130
apps/activities/talent/calendar/SKILL.md
··· 1 - --- 2 - name: calendar 3 - description: > 4 - Manage calendar events organized by facet and day. List, create, update, 5 - cancel, and move events including scheduling with participants and times. 6 - Use when the owner mentions calendar events, scheduling, appointments, 7 - meetings, or wants to create, reschedule, or cancel events. 8 - TRIGGER: calendar, schedule, appointment, meeting, event, reschedule. 9 - --- 10 - 11 - # Calendar CLI Skill 12 - 13 - Use these commands to manage calendar events from the terminal. 14 - 15 - **Environment defaults**: When `SOL_DAY` is set, commands that take a DAY argument will use it automatically. Same for `SOL_FACET` where FACET is required. 16 - 17 - Common pattern: 18 - 19 - ```bash 20 - sol call calendar <command> [args...] 21 - ``` 22 - 23 - ## list 24 - 25 - ```bash 26 - sol call calendar list [DAY] --facet FACET 27 - ``` 28 - 29 - List events for a day. 30 - 31 - - `DAY`: day in `YYYYMMDD` (default: `SOL_DAY` env). 32 - - `--facet`: facet name (default: `SOL_FACET` env). 33 - 34 - Example: 35 - 36 - ```bash 37 - sol call calendar list 20260115 --facet work 38 - ``` 39 - 40 - ## create 41 - 42 - ```bash 43 - sol call calendar create TITLE --start HH:MM --day DAY --facet FACET [--end HH:MM] [--summary TEXT] [--participants NAMES] 44 - ``` 45 - 46 - Create a calendar event. 47 - 48 - - `TITLE`: event title (positional argument). 49 - - `--start`: start time in `HH:MM` (required). 50 - - `--day`: day in `YYYYMMDD` (default: `SOL_DAY` env). 51 - - `--facet`: facet name (default: `SOL_FACET` env). 52 - - `--end`: optional end time in `HH:MM`. 53 - - `--summary`: optional event description. 54 - - `--participants`: optional comma-separated participant names. 55 - 56 - Example: 57 - 58 - ```bash 59 - sol call calendar create "Team standup" --start 09:00 --end 09:30 --day 20260115 --facet work --participants "Alicia, Ben" 60 - ``` 61 - 62 - ## update 63 - 64 - ```bash 65 - sol call calendar update LINE --day DAY --facet FACET [--title TEXT] [--start HH:MM] [--end HH:MM] [--summary TEXT] [--participants NAMES] 66 - ``` 67 - 68 - Update an existing calendar event. 69 - 70 - - `LINE`: 1-based line number from `list` output (positional argument). 71 - - `--day`: day in `YYYYMMDD` (default: `SOL_DAY` env). 72 - - `--facet`: facet name (default: `SOL_FACET` env). 73 - - `--title`: new event title. 74 - - `--start`: new start time in `HH:MM`. 75 - - `--end`: new end time in `HH:MM`. 76 - - `--summary`: new event description. 77 - - `--participants`: new comma-separated participant names. 78 - 79 - Example: 80 - 81 - ```bash 82 - sol call calendar update 2 --day 20260115 --facet work --start 10:00 --end 10:30 83 - ``` 84 - 85 - ## cancel 86 - 87 - ```bash 88 - sol call calendar cancel LINE --day DAY --facet FACET 89 - ``` 90 - 91 - Cancel a calendar event. 92 - 93 - - `LINE`: 1-based line number from `list` output (positional argument). 94 - - `--day`: day in `YYYYMMDD` (default: `SOL_DAY` env). 95 - - `--facet`: facet name (default: `SOL_FACET` env). 96 - 97 - Behavior notes: 98 - 99 - - Cancelled events remain visible in listings to preserve line numbering. 100 - 101 - Example: 102 - 103 - ```bash 104 - sol call calendar cancel 3 --day 20260115 --facet work 105 - ``` 106 - 107 - ## move 108 - 109 - ```bash 110 - sol call calendar move LINE --day YYYYMMDD --from SOURCE --to DEST [--consent] 111 - ``` 112 - 113 - Move a non-cancelled calendar event to another facet. 114 - 115 - - `LINE`: 1-based line number from `list` output (positional argument). 116 - - `--day`: day in `YYYYMMDD` (required). 117 - - `--from`: source facet name. 118 - - `--to`: destination facet name. 119 - - `--consent`: required when called by a proactive agent. Must have explicit owner approval before calling with this flag. 120 - 121 - Behavior notes: 122 - 123 - - Only non-cancelled events can be moved. 124 - - The `--consent` flag signals that the owner has explicitly approved this action. Proactive agents must obtain owner approval before including it. 125 - 126 - Example: 127 - 128 - ```bash 129 - sol call calendar move 1 --day 20260115 --from personal --to work --consent 130 - ```