CtrlK
BlogDocsLog inGet started
Tessl Logo

debug-openshell-cluster

Debug why an OpenShell gateway deployment is unhealthy, unreachable, or unable to create sandboxes. Use for gateway health failures, Docker/Podman runtime issues, Helm failures, Kubernetes scheduling, TLS or auth, gateway interceptors, supervisor middleware startup or runtime failures, external compute-driver sockets, VM drivers, or sandbox startup. Trigger keywords - debug gateway, gateway failing, deployment failing, helm install failing, cluster health, gateway health, gateway not starting, health check failed, sandbox pending, docker driver, podman driver, kubernetes driver, external driver, compute driver socket, gateway interceptor, supervisor middleware, middleware failed, vm driver.

75

Quality

92%

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

85%Weight 40%Scale 1-3

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A highly actionable, well-sequenced debugging runbook with concrete commands throughout; its main weakness is length and repetition between the step walkthroughs and the summary failure table.

Suggestions

Trim redundancy between the per-platform Step sections and the 'Common Failure Patterns' table — the table can cross-reference the steps rather than restating the same findings verbatim.

Consider splitting the deep Kubernetes sidecar-topology and cert-manager/JWT detail (Steps 6) into a reference file, keeping SKILL.md as a tighter overview.

DimensionReasoningScore

Conciseness

Operational and free of conceptual padding, but at ~415 lines it is verbose with notable redundancy between the per-platform Step sections and the 'Common Failure Patterns' table that re-states the same findings.

2 / 3

Actionability

Provides fully executable, copy-paste-ready commands — specific kubectl jsonpath expressions, named secrets, systemd units, and stat/rg/journalctl invocations for each failure mode.

3 / 3

Workflow Clarity

Seven explicitly sequenced diagnostic steps with a clear stop condition ('stop once the root cause is clear') and ordered gating (e.g. inspect startup dependencies before the compute platform).

3 / 3

Progressive Disclosure

No bundle files exist, so the single-file SKILL.md is appropriately self-contained and well-sectioned (Overview, Prerequisites, Workflow, Common Failure Patterns, Reporting) with an in-file platform matrix for navigation.

3 / 3

Total

11

/

12

Passed

Description

100%Weight 40%Scale 1-3

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 specific, trigger-rich, and clearly separates capability from invocation conditions, all in third person. It is a strong, low-conflict trigger description.

DimensionReasoningScore

Specificity

Lists multiple concrete actions and subsystems — 'Debug why an OpenShell gateway deployment is unhealthy, unreachable, or unable to create sandboxes' across Docker/Podman, Helm, Kubernetes, TLS, interceptors, middleware, and VM drivers.

3 / 3

Completeness

Clearly answers both what ('Debug why an OpenShell gateway deployment is unhealthy...') and when ('Use for gateway health failures...') with explicit triggers, satisfying the top anchor.

3 / 3

Trigger Term Quality

Explicit 'Trigger keywords' list includes natural user phrasings like 'debug gateway', 'gateway not starting', 'health check failed', 'sandbox pending', and 'helm install failing' that a user would actually say.

3 / 3

Distinctiveness Conflict Risk

Narrowly scoped to OpenShell gateway deployment debugging with domain-specific triggers, making it unlikely to fire for unrelated skills.

3 / 3

Total

12

/

12

Passed

Validation

100%

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

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
NVIDIA/OpenShell
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.