- 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이 GitHub에서 이 SKILL.md를 가져와 모든 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.
FAQ
게시자에게서 .agents/skills/verify-service-connection/SKILL.md를 다운로드하거나 경로를 복사해 저장소를 엽니다. PlugMCP는 스킬을 목록에 올릴 뿐 파일을 호스팅하지 않습니다.
게시자가 https://github.com/amplifthq/openmeld에서 관리합니다.
Claude, Cursor, Codex, Grok Build는 게시자의 저장소에서 추가한 SKILL.md를 읽을 수 있습니다. Grok Bot은 채팅에서 스킬의 GitHub 폴더 링크를 보내면 설치합니다.