メニュー
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コマンドは1行のまま表示されます。コピー前に横へスクロールして全体を確認してください。
ローカルで確認しますか？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.
mcp_moraine_list_sessions for that window, sorted newest first.mcp_moraine_open.mcp_moraine_file_attention and then open the returned event, turn, or session handles.If the server was registered with a different name, use the corresponding Moraine-prefixed MCP tools available in the current session.
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 mcp_moraine_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.