CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

openshell-cli

Guide agents through using the OpenShell CLI (openshell) for sandbox management, gateway registration, provider configuration and refresh, profile management, policy iteration, settings, service exposure, BYOC workflows, and attached-provider inference. Covers basic through advanced multi-step workflows. Trigger keywords - openshell, sandbox create, sandbox exec, sandbox connect, logs, provider create, profile list, profile describe, provider refresh, policy set, policy get, settings, service expose, forward, port forward, BYOC, bring your own container, inference, use openshell, run openshell, CLI usage, manage sandbox, manage provider, gateway add, gateway select.

Quality

85%

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

SKILL.md
Quality
Evals
Security

Quality

Content

70%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 delivers exceptional actionability and clearly sequenced, well-validated workflows with thorough error-recovery guidance. Its main weaknesses are token efficiency and progressive disclosure: a 58 KB monolithic SKILL.md inlines extensive rare-path operational detail that should live in per-topic reference files loaded on demand.

Suggestions

Split the deep edge-case material (UpdateSandbox RPC contract, credential placement metadata, stable_placeholder lifecycle, refresh backend migration and recovery markers, stdin reattachment semantics) into per-topic files under references/, keeping SKILL.md to the core command workflows with one-level-deep pointers.

Tighten the long multi-clause conditional paragraphs into scannable bullets or tables (e.g., a table mapping refresh RECOVERY/FAILURE_CODE values to remedies) to cut context tokens while preserving the information.

Move version- and time-sensitive compatibility details (e.g., 'Before OpenShell 0.1.0, the gateway does not migrate legacy inline refresh material', supervisor upgrade ordering) into a dedicated compatibility or deprecated section in a reference file.

DimensionReasoningScore

Conciseness

The ~1090-line (58 KB) body never pads with concepts Claude already knows, but it pervasively inlines rare edge-case minutiae as long dense paragraphs (sandbox UpdateSandbox RPC contract and retry backoff, credential placement metadata rules, stable_placeholder lifecycle, Vault backend migration, stdin reattachment semantics) that most invocations never need and that belong in reference files. This is 'noticeably verbose' with several sections that could be tightened or deferred; it is not a 1 because every sentence is product-specific rather than filler, and not a 3 because the deferrable detail is pervasive rather than isolated.

2 / 5

Actionability

Commands throughout are copy-paste ready with realistic flags and arguments (e.g., the 'policy get --base | sed' pipeline, 'provider refresh configure' with all flags, 'sandbox create --expose' variants), and specific examples cover the common cases for every workflow. This fully matches the top anchor for executable, copy-paste-ready guidance.

5 / 5

Workflow Clarity

Each of the ten workflows is clearly sequenced, and Workflow 4 includes a flowchart, numbered steps, explicit validation checkpoints ('--wait' with documented exit codes 0/1/124, 'policy list' revision status), and a feedback loop back to log monitoring. Destructive and batch operations do carry verification guidance (e.g., "'deletion accepted' means cleanup is still pending. Inspect the sandbox until it disappears"), so the destructive-operation cap is not triggered; error-recovery guidance for named failure codes is extensive.

5 / 5

Progressive Disclosure

The body has clear structure and navigation (ten labeled workflows, companion-skill table, self-teaching --help section), so it is above the 'minimal structure / no headers' level, but no bundle files exist at all — the deep-dive edge-case material that clearly belongs in separate per-topic reference files is inlined in a single monolithic file. This matches 'some structure but content that should be separate is inline'; a 4 would require most content to be appropriately split across files.

3 / 5

Total

15

/

20

Passed

Description

96%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 strong: it comprehensively enumerates the CLI's capability areas, uses third-person imperative voice, and provides an explicit, synonym-rich trigger keyword list that clearly answers both 'what' and 'when'. The only weakness is the inclusion of a few overly generic keywords that create minor overlap risk with unrelated skills.

DimensionReasoningScore

Specificity

The description lists nine concrete capability areas ("sandbox management, gateway registration, provider configuration and refresh, profile management, policy iteration, settings, service exposure, BYOC workflows, and attached-provider inference") that comprehensively cover the CLI's surface as documented in the body. It matches the anchor for multiple specific concrete actions with comprehensive coverage; a 4 would require minor coverage gaps, which are not evident.

5 / 5

Completeness

The 'what' is explicit (the capability list) and the 'when' is explicit via the "Trigger keywords - ..." clause, which is equivalent explicit trigger guidance with concrete trigger phrases, so the missing-'Use when' cap does not apply. Both questions are clearly and concretely answered; a 4 would mean the 'when' was only weakly explicit, which it is not.

5 / 5

Trigger Term Quality

The trigger keyword list spans command-shaped phrases ("sandbox create", "policy set", "gateway add"), natural user phrasings ("manage sandbox", "run openshell", "port forward"), and synonyms ("bring your own container" alongside "BYOC"). This is comprehensive natural-term coverage including synonyms, matching the top anchor rather than the 'a few natural terms missing' level below.

5 / 5

Distinctiveness Conflict Risk

The niche is clear and anchored by the unique product name and its command identifiers, but several listed triggers ("settings", "logs", "inference", "forward", "CLI usage") are generic words that could fire for unrelated requests. This is 'mostly distinct; minor overlap risk' rather than the minimal-conflict top anchor, but clearly above the midpoint.

4 / 5

Total

19

/

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 (1092 lines); consider splitting into references/ and linking

Warning

Total

15

/

16

Passed

Repository

NVIDIA/OpenShell

Path

skills/openshell-cli/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.