CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

lambda-labs-gpu-cloud

Reserved and on-demand GPU cloud instances for ML training and inference. Use when you need dedicated GPU instances with simple SSH access, persistent filesystems, or high-performance multi-node clusters for large-scale training.

Quality

73%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Medium

Suggest reviewing before use

Fix and improve this skill with Tessl

tessl review fix ./skills/infrastructure/lambda-labs/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

61%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 a dense, well-structured reference with mostly executable code across SSH, curl, the Python client, and Slurm, plus clear step sequences for setup, launch, and training workflows. It loses points for verbosity — generic PyTorch DDP boilerplate and basic verification commands Claude already knows, and launch/terminate demonstrated twice in both Python and curl — and for destructive terminate operations that lack any validation checkpoint, which caps workflow clarity at 3.

Suggestions

Add validation before destructive operations: before api.terminate_instance or the curl terminate call, require verifying the instance ID and confirming checkpoints/data are saved to a persistent filesystem — the current terminate workflows have no safeguards despite local SSD being ephemeral.

Cut content Claude already knows: the generic DDP training-loop boilerplate, 'nvidia-smi'/'nvcc --version' verification commands, and 'ip addr show' private-IP lookup pad the token budget without adding skill-specific value.

Deduplicate: pick one interface (Python client OR curl) for launch/list/terminate, and replace the inline Common issues table with a brief pointer to references/troubleshooting.md since it duplicates that file's coverage.

DimensionReasoningScore

Conciseness

The bulk is dense provider-specific fact (GPU pricing table, mount paths, regions) that earns its place, but there are several unnecessary spots: generic PyTorch DDP boilerplate ('dist.init_process_group("nccl")' with a '# Training loop...' placeholder), basic verification commands Claude already knows ('nvidia-smi', 'nvcc --version', 'ip addr show'), and duplication — launch/list/terminate shown in both the Python API and curl sections, and the 'Common issues' table overlapping references/troubleshooting.md. This fits 'mostly efficient but includes some unnecessary explanation or could be tightened', not the lean anchor 5 nor the heavily padded anchor 2.

3 / 5

Actionability

Guidance is mostly executable and copy-paste ready: concrete SSH commands ('ssh ubuntu@<INSTANCE-IP>'), real curl endpoints ('https://cloud.lambdalabs.com/api/v1/instance-operations/launch'), complete Python client requests, 'torchrun --nproc_per_node=8 train_ddp.py', and Slurm 'srun' invocation. It falls short of anchor 5 only due to minor gaps like the '# Training loop...' placeholder in the DDP example and pseudo-variables in the fine-tune workflow.

4 / 5

Workflow Clarity

Multi-step processes are clearly sequenced (account setup → launch → SSH connect; fine-tuning workflow numbered launch → setup → download → train), but terminating instances is a destructive operation (local SSD is ephemeral, and the skill itself warns 'Data lost after terminate') and the terminate workflows — 'api.terminate_instance(request)' and the curl terminate call — include no validation checkpoint (no verify-instance-ID, no confirm-checkpoints-saved step). Per the rubric's destructive-operation cap, workflow clarity cannot exceed 3; the sequence quality keeps it from scoring 2.

3 / 5

Progressive Disclosure

The body is well organized with clear section headers, and the References section clearly signals two real one-level-deep bundle files ('[Advanced Usage](references/advanced-usage.md) - Multi-node training, API automation' and '[Troubleshooting](references/troubleshooting.md) - Common issues and solutions'), both of which exist and match their descriptions. It is not anchor 5 because some content duplicated in the references is fully inlined (the Common issues table and the full Python + curl API reference), which is a minor organization gap rather than the 'content that should be separate is inline' of anchor 3, where references would also be poorly signaled.

4 / 5

Total

14

/

20

Passed

Description

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

The description clearly and explicitly answers both what the skill provides and when to use it, with concrete trigger phrases covering SSH access, persistent filesystems, and multi-node clusters. Its weaknesses are the second-person phrasing ('Use when you need'), which costs specificity, and the missing vendor name, which leaves moderate overlap risk with other GPU-cloud providers.

Suggestions

Rewrite in third person to remove the second-person penalty: 'Use when the task requires dedicated GPU instances...' instead of 'Use when you need...'.

Include the vendor name ('Lambda Labs') in the description so the skill is clearly distinguishable from the similar GPU-cloud providers (RunPod, Vast.ai) it currently overlaps with.

DimensionReasoningScore

Specificity

The description lists several concrete capabilities — 'dedicated GPU instances with simple SSH access, persistent filesystems, or high-performance multi-node clusters' — which would fit anchor 4, but the second-person phrasing 'Use when you need' violates the third-person voice requirement and reduces the specificity score by 1 per the rubric guideline. It is not anchor 2 because the domain and multiple concrete capabilities are clearly named rather than generic.

3 / 5

Completeness

It explicitly answers both questions: what ('Reserved and on-demand GPU cloud instances for ML training and inference') and when ('Use when you need dedicated GPU instances with simple SSH access, persistent filesystems, or high-performance multi-node clusters for large-scale training'), matching the anchor-5 pattern of a clear what followed by concrete trigger phrases. Not anchor 4, since the when clause is already fully explicit rather than merely adequate.

5 / 5

Trigger Term Quality

Good natural keyword coverage: 'GPU cloud instances', 'ML training', 'inference', 'SSH access', 'multi-node clusters', 'large-scale training' — phrases a user with this need would plausibly say. It falls short of anchor 5's comprehensive synonym coverage because natural variations like specific GPU names (H100, A100), 'rent GPUs', or 'GPU server' are missing.

4 / 5

Distinctiveness Conflict Risk

The description never names the vendor ('Lambda Labs' appears only in the frontmatter name and body), so it could describe other dedicated-GPU-cloud providers like RunPod or Vast.ai, which the body itself lists as alternatives. This is 'somewhat specific but could still overlap with similar skills' — not anchor 4, which requires being mostly distinct with only minor overlap risk.

3 / 5

Total

15

/

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

skill_md_line_count

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

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/infrastructure/lambda-labs/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.