메뉴
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.
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.