メニュー
Handle the one-time first-run event to set up onboarding tickets and introduce yourself to the user. You **MUST** use this skill (and *carefully follow the process in this doc*) whenever you receive a message from the "mind/onboarding" source!
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Submit a bug report to libraries within the `mngr` project (eg, `mngr`, its plugins, `minds`, etc). Use to report bugs you encounter while running that seem to be issues with the `mngr` code itself, rather than with your own code or configuration.
Run commands to explore the current state of mngr and any relevant running agents. Use this skill when you need to debug issues with mngr tasks, or understand what tasks are currently running and their states.
Handle events from the mngr/agent_states source about sub-agent state transitions (finished, waiting, done, etc). You **MUST** use this skill (and *carefully follow the process in this doc*) whenever you receive a message from the "mngr/agent_states" source!
Clean up old agents, their output directories, and other historical data. Use during nightly cleanup or when the system has accumulated stale data.
Handle unexpected situations where the Minds system does not appear to be working as expected. Use when you encounter behavior that seems to contradict what your docs and prompts and skills say should happen, or when something seems broken and you are unsure how to proceed.
Create a sub-agent to perform a task. Use when you need to delegate work to another agent, for example, a working agent (for actually accomplishing some task) or a verifying agent (for deciding what to do about the output of a working agent).
| name | handle-mind-onboarding |
| description | Handle the one-time first-run event to set up onboarding tickets and introduce yourself to the user. You **MUST** use this skill (and *carefully follow the process in this doc*) whenever you receive a message from the "mind/onboarding" source! |
The mind/onboarding event fires exactly once -- the first time this mind starts.
Use it to bootstrap the onboarding process.
Read the onboarding checklist: Read thinking/onboarding.md, which contains a prioritized list of onboarding items grouped by when they should happen (first session, first day, first week, first month).
Create tickets for each unchecked item: For each unchecked (- [ ]) item in the checklist, create a ticket using create-ticket:
tk create "<item title>" \
--description "<item description from the checklist>" \
--tags onboarding \
--priority <priority based on timing group> \
--type task
Use priority levels that reflect the timing groups:
0123Do this all as one big bash command! Otherwise it takes you a while, since there are many entries.
thinking/onboarding.md as soon as you've created its ticket (change - [ ] to - [x]).
The checklist tracks "ticket created", not "task completed" -- ticket closure is tracked separately by tk.Do this with a single sed command that checks off all the items at once. For example:
Handle the most urgent item yourself: The "Find a way to provide value immediately" item should be done immediately -- don't delegate it.
Use send-message-to-user to send any necessary messages and questions.
Continue onboarding over time: The other items will be handled over the first hours, days, and weeks of usage. Don't try to do everything at once -- let the user get used to you gradually and avoid overwhelming them.
Continue working through the other tickets tagged "onboarding" over time through the normal ticket workflow.