菜单
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.
默认使用会先检查来源的 Prompt；你也可以切换为直接命令，或下载本地副本。
决定是否安装前，请先阅读 SKILL.md，以及 SkillsMP 当前展示的配套文件。
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
直接命令不会经过审查 Prompt；运行前请先检查来源。
npx skills add https://github.com/eric-tramel/moraine --skill realtime-peek命令会保持在同一行。复制前请横向滚动并检查完整内容。
想先保存到本地？可下载 SkillsMP 当前能够提供的文件。
Search and inspect prior agent sessions, observe active agent work, or prepare a sanitized Moraine bug report through the local Moraine MCP server.
Cut and publish Moraine releases from a version argument such as /release X.Y.Z in Kiro or a request to use $moraine-dev:release in Codex. Use when Codex or Kiro 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. In Codex, start or continue a durable goal for the release.
Coordinate a delegated full multi-persona code review for a Moraine PR or local change. Use when asked to review a PR, run review agents, get code review feedback, or iterate on review feedback using all CodeReview personas: elegance, idiom, correctness, completeness, security, YAGNI, and scope. Invoking this skill is an explicit request to launch reviewer subagents.
基于 SOC 职业分类
正在显示 SKILL.md
| 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 first. If the compact
summary is insufficient, request a bounded page with id plus limit and
continue with { "cursor": next_cursor } only as far as needed. Open an
individual event ID when exact content is required.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.