메뉴
Mark events as handled after processing them. You **MUST** use this skill (and *carefully follow the process in this doc*) after handling events, otherwise you will not be allowed to stop!
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 | mark-events-handled |
| description | Mark events as handled after processing them. You **MUST** use this skill (and *carefully follow the process in this doc*) after handling events, otherwise you will not be allowed to stop! |
After handling a group of events, you must mark each one as handled individually. But first, verify that you actually did the right thing for each event.
Before marking anything as handled, go through each event and confirm:
If you realize you missed something or took the wrong action for an event, go do the right thing first before marking it as handled. Don't just claim you handled it.
Call handle_event.sh once per event, providing metadata about how you handled it:
./skills/mark-events-handled/handle_event.sh <event_id> \
--summary "<short description of what you did>" \
--confidence <0.0-1.0> \
[--ticket <ticket-id>] \
[--message <message-id>]
<event_id> -- the event_id from the event you handled--summary -- a short description of how you handled the event (e.g., "Delegated fix-login-bug task to working agent", "Sent clarification question to user", "Ignored duplicate event")--confidence -- a float from 0.0 to 1.0 indicating how confident you are that you handled the event correctly. Use 0.9+ when you followed a clear skill and the action was straightforward. Use lower values when you had to improvise or are unsure.--ticket <id> -- if you created one or more tickets as a result of handling this event, pass each ticket ID. Can be specified multiple times.--message <id> -- if you were uncertain about how to handle the event and asked for clarification, pass the message ID(s) where you asked. Can be specified multiple times.# Straightforward: delegated a user request to a working agent
./skills/mark-events-handled/handle_event.sh evt-abc123 \
--summary "Delegated 'fix auth bug' to working agent my-mind-fix-auth" \
--confidence 0.95 \
--ticket tk-5c46
# Uncertain: asked the user for clarification
./skills/mark-events-handled/handle_event.sh evt-def456 \
--summary "User request was ambiguous, asked for clarification in daily conversation" \
--confidence 0.5 \
--message msg-789
# Simple: ignored a duplicate event
./skills/mark-events-handled/handle_event.sh evt-ghi789 \
--summary "Duplicate of evt-abc123, already handled" \
--confidence 1.0
If you're genuinely unsure, mark it as handled with a low confidence score and ask a question about it. It's better to move forward and revisit than to get stuck.