菜单
Use this skill when source changes must be proven in an installed, supervised, or operator-facing runtime before claiming smoke-green or watched-live-green. Trigger for Homebrew/launchd rollouts, stale-binary suspicion, installed-vs-source drift, or live watch validation after deploy.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Use this skill when reviewing, provisioning, or documenting MCP membrane tools for external clients such as Perplexity, Claude, or Codex. It keeps Muninn capture, LifeGraph tools, and raw graph/runtime tools separated.
Use this skill when authoring or revising an agent role lens before governed execution. It gathers the missing role definition inputs, explains the required payload shape, and prepares the payload for the role.create_or_update workflow.
Use at session start and closeout to retrieve and write durable Muninn continuity context.
Use when the user needs planning, decomposition, orchestration, or seam selection guidance.
Use when the user needs validation strategy, test selection, or confidence reporting.
Use this skill when an agent summarizes the operator's LifeGraph, answers "what is in my LifeGraph?", or turns LifeGraph records into planning context. It requires provenance-aware summaries that separate confirmed graph facts from seeded placeholders, inferred intent, and recommended next structure.
| name | runtime-rollout-watch |
| description | Use this skill when source changes must be proven in an installed, supervised, or operator-facing runtime before claiming smoke-green or watched-live-green. Trigger for Homebrew/launchd rollouts, stale-binary suspicion, installed-vs-source drift, or live watch validation after deploy. |
Scope: Philotic-specific, but generally applicable to installed runtimes.
Use this skill when the work crosses the boundary from "code is fixed" to "the live stack is actually running that fix."
This skill owns:
This skill does not own:
Use $runtime-debugger when the main problem is locating the failing live boundary. Use $verification-ladder when the main question is validation depth rather than rollout proof.
Report:
