CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

launch-openshell-gator

Launch and supervise OpenShell gator agents. Use when starting gator on issues or PRs, checking gator sandboxes, building the gator sandbox image, restarting stuck gators, inspecting gator logs, or experimenting with gator harness/model overrides. Trigger keywords - launch gator, start gator, run gator, gator sandbox, supervised gator, gator logs, restart gator.

Quality

88%

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.

The content is an unusually actionable, well-sequenced operator runbook with excellent validation checkpoints and failure-recovery guidance; its weaknesses are token efficiency (repeated boilerplate guard blocks) and the absence of progressive disclosure (all reference material inlined in one long SKILL.md with no bundle files). Splitting troubleshooting and option-compatibility detail into references/ files would address both lowest dimensions at once.

Suggestions

Factor the repeated gateway-name/sandbox-name/PR-number regex validation snippets into a single 'Input Normalization' snippet defined once and referenced by shorthand in each launch/monitor/restart block, cutting substantial duplicated tokens (conciseness).

Move the deep reference material — Kubernetes image delivery options, provider credential/refresh rotation, and the same-SHA duplicate-guard exception list — into references/ files (e.g. references/image-delivery.md, references/credentials.md, references/same-sha-guard.md) and keep one-line pointers in SKILL.md (progressive_disclosure).

Consolidate the Preflight Steps 5 and 6 gateway blocks (both run the identical 'sandbox list' with the same guard) into one combined check step to remove duplicated commands (conciseness).

DimensionReasoningScore

Conciseness

The body is mostly efficient — all repo-specific detail Claude could not know, no generic concept explanations — but the gateway-name regex guard block is repeated verbatim roughly ten times across preflight, launch, monitoring, and restart sections, and dense paragraphs (image delivery modes, refresh credential rotation, same-SHA guard policy) could be tightened or moved out of the always-loaded body. It sits at 'mostly efficient but could be tightened', clearly above the verbose anchor of 2 but below 4 because the repeated guard boilerplate is genuinely redundant tokens.

3 / 5

Actionability

Guidance is fully executable throughout: exact copy-paste bash for every preflight check and launch variant, concrete regex validations for names and numbers, full run.sh invocations with all flags, and a sentinel table pairing each status with a specific operator action. Specific examples cover the common cases (PR watcher, issue, issue/PR pair, authorized-maintainer prompt, model experiment).

5 / 5

Workflow Clarity

The multi-step process is clearly sequenced (Preflight Steps 1–6, launch, monitor, restart, troubleshoot) with explicit validation checkpoints at every step (expected results and branch-on-failure guidance, e.g. 'If the gateway is unreachable... switch to debug-openshell-cluster'), feedback loops for error recovery (retry caps, --reset-refresh, relaunch reasons), and destructive sandbox deletion gated behind 'check that the sandbox is truly stale or that the operator asked for a restart'.

5 / 5

Progressive Disclosure

Section structure is good (clear headers, a key-paths table, sentinel tables, pointers to other skills and scripts/agents/gator/README.md), but this is a ~430-line monolith with no bundle files at all: reference-heavy material that clearly belongs in separate files — image delivery option compatibility, provider credential/refresh handling, same-SHA duplicate-guard exception policy, sentinel interpretation — is inlined into the always-loaded SKILL.md body, matching the anchor 'some structure but content that should be separate is inline'. It is above 2 because navigation via headers is easy and cross-skill references are clearly signaled, but below 4 given the volume of inlined detail.

3 / 5

Total

16

/

20

Passed

Description

100%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 is exemplary: third-person, concrete, and complete with an explicit 'Use when...' clause plus a dedicated trigger-keyword list. Its only minor flaw is mild redundancy between the 'Use when' scenarios and the 'Trigger keywords' list, which slightly pads length without adding information.

DimensionReasoningScore

Specificity

The description lists multiple specific concrete actions — "starting gator on issues or PRs, checking gator sandboxes, building the gator sandbox image, restarting stuck gators, inspecting gator logs, or experimenting with gator harness/model overrides" — comprehensively covering the skill's operator surface with no vague filler.

5 / 5

Completeness

It explicitly answers both questions: what ("Launch and supervise OpenShell gator agents") and when ("Use when starting gator on issues or PRs, checking gator sandboxes, building the gator sandbox image, restarting stuck gators, inspecting gator logs...") with concrete trigger phrases, matching the top anchor exactly.

5 / 5

Trigger Term Quality

It gives comprehensive natural trigger coverage including synonyms ("launch gator, start gator, run gator") plus scenario phrases users would actually say ("gator sandbox, supervised gator, gator logs, restart gator"), matching the anchor for full coverage of natural terms.

5 / 5

Distinctiveness Conflict Risk

"gator" is a distinct niche identifier and every trigger is gator-specific (gator sandbox, gator logs, restart gator), so the risk of firing for an unrelated skill is minimal — a clear niche with distinct triggers.

5 / 5

Total

20

/

20

Passed

Validation

75%

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

Validation — 12 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

metadata_version

'metadata.version' is missing

Warning

metadata_field

'metadata' should map string keys to string values

Warning

relative_links

Relative link issues: 9 missing

Warning

referenced_paths_exist

Referenced path issues: 17 missing, 17 deeper-than-1-level

Warning

Total

12

/

16

Passed

Repository

NVIDIA/OpenShell

Path

.agents/skills/launch-openshell-gator/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.