菜单
Use Moraine realtime session data to inspect active agent work across harnesses when the user asks what is happening now or what another agent is doing.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Run isolated Moraine dev sandbox validation. Use when testing ingest, MCP, monitor, ClickHouse schema, source formats, stack behavior, or any change where QA must not touch the developer's host ~/.moraine install; use before reporting completion for stack-facing changes.
Help prepare and, only with explicit user approval, file a sanitized Moraine bug report for reproducible defects in Moraine itself.
Use Moraine realtime session data to inspect active agent work across harnesses when the user asks what is happening now or what another agent is doing.
Use Moraine MCP tools to recover prior agent-session context when the user refers to earlier work, decisions, failures, branches, files, or other agents.
Cut and publish Moraine releases from a version argument such as /release X.Y.Z or a request to use $moraine-dev:release. Use when Codex is asked to run Moraine's release process, bump release-managed versions, create and merge the release PR, push the vX.Y.Z tag, update GitHub release notes for a general audience, verify the release-moraine workflow, and confirm the PyPI moraine-cli package. Start or continue a Codex goal for the release.
Use Moraine MCP tools to recover prior agent-session context when the user refers to earlier work, decisions, failures, branches, files, or other agents.
| name | realtime-peek |
| description | Use Moraine realtime session data to inspect active agent work across harnesses when the user asks what is happening now or what another agent is doing. |
Use this skill when the user asks about current or very recent agent activity, including other harnesses, sibling agents, subagents, or your own active session.
list_sessions for that window, sorted newest first.open.file_attention and then open the returned event, turn, or session handles.Summarize active work by source or harness, session title or ID, branch or working directory when visible, last update time, visible tool or terminal activity, and the current apparent state. Keep the summary compact and separate observed facts from inference.
If a record is still active, say that it is a live view and may change after the query. If the latest turn is incomplete, avoid treating it as a final decision.
Do not replay sensitive terminal or tool output into the current chat. Summarize what happened, redact secret-looking values such as tokens, keys, cookies, and credentials, and avoid quoting private data unless it is necessary for the user's requested debugging task.
Use search_sessions with keyword queries when the recent session list is too broad or when the user gives a content clue such as an issue number, command, error, file path, or branch name. After finding a candidate, narrow with within_id rather than pulling whole sessions into context.