CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

verify-remote-agent-execution

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.

Quality

95%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Quality

Content

100%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

An exemplary verification skill body: lean, entirely operational, with an exact run command, explicit expected outcomes, a failure-to-root-cause mapping, clearly bounded scope, and a documented recovery path. There is no padding, no assumed-knowledge explanation, and the pinned versions and commit are justified reproducibility anchors.

DimensionReasoningScore

Conciseness

Every sentence is operational and repo-specific: harm statement, tooling with pinned TLC version and sha256, prerequisites (Java on PATH, pnpm install), expected outcomes, failure-to-bug mapping, and scope exclusions. No explanation of concepts Claude already knows and no padding — matches anchor 5's "every token earns its place". The pinned commit and jar hash are reproducibility pins, not date-conditioned guidance, so the time-sensitivity penalty does not apply.

5 / 5

Actionability

Fully executable: exact command ("node .agents/skills/verify-remote-agent-execution/check.mjs"), working directory and prerequisite ("From the repository root, after pnpm install"), concrete expected results ("must return aborted"... "readable as aborted with no completed answer text"), and a diagnostic table mapping each named failure to the specific function at fault. Copy-paste ready with common cases covered — anchor 5.

5 / 5

Workflow Clarity

The sequence is unambiguous: check triggers (five named functions in one file), run the single command, verify the two expected outcomes, and on failure consult the per-message diagnosis; "Read every TLC result with /statechart" closes the loop. As a single-purpose verification skill whose one action is explicit and whose failure section is a built-in feedback loop, it satisfies both anchor 5 and the simple-skill exception; the destructive/batch cap does not apply since the skill is itself a validation step.

5 / 5

Progressive Disclosure

At ~45 lines with well-organized sections (When this applies, Run, What a failure means, Scope, recovery pointer) and no need for external reference files, this matches the under-50-line simple-skill case where organized sections alone warrant a 5. Bundle files (check.mjs, view.mjs, the TLA+ spec) are referenced by name exactly where they are used, one level deep.

5 / 5

Total

20

/

20

Passed

Description

87%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A strong description: it states the invariant being verified in concrete terms and gives an explicit, precise use-when clause keyed to exact function names. The only improvement room is adding natural-language trigger synonyms alongside the function names and covering all five trigger functions.

Suggestions

Add natural-language trigger phrases (e.g. "remote agent execution state", "stop/cancel semantics", "stored reply") alongside the exact function names so the description also matches users who describe the change informally.

Include resolveSettledExecutionStatus in the use-when list, since the body's "When this applies" section treats it as a trigger function.

DimensionReasoningScore

Specificity

"Check Remote Agent native execution" is a semi-generic action, but the concrete verified behaviors ("A stop is not stored as a reply, and a stored reply is not rewritten as a stop") plus four named functions make the capabilities specific with only minor gaps (tooling like TLA+/TLC verification is not mentioned). Clearly above anchor 3's generic 1-2 actions, but not the comprehensive multi-action coverage of anchor 5.

4 / 5

Completeness

Explicitly answers both: what ("Check Remote Agent native execution. A stop is not stored as a reply, and a stored reply is not rewritten as a stop") and when ("Use when changing [four function names]") with concrete trigger phrases. Anchor 5 fits; the when-clause is maximally specific, so anchor 4's "could be more explicit" does not apply.

5 / 5

Trigger Term Quality

"Use when changing initializeRemoteAgentExecutionState, markRemoteAgentExecutionProgress, requestRemoteAgentExecutionCancellation, or completeRemoteAgentExecutionState" gives exact, natural triggers a developer would name, but no natural-language synonyms or variations (e.g. "remote agent execution state", "cancellation", "stop/reply semantics") and omits resolveSettledExecutionStatus, which the body lists as a trigger. Good coverage, a few terms missing — anchor 4, not anchor 5's comprehensive synonym coverage.

4 / 5

Distinctiveness Conflict Risk

A clear niche — verification of specific Remote Agent execution-state functions, triggered by exact function names — with essentially zero overlap risk against other skills. Matches anchor 5's "clear niche with distinct triggers; minimal conflict risk".

5 / 5

Total

18

/

20

Passed

Validation

100%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

amplifthq/opentag

Path

.agents/skills/verify-remote-agent-execution/SKILL.md

Reviewed

Table of Contents

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.