likesjx

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.

Create, inspect, enable, disable, and remove scheduled cron jobs on the hotel. Use when the operator or an autonomous workflow needs recurring work at a fixed schedule.

Use this skill when a client should adopt the shared Muninn memory workflow for continuity across sessions. Trigger when setting up Muninn-backed recall/write-back habits, wiring a client to the shared helper, or standardizing memory behavior across multiple cognitive clients.

Use this skill to validate repo health before starting work. It checks that required files, tools, and services are present and functional. Run at session start or after major structural changes.

Use this skill when debugging live runtime behavior in a multi-process or distributed system, especially IPC framing, socket registration, supervised process startup, routing/materialization, liveness, or request/response mismatches. Trigger when the user asks to watch a live stack, debug runtime integration issues, inspect process/socket state, or compare test behavior against real execution. This skill is general and should not assume a Rust-only stack.

HIGH PRIORITY. Use this skill when changing architecture or workflow docs so domain, frontmatter, status truth, proposal links, and task links stay aligned automatically. Trigger for edits in docs/architecture/, docs/README.md, or docs/task.md when the work changes current truth, near-future seams, proposal status, or documentation structure.

HIGH PRIORITY. Use this skill to keep architecture and process proposals concise, current, and linked to active tasks. A proposal is not a static doc; it is an active plan. Trigger for disposition updates, task alignment, or removing stale certainty. Pair this with architecture-docs-maintainer when metadata, domains, or source-of-truth linkage also need upkeep.

HIGH PRIORITY. Use this skill at the START of EVERY session to retrieve project context and during the session to store decisions. It is the mandatory bootstrap mechanism for continuity and the engine for project optimization. Retrieve before meaningful work, write back important decisions, and use revealed gaps to improve repo-local protocols.

Use this skill when deciding how deeply to validate a change or when explaining confidence in a code change. Trigger for test planning, selecting the right validation rung, or classifying confidence as test-green, smoke-green, or watched-live-green. Do not use this skill for runtime root-cause investigation or slice close-out unless validation choice is the main task.

HIGH PRIORITY. Use this skill to finish every implementation slice. It mandates "green status clearing" (verified build/test/smokes), updates to docs/task.md, and explicit disposition updates for touched architecture proposals. No slice is complete until this operational close-out is recorded and committed.

One-paragraph description of when to use this skill, what triggers it, and what it should NOT be used for.

MeshOps distributed coordination mesh for OpenClaw gateways: ring-of-trust admission, CRDT-synced state, capability-contract routing, and governed delegation. Named for the ansible from Ender's Game, not the infrastructure tool.

Manage ansible skill lifecycle across gateways: source-of-truth edits, mirror sync, deployment verification, and drift cleanup.

Write PlantUML sequence-diagram blocks in architecture markdown, save .puml files, render local SVG assets, and inject markdown image links.