agentleFS
amplifthqamplifthq/openmeld/.agents/skills/verify-service-connection/SKILL.md

verify-service-connection

Skill1.4k starsChanged 5 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

Week of Sep 20: 0 new projectsWeek of Sep 27: 0 new projectsWeek of Oct 4: 0 new projectsWeek of Oct 11: 0 new projectsWeek of Oct 18: 0 new projectsWeek of Oct 25: 0 new projectsWeek of Nov 1: 0 new projectsWeek of Nov 8: 0 new projects
Sep 2026Oct 2026Nov 2026
New projects taking a version of this file each week, over the 8 weeks our latest run read: only 0 in all, so this is a hint, not a trend.

Most recently taken up by

Who's talking about amplifthq/openmeld

The biggest 5 of 31 mentions linking to the repository that our crawl found. Each line is their own headline.

See all 31

Talked about on GitHub (31 times).

On GitHub · 31

26 more on GitHub

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
  1. Distinctive:

    Only the local Service's online state reports healthy.

    line 8
  2. Distinctive:

    Run it when a change touches any of these:

    line 14
  3. Very specific:

    Read every TLC result with /statechart.

    line 38
  4. Very specific:

    Use /maintain-formal-verification-skill to bring this check back in line.

    line 53

≈ “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.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

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.ts
    • createServiceConnectionStateTracker
    • toHealthProjection
    • classifyConnectionFailureReason
  • clients/openmeld-cli/src/local-service/carrier/service-runner.ts
    • the run loop that sets connecting, online, and the failure states
    • noteAuthenticationRequiredState
    • noteReconnectFailureState
    • markStopping

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.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.

What a failure means

  • A health mismatch names the phase and the actual and expected values. The code check calls 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.
  • TLC cannot parse the spec: the model drifted. One step in the spec is one connectionState.set in the run loop, or the health read that forces stopping while 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.

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.