CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

remote-compute-ssh

Evaluate and use Remote Compute before choosing where to run GPU, high-memory, parallel, batch, model-inference, bioinformatics, or other long-running scientific work; supports short remote commands and asynchronous jobs with automatic harvest and analysis.

Quality

83%

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

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

Highly actionable and workflow-clear content for a complex multi-mode compute API, with strong error recovery and validation guidance. Its weaknesses are redundancy in the job-snapshot semantics and a monolithic inline structure that buries what should be split into one-level-deep reference files.

Suggestions

Move the per-target execution-mode details (Kubernetes, Hugging Face, Ray, Modal Sandboxes) out of SKILL.md into separate files under references/ (e.g. references/external-targets.md, references/modal-sandboxes.md), keeping only the mode-selection guidance inline.

Extract the two inline 'API reference' sections into references/api-reference.md, leaving a concise method summary with one or two key examples in SKILL.md.

Deduplicate the follow_up_delivery explanation in the 'Read a saved Job snapshot' section — state the suppressed/committed semantics once instead of twice in consecutive paragraphs.

DimensionReasoningScore

Conciseness

The body is dense and API-specific rather than teaching known concepts, but the follow_up_delivery 'suppressed'/'committed' semantics are explained twice within the same section ("A final .result() read returns suppressed..." then again "A final .result() snapshot reports follow_up_delivery: 'suppressed'..."), and several boundary passages (e.g. the details write-result paragraph) could be tightened.

3 / 5

Actionability

Copy-paste-ready JavaScript covers every common case — listHosts filtering, create, callCommand with options and error codes, submitJob with inputs/outputs/harvest, status/result/cancel snapshots, chaining via left_on_remote, and batch submission — each annotated with result shapes and option semantics.

5 / 5

Workflow Clarity

The async lifecycle is sequenced up front (submit → save job_id → non-blocking snapshots → harvest → analysis turn → publish artifacts), first-contact and analysis-turn workflows are numbered, and explicit validation checkpoints and feedback loops exist (read-again-after-write for the knowledge doc, details_conflict re-read-and-merge, validate environment activation then retry).

5 / 5

Progressive Disclosure

The single reference (references/slurm-troubleshooting.md) is real, clearly signaled at the point of need, and one level deep, but roughly 500 lines of inline API reference plus per-target details (Kubernetes, Hugging Face, Ray, Modal) that clearly belong in separate reference files are inlined in SKILL.md.

3 / 5

Total

16

/

20

Passed

Description

83%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 that clearly states both capability and use-when with concrete scientific-compute trigger terms. Its main gaps are the generic "use Remote Compute" verb and the absence of common synonyms (cluster, HPC, Slurm, SSH) that users would naturally say.

DimensionReasoningScore

Specificity

The description lists several concrete actions — "supports short remote commands and asynchronous jobs with automatic harvest and analysis" plus the evaluate-before-choosing framing — but "use Remote Compute" is generic and capabilities like host knowledge docs and Slurm submission are absent, leaving minor coverage gaps.

4 / 5

Completeness

It explicitly answers both what ("short remote commands and asynchronous jobs with automatic harvest and analysis") and when ("before choosing where to run GPU, high-memory, parallel, batch, model-inference, bioinformatics, or other long-running scientific work") with concrete trigger phrases.

5 / 5

Trigger Term Quality

Natural trigger terms are present ("GPU", "high-memory", "parallel", "batch", "model-inference", "bioinformatics", "long-running scientific work"), but common user phrasings like "cluster", "HPC", "Slurm", "SSH", or "server" are missing.

4 / 5

Distinctiveness Conflict Risk

The remote-scientific-compute niche with triggers like bioinformatics and GPU work is mostly distinct, but it never names SSH, cluster, or HPC, leaving minor overlap risk with generic remote-execution or SSH skills.

4 / 5

Total

17

/

20

Passed

Validation

93%

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

Validation — 15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

skill_md_line_count

SKILL.md is long (521 lines); consider splitting into references/ and linking

Warning

Total

15

/

16

Passed

Repository

aipoch/open-science

Path

resources/skills/remote-compute-ssh/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.