CtrlK
BlogDocsLog inGet started
Tessl Logo

sim-helm

Install, upgrade, and operate the Sim Helm chart on Kubernetes. Covers install path selection (inline / existingSecret / External Secrets Operator), required secret generation, the values.yaml mental model (env vs envDefaults vs Secret), and common failure triage. Invoke when a user asks about deploying Sim to a cluster, authoring a Sim values.yaml, debugging a Sim pod that won't start, upgrading a Sim release, or wiring Sim into a secret manager.

80

Quality

100%

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

100%

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

A well-structured, diagnostic-first operations skill: lean dense content, fully executable commands, a sequenced workflow with validation and rollback, and clean one-level-deep reference disclosure.

DimensionReasoningScore

Conciseness

Dense tables and rules with no padding explaining Kubernetes/Helm basics Claude already knows; every section (workflow, secret modes, required secrets, rules of engagement) earns its place. Not below 3 because the length is operational substance, not verbosity.

3 / 3

Actionability

Copy-paste-ready commands throughout — "helm lint helm/sim --values", "openssl rand -hex 32", exact value keys like "app.secrets.existingSecret.enabled: true", and a full parallel kubectl logging block.

3 / 3

Workflow Clarity

A clear five-step sequence (Capture → Diagnose → Propose → Validate → Deliver) with an explicit validation checkpoint ("Validate before applying" with lint/template/dry-run) and a feedback loop ("If lint or template fails, fix the values — do not work around chart validation").

3 / 3

Progressive Disclosure

Overview SKILL.md signals one-level-deep references (install-paths.md, secrets.md, values-model.md, troubleshooting.md) via a diagnostic table, and those files exist as real bundle files. Not below 3 because navigation is explicit and content is appropriately split.

3 / 3

Total

12

/

12

Passed

Description

100%

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 strong, third-person description that names concrete capabilities, provides natural trigger phrases, and explicitly covers both what and when. No fluff or over-claims.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — "Install, upgrade, and operate", "install path selection (inline / existingSecret / External Secrets Operator)", "required secret generation", "values.yaml mental model", and "failure triage" — matching the anchor for specific concrete actions.

3 / 3

Completeness

Explicitly answers both what (install/upgrade/operate the Sim Helm chart and its sub-tasks) and when via an explicit "Invoke when..." clause listing concrete triggers.

3 / 3

Trigger Term Quality

Natural phrasing users would say is well covered: "deploying Sim to a cluster", "authoring a Sim values.yaml", "debugging a Sim pod that won't start", "upgrading a Sim release", "wiring Sim into a secret manager".

3 / 3

Distinctiveness Conflict Risk

Tightly scoped to the Sim Helm chart on Kubernetes with niche-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
simstudioai/sim
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.