agentleFS
Sign inStart free
amplifthqamplifthq/openmeld/.agents/skills/verify-remote-agent-execution/SKILL.md

verify-remote-agent-execution

Skill1.4k starsChanged 5 days agoMITView on GitHub

Check Remote Agent native execution. A stop is not stored as a reply, and a stored reply is not rewritten as a stop. Use when changing initializeRemoteAgentExecutionState, markRemoteAgentExecutionProgress, requestRemoteAgentExecutionCancellation, or completeRemoteAgentExecutionState.

1 other project uses a version of this.

Trending

More talk lately.about the whole repository

Dec 2025: 0 mentionsJan 2026: 0 mentionsFeb 2026: 0 mentionsMar 2026: 0 mentionsApr 2026: 0 mentionsMay 2026: 0 mentionsJun 2026: 0 mentionsJul 2026: 0 mentionsAug 2026: 0 mentionsSep 2026: 0 mentionsOct 2026: 24 mentionsNov 2026: 7 mentions
Dec 2025Jun 2026Nov 2026
Mentions a month of the amplifthq/openmeld repository that our weekly crawl found. There is no adoption data for this file yet.

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

3 rules. About 0 are common, 0 are distinctive, and 3 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈0

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 3

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Run it when a change touches any of these in services/remote-agent/agent-core/execution-state.ts:

    line 14
  2. Very specific:

    Read every TLC result with /statechart.

    line 34
  3. Very specific:

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

    line 49

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 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 Remote Agent execution

A stop that wins before a reply is stored never becomes a completed reply, and a reply that is already stored stays a reply. Harm: the Space shows a successful answer after the member stopped the hosted agent, or a stop erases an answer that already landed.

The steps are compare-and-set transitions on one submission, so the spec is TLA+ and the checker is TLC 1.7.4 (jar sha256 936a262061c914694dfd669a543be24573c45d5aa0ff20a8b96b23d01e050e88). The code check calls the real functions with the in-memory storage from services/remote-agent/tests/storage.ts and rereads the terminal outcome using resolveRemoteAgentTerminalExecutionOutcome. 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 in services/remote-agent/agent-core/execution-state.ts:

  • initializeRemoteAgentExecutionState
  • markRemoteAgentExecutionProgress
  • requestRemoteAgentExecutionCancellation
  • completeRemoteAgentExecutionState
  • resolveSettledExecutionStatus

Confirmed against commit 965d9eb3219fa2c35789f9ab9a2206ab8699de9b. Move that commit forward only after you have confirmed that RemoteAgentExecution.tla and check.test.ts still describe those functions.

Run

From the repository root, after pnpm install:

node .agents/skills/verify-remote-agent-execution/check.mjs

The stop-then-complete replay must return aborted. The persisted outcome must also be readable as aborted with no completed answer text. A failure during readback catches an inconsistent stored record even if completion returned the expected status.

Read every TLC result with /statechart. The user-facing labels are in view.mjs next to the spec.

What a failure means

  • settles a stop as stopped expected aborted and got completed: resolveSettledExecutionStatus no longer turns cancellation_requested into aborted. That is the bug the rule exists to catch.
  • keeps a stored reply failed: stop after completed changed the row or reported it as stoppable.
  • does not start after a stop that arrived first failed: initialization ignored the admission stop intent.
  • TLC failed while the code check passed: the model allows a step the functions do not, or the opposite. One spec step is one successful compare-and-set. Do not drop AStopIsNotAReplyOrMoreWork to make TLC pass.

Scope

One submission. repairRemoteAgentCompletedExecutionWithoutAnswer is not in the model: a completed row with no stored answer can still become failed. The chart hides the idle end step and a progress tick that stays on Working.

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.

Check your setup, free