verify-service-connection
Skill1.4k starsChanged 6 days agoMITView on GitHub
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.
1 other project uses a version of this.
Adopted by
Steady: 0 new projects took it in the last 4 weeks, none the 4 weeks before.thin data
Most recently taken up by
- amplifthq/openmeldword for word, first seen Nov 15, 2026
Who's talking about amplifthq/opentag
- amplifthq/openmeld“docs: clarify credential handling for fork contributions”GitHub · Oct 14, 2026 · 1 reactions
- sudosubin/agents.nix“agent-skills.github.amplifthq.opentag: 0-unstable-2026-10-14 → 0.10.0”GitHub · Oct 15, 2026
- amplifthq/openmeld“chore: sync final OpenMeld main before repository cutover”GitHub · Oct 15, 2026
- amplifthq/openmeld“fix(ci): wait for asynchronous publishers before local takeover”GitHub · Oct 14, 2026
- ProSkillsMD/proskills“[Candidate] amplifthq/opentag/.agents/skills/openmeld-changelog - openmeld-changelog”GitHub · Oct 14, 2026
The biggest 5 of 15 mentions linking to the repository that our crawl found. Each line is their own headline.
See all 15
Talked about on GitHub (15 times).
On GitHub · 15
- Oct 14, 2026docs: clarify credential handling for fork contributions — amplifthq/openmeld1 reaction · 2 comments
- Oct 15, 2026agent-skills.github.amplifthq.opentag: 0-unstable-2026-10-14 → 0.10.0 — sudosubin/agents.nix0 reactions
- Oct 15, 2026chore: sync final OpenMeld main before repository cutover — amplifthq/openmeld0 reactions · 3 comments
- Oct 14, 2026fix(ci): wait for asynchronous publishers before local takeover — amplifthq/openmeld0 reactions · 5 comments
- Oct 14, 2026[Candidate] amplifthq/opentag/.agents/skills/openmeld-changelog - openmeld-changelog — ProSkillsMD/proskills0 reactions · 1 comment
10 more on GitHub
- Oct 14, 2026[Candidate] amplifthq/opentag/.agents/skills/fixing-flaky-tests - fixing-flaky-tests — ProSkillsMD/proskills0 reactions · 1 comment
- Oct 14, 2026[Candidate] amplifthq/opentag/.agents/skills/debugging-ci-failures - debugging-ci-failures — ProSkillsMD/proskills0 reactions · 1 comment
- Oct 14, 2026agent-skills.github.amplifthq.opentag: 0.10.0 → 0-unstable-2026-10-14 — sudosubin/agents.nix0 reactions
- Oct 3, 2026agent-skills.github.amplifthq.opentag: v0.10.0 → refs/tags/v0.10.0 — sudosubin/agents.nix0 reactions
- Sep 25, 2026agent-skills.github.amplifthq.opentag: init at 0.10.0 — sudosubin/agents.nix0 reactions
- Sep 10, 2026chore: pin verified OpenTag release 3a3136dc — amplifthq/opentag-railway0 reactions · 1 comment
- Sep 8, 2026fix: respect Actions allowlist for image publication — amplifthq/openmeld0 reactions · 1 comment
- Sep 8, 2026feat: define Railway template and verified image pinning — amplifthq/opentag-railway0 reactions · 3 comments
- Sep 7, 2026refactor: converge control plane around teammates and effects — amplifthq/openmeld0 reactions · 7 comments
- Aug 29, 2026[T0.3] 技术验证: OpenTag runner 源码走读 — bao-linfeng/AgentDock0 reactions · 2 comments
Other versions1 project uses a version of this.
Word for word · 1
- amplifthq/openmeld★ 1.4k100% same
Edited · 0
None found.
Wrote their own version · 0
None found.
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository16 other files it gives its agents.
- AGENTS.mdAGENTS.md
- .claude/CLAUDE.mdCLAUDE.md
- CLAUDE.mdCLAUDE.md
- debugging-ci-failuresSkill
- fixing-flaky-testsSkill
- openmeld-changelogSkill
- postgresql-planningSkill
- react-doctorSkill
- verify-remote-agent-executionSkill
- verify-runtime-coordinator-livenessSkill
- verify-wake-progressSkill
- writing-testsSkill
- docs-lifecycle-scanSkill
- openmeld-changelogSkill
- release-runbookSkill
- wake-traceSkill
The file
We split this skill into the rules it gives an agent
4 rules. About 0 are common, 2 are distinctive, and 2 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈2
Distinctive · estimate
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 8
Only the local Service's online state reports healthy.
- Distinctive: line 14
Run it when a change touches any of these:
- Very specific: line 38
Read every TLC result with /statechart.
- Very specific: line 53
Use /maintain-formal-verification-skill to bring this check back in line.
≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Verify the 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.
When this applies
Run it when a change touches any of these:
clients/openmeld-cli/src/local-service/state/service-connection-state.tscreateServiceConnectionStateTrackertoHealthProjectionclassifyConnectionFailureReason
clients/openmeld-cli/src/local-service/carrier/service-runner.ts- the run loop that sets
connecting,online, and the failure states noteAuthenticationRequiredStatenoteReconnectFailureStatemarkStopping
- the run loop that sets
Confirmed against commit 965d9eb3219fa2c35789f9ab9a2206ab8699de9b. Move that commit forward only after you have confirmed that ServiceConnection.tla and check.mjs still describe those functions.
Run
From the repository root:
node .agents/skills/verify-service-connection/check.mjsExit 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.
What a failure means
- A health mismatch names the phase and the actual and expected values. The code check calls
toHealthProjectionfor all six service connection states. In particular,connectingmust reportdegraded/suspectuntil the connection is online. a non-401 stream upgrade rejection is internal:classifyConnectionFailureReasontreated a 500, or a message that merely contains "401" or "socket", as sign-in or network. That sends the user to the wrong recovery.NoReconnectAfterQuitfailed: the model now has a path from stopping back to connecting. CheckmarkStoppingand thewhile (!stopRequested)loop before you weaken the rule.- TLC cannot parse the spec: the model drifted. One step in the spec is one
connectionState.setin the run loop, or the health read that forcesstoppingwhile draining.
Scope
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.
After a change that skipped this skill
Use /maintain-formal-verification-skill to bring this check back in line.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

