CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

aris-run-experiment

Deploy and run ML experiments on local, remote, Vast.ai, or Modal serverless GPU. Use when user says "run experiment", "deploy to server", "跑实验", or needs to launch training jobs.

Quality

80%

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

Fix and improve this skill with Tessl

tessl review fix ./skills/aris-run-experiment/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

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

The body is highly actionable with concrete, executable commands for every environment and a well-sequenced workflow that includes a mandatory resource guard and launch verification. Its weaknesses are redundancy (the GPU check is repeated three times), the absence of failure-recovery guidance after launch verification, and a monolithic single-file structure where the W&B guide and CLAUDE.md example could be split into reference files.

Suggestions

Consolidate the GPU-availability check: state the nvidia-smi/MPS commands once (e.g. in Step 0) and have Step 2 reference it instead of repeating them, removing the duplicated free-GPU criteria.

Add an error-recovery branch to Step 5: instruct what to do when screen -ls shows no session or the process exited early (e.g. tail the tee'd log, report the error, do not retry blindly).

Move the W&B integration code block and the CLAUDE.md configuration example into a reference file (e.g. references/wandb.md, references/config-examples.md) and link to them from the main body to reduce inline bulk.

DimensionReasoningScore

Conciseness

The body is mostly command-driven and tight, but the nvidia-smi GPU-availability check appears nearly verbatim three times (Step 0 inline check, Step 2 pre-flight, and the Local deploy section), and passages like "Benefits: version-tracked, multi-server sync with one push, no rsync include/exclude rules needed" explain things Claude already knows. This fits the 'mostly efficient but could be tightened' anchor rather than the minor-trim level of 4.

3 / 5

Actionability

Nearly every step ships copy-paste-ready commands with explicit placeholders: the rsync include/exclude filters, the ssh + screen + conda launch command, "vastai destroy instance <INSTANCE_ID>", "modal run modal_launcher.py", and "vastai ssh-url <INSTANCE_ID>". Common cases (local, remote, Vast.ai, Modal) are each covered with concrete examples, matching the fully-executable top anchor.

5 / 5

Workflow Clarity

Steps 0-7 are clearly sequenced with real checkpoints: the mandatory Step 0 guard ("STOP IMMEDIATELY... Do NOT fabricate"), Step 5 "Verify Launch" via screen -ls / modal app list, and Step 7's download-results-before-destroy ordering for the destructive vast.ai teardown. It falls short of 5 because there is no error-recovery loop after verification — no guidance for what to do if the screen session is absent or the launch fails.

4 / 5

Progressive Disclosure

The skill is a single ~300-line file with no bundle files (no references/, scripts/, or assets/ exist), and substantial content that could live in separate reference files is inlined — the full W&B integration code block (Step 3.5), the large CLAUDE.md example block, and the Modal/Vast.ai setup notes. Section structure is good, but content that should be split out is inline, which is the score-3 anchor rather than the well-split structure of 4.

3 / 5

Total

15

/

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 explicitly covers both what the skill does and when to use it, with natural trigger phrases including a Chinese synonym. Minor weaknesses are the limited action verb variety and the somewhat generic "deploy to server" trigger that could overlap with non-ML deployment skills.

DimensionReasoningScore

Specificity

"Deploy and run ML experiments on local, remote, Vast.ai, or Modal serverless GPU" names the domain and concrete actions (deploy, run) across four enumerated platforms, going beyond the 1-2 actions of a score-3 anchor. It falls short of 5 because only two action verbs are given, without the multi-action breadth of "extract, fill, merge, convert".

4 / 5

Completeness

Both questions are answered explicitly: the "what" is "Deploy and run ML experiments on local, remote, Vast.ai, or Modal serverless GPU" and the "when" is "Use when user says 'run experiment', 'deploy to server', '跑实验', or needs to launch training jobs" with concrete trigger phrases. This matches the top anchor exactly; score 4 would require the 'when' to be less explicit than it is.

5 / 5

Trigger Term Quality

Natural phrases users would actually say are present: "run experiment", "deploy to server", "跑实验", "needs to launch training jobs", including a bilingual synonym. A few common variations (e.g. "train a model", "rent a GPU") are missing, keeping it below the comprehensive-coverage anchor at 5.

4 / 5

Distinctiveness Conflict Risk

The ML-experiment-deployment niche is clear and the GPU-platform triggers are distinct, but "deploy to server" is a fairly generic phrase that could overlap with web- or app-deployment skills, giving minor conflict risk. Not 3, since the overall framing (ML experiments, GPU backends) keeps it well distinguishable; not 5 due to that generic trigger phrase.

4 / 5

Total

17

/

20

Passed

Validation

87%

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

Validation — 14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

allowed_tools_field

'allowed-tools' contains unusual tool name(s)

Warning

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

14

/

16

Passed

Repository

OpenLAIR/dr-claw

Path

skills/aris-run-experiment/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.