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.

Quality

96%

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

Quality

Content

92%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 is well-structured and highly actionable: a diagnostic-first workflow with validation checkpoints, concrete commands, and clean progressive disclosure into verified reference files. Only minor conciseness trims would improve it.

Suggestions

Tighten the opening paragraph and 'What this skill does not cover' section — the diagnostic-first summary largely duplicates the workflow steps that follow.

Consider folding the 'When the user is stuck' kubectl block into references/troubleshooting.md to keep the overview leaner, since it is itself a triage reference.

Dimension	Reasoning	Score
Conciseness	Mostly lean with dense tables and no explaining of basic Kubernetes/Helm concepts, but a few prose passages (the intro paragraph and 'What this skill does not cover') go slightly beyond the minimum needed.	4 / 5
Actionability	Provides copy-paste-ready commands throughout — helm lint/template/upgrade, a parallel kubectl log-gathering block, and openssl rand generation — covering the common operational cases.	5 / 5
Workflow Clarity	A five-step ordered workflow with an explicit 'Validate before applying' step, a fix-and-retry feedback loop, and warnings on destructive operations (helm uninstall, kubectl delete sts).	5 / 5
Progressive Disclosure	SKILL.md is a clear overview with a diagnose table mapping each situation to one-level-deep references; all four referenced files (install-paths, secrets, values-model, troubleshooting) exist and are clearly signaled.	5 / 5
	Total	19 / 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: it states concrete capabilities, gives an explicit 'Invoke when' trigger clause with natural user phrasings, and occupies a clearly distinct niche. No first/second-person voice or vague fluff is present.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions — install/upgrade/operate, install-path selection across three modes, secret generation, the values.yaml model, and failure triage — giving comprehensive coverage rather than vague language.	5 / 5
Completeness	Explicitly states both what the skill does and when to invoke it, with concrete trigger phrases anchored by 'Invoke when a user asks about...'.	5 / 5
Trigger Term Quality	The 'Invoke when' clause covers natural user phrasings (deploying Sim, authoring values.yaml, debugging a pod that won't start, upgrading a release, wiring into a secret manager) with synonym variation.	5 / 5
Distinctiveness Conflict Risk	Tightly scoped to the Sim Helm chart on Kubernetes, a clear niche with distinct triggers and minimal overlap with other skills.	5 / 5
	Total	20 / 20 Passed

Validation

100%

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 — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: simstudioai/sim
Path: helm/sim/.claude/skills/sim-helm/SKILL.md
Commit: 804a452

Reviewed: 3 minutes ago

Table of Contents

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.