Tessl • The package manager for agent skills

SkillPublic

lambda-gpu-cloud

Safely inspect and operate Lambda Cloud GPU instances through the documented Cloud API and SSH, with explicit approval before billable or destructive actions.

Quality

75%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./backend/cli/skills/cloud-compute/lambda-labs/SKILL.md

Quality

Content

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

A well-structured, lean instruction skill: a copy-paste API pattern, a sequenced operating policy with reconciliation and verification checkpoints, and clear security boundaries. The only notable gap is the absence of concrete mutation-request examples, which are delegated to the live official docs.

Dimension	Reasoning	Score
Conciseness	The body is lean and assumes Claude's competence — no padding with known concepts, and the curl pattern is minimal and purposeful. Minor repetition in the credential boundary ("Never print, log, persist, or put the key in a URL" alongside "intentionally unavailable there") keeps it just below the 'every token earns its place' anchor.	4 / 5
Actionability	Concrete, copy-paste-ready guidance: base URL "https://cloud.lambda.ai/api/v1", an executable curl command that pipes the auth header over stdin, exact UI paths ("Customize > Compute > Lambda", "Customize > Compute > SSH"), and pinned sources of truth. Not 5 because mutation endpoints (launch, terminate, storage attach) get no example requests — they are deferred to the external API docs.	4 / 5
Workflow Clarity	The numbered Operating policy is a clear sequence with explicit validation checkpoints and feedback loops: "Make one mutation, retain its response identifier, then reconcile with a list request", "Verify SSH and the intended workload after launch", and "Verify required outputs before termination", each preceded by explicit approval gates for billable or destructive actions. This matches the anchor 'Clear sequence with explicit validation steps; feedback loops for error recovery'.	5 / 5
Progressive Disclosure	No bundle files exist (references/, scripts/, assets/ are all absent) and none are needed. The ~40 content lines are organized into five clearly labeled sections (credential boundary, API contract, Operating policy, SSH handoff, Sources of truth) with well-signaled one-level-deep external links, satisfying the simple-skill exception for a 5.	5 / 5
	Total	18 / 20 Passed

Description

57%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 distinctive, domain-specific description with a clear 'what', but it lacks any 'Use when...' trigger guidance and uses the generic verb "operate" instead of concrete actions. These gaps cap three of the four dimensions at 3.

Suggestions

Add a 'Use when...' clause, e.g. "Use when the user mentions Lambda Cloud, Lambda Labs, renting or launching GPU instances, or checking GPU availability and pricing" — this would raise both completeness and trigger_term_quality.

Replace the generic "operate" with specific concrete actions such as "launch, list, and terminate instances; check GPU capacity and current pricing" to raise specificity.

Include natural synonyms and phrases users would actually say ("on-demand GPUs", "GPU availability", "Lambda Labs") for broader trigger-term coverage.

Dimension	Reasoning	Score
Specificity	"Safely inspect and operate Lambda Cloud GPU instances" names the domain and two actions ("inspect", "operate"), but "operate" is generic, matching the anchor 'Names domain and 1-2 concrete actions, but not comprehensive'. It is not 4 because it does not list several specific concrete actions like launch, terminate, or list instances.	3 / 5
Completeness	The 'what' is clear ("inspect and operate Lambda Cloud GPU instances through the documented Cloud API and SSH"), but there is no 'Use when...' or equivalent trigger clause anywhere, so 'when' is missing entirely. Per the judging guidelines, a missing 'Use when' clause caps completeness at 3; it is not 4 because 'when' is not even weakly implied.	3 / 5
Trigger Term Quality	"Lambda Cloud", "GPU instances", "SSH", and "Cloud API" are relevant domain-specific keywords a user would say, but the description misses common variations and synonyms such as "Lambda Labs", "rent/launch a GPU", or "on-demand capacity". Not 2 (terms are domain-specific, not generic); not 4 (synonym coverage is absent).	3 / 5
Distinctiveness Conflict Risk	"Lambda Cloud GPU instances through the documented Cloud API and SSH" names a clear niche with distinct triggers unlikely to overlap with other skills, matching the anchor 'Clear niche with distinct triggers; minimal conflict risk'.	5 / 5
	Total	14 / 20 Passed

Validation

87%

Warnings & errors only

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

Criteria	Description	Result
metadata_version	'metadata.version' is missing	Warning
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	14 / 16 Passed

Repository: synthetic-sciences/openscience
Path: backend/cli/skills/cloud-compute/lambda-labs/SKILL.md
Revision: 6a85742

Reviewed: 22 days ago

Discovery Implementation Validation

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.

lambda-gpu-cloud

Table of Contents

Is this your skill?