- name
SKILL.md
スキルファイルは公開元のリポジトリに置かれたままです。
コピーしたコマンドをターミナルに貼り付けてください。この SKILL.md がそのエージェントにインストールされます。
npx skills add amplifthq/openmeld --skill verify-service-connection -a cursor -yコピーしたコマンドをターミナルに貼り付けてください。この SKILL.md がそのエージェントにインストールされます。
npx skills add amplifthq/openmeld --skill verify-service-connection -a claude-code -yコピーしたコマンドをターミナルに貼り付けてください。この SKILL.md がそのエージェントにインストールされます。
npx skills add amplifthq/openmeld --skill verify-service-connection -a codex -yコピーしたコマンドをターミナルに貼り付けてください。この SKILL.md がそのエージェントにインストールされます。
npx skills add amplifthq/openmeld --skill verify-service-connection -a grok -yコピーしたメッセージを Grok Bot のチャットで送信してください。Bot がこの SKILL.md を GitHub から取得し、すべての Bot が共有するスキルに追加します。
Install this skill: https://github.com/amplifthq/openmeld/tree/HEAD/.agents/skills/verify-service-connection公開元より
Only the local Service's online state reports healthy. Connecting, starting, and authentication problems report degraded, and stopping reports idle. The loop model also checks that quitting prevents reconnection. Core owns the separate Wakeability projection.
This is an ordering question about one connection loop, so the spec is TLA+ and the checker is TLC 1.7.4 (jar sha256 936a262061c914694dfd669a543be24573c45d5aa0ff20a8b96b23d01e050e88). The code check calls toHealthProjection, classifyConnectionFailureReason, and createServiceConnectionStateTracker. Java 11 or newer must be on PATH. The check downloads the jar into ~/.cache/openmeld-tlc/ on first run.
Run it when a change touches any of these:
clients/openmeld-cli/src/local-service/state/service-connection-state.ts
createServiceConnectionStateTrackertoHealthProjectionclassifyConnectionFailureReasonclients/openmeld-cli/src/local-service/carrier/service-runner.ts
connecting, online, and the failure statesnoteAuthenticationRequiredStatenoteReconnectFailureStatemarkStoppingConfirmed against commit 965d9eb3219fa2c35789f9ab9a2206ab8699de9b. Move that commit forward only after you have confirmed that ServiceConnection.tla and check.mjs still describe those functions.
From the repository root:
node .agents/skills/verify-service-connection/check.mjs
Exit 0 means the health projection, the upgrade-rejection classification, and the loop model all hold. pnpm install is not required for this check.
Read every TLC result with /statechart. The user-facing labels are in view.mjs next to the spec.
toHealthProjection for all six service connection states. In particular, connecting must report degraded/suspect until the connection is online.a non-401 stream upgrade rejection is internal: classifyConnectionFailureReason treated a 500, or a message that merely contains "401" or "socket", as sign-in or network. That sends the user to the wrong recovery.NoReconnectAfterQuit failed: the model now has a path from stopping back to connecting. Check markStopping and the while (!stopRequested) loop before you weaken the rule.connectionState.set in the run loop, or the health read that forces stopping while draining.One service process. Backoff durations are not in the model. sign_in_unavailable is degraded reason auth_unavailable, not authentication_required. The chart hides "you quit" from connecting, sign-in, and the reconnecting states. You can still quit from those; the chart shows quit from Starting and Connected, and every other state can still try again or fail.
Use /maintain-formal-verification-skill to bring this check back in line.
Check the local OpenMeld Service connection loop. The computer is shown as connected only while the session is online, stopping is idle, and quitting does not reconnect. Use when changing the service
---name: verify-service-connectiondescription: Check the local OpenMeld Service connection loop. The computer is shown as connected only while the session is…---# .agents/skills/verify-service-connection/SKILL.md概要
Check the local OpenMeld Service connection loop. The computer is shown as connected only while the session is online, stopping is idle, and quitting does not reconnect. Use when changing the service run loop, toHealthProjection, or classifyConnectionFailureReason.
よくある質問
公開元から .agents/skills/verify-service-connection/SKILL.md をダウンロードするか、パスをコピーしてリポジトリを開いてください。PlugMCP はスキルを掲載するだけで、ファイルはホストしていません。
公開元は https://github.com/amplifthq/openmeld で管理しています。
Claude、Cursor、Codex、Grok Build は、公開元のリポジトリから追加した SKILL.md を読み込めます。Grok Bot は、チャットでスキルの GitHub フォルダーのリンクを送るとインストールします。