CtrlK
BlogDocsLog inGet started
Tessl Logo

ubuntu-helm-creator

Generate Kubernetes Helm charts backed by Canonical Ubuntu OCI images (rocks). Use when creating a new Helm chart from scratch for a rock; achieving feature parity with an upstream chart (Bitnami, ArtifactHub, GitHub); adding features to an existing chart. Trigger phrases are "generate helm chart", "create helm chart based on upstream chart", "helm chart for app", "feature parity with upstream", "add feature to chart", "scaffold chart", "ubuntu rock helm", "rock-backed chart". Produces chart scaffolding, values.yaml with image.digest, PSS-Restricted security defaults, Pebble-wired probes, tests, and README.md.

78

Quality

Does it follow best practices?

Impact

No eval scenarios have been run

SecuritybySnyk

Advisory

Suggest reviewing before use

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.

The body is a lean, action-oriented workflow that gives executable code and commands, explicit validation/retry feedback loops, and one-level-deep delegation to sibling skills and bundle scripts. It assumes Claude's competence and avoids restating known concepts.

DimensionReasoningScore

Conciseness

The body is dense and token-efficient: executable YAML/Bash blocks, a decision tree, and numbered steps with almost no explanation of concepts Claude already knows. A minor repeat of the description's opening line and a few framing sentences do not pad the content meaningfully — every token earns its place.

3 / 3

Actionability

Provides copy-paste-ready, executable guidance throughout — real script invocations ("scripts/inspect-rock.sh inspect…"), concrete values.yaml/image wiring templates, Pebble probe YAML, and a filled-in task.yaml — rather than abstract direction.

3 / 3

Workflow Clarity

Both modes present a clearly sequenced, numbered workflow (Step 0 decision tree → steps 1–6 Zero-to-One; steps 1–10 Feature Development) with explicit validation checkpoints ("Validate" via ubuntu-helm-validator) and a Failure and Retry Protocol with capped attempts and rollback for destructive/batch feature changes.

3 / 3

Progressive Disclosure

The body is an overview that delegates to clearly signaled one-level-deep references — sibling skills ([ubuntu-helm-validator], [ubuntu-helm-analyzer], [ubuntu-helm-docs], helm-generator) and the real scripts/inspect-rock.sh and scripts/setup.sh bundle files — with no deep nesting and well-organized sections.

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.

The description is concise yet complete: it states concrete capabilities, an explicit "Use when…" trigger clause with natural keyword phrases, and a distinctive niche. It is written in third person and avoids verbosity or vague fluff.

DimensionReasoningScore

Specificity

Names concrete outputs — "Produces chart scaffolding, values.yaml with image.digest, PSS-Restricted security defaults, Pebble-wired probes, tests, and README.md" — alongside the core action of generating Helm charts, listing multiple specific concrete actions rather than vague language.

3 / 3

Completeness

Clearly answers both what ("Generate Kubernetes Helm charts backed by Canonical Ubuntu OCI images (rocks)… Produces chart scaffolding…") and when ("Use when creating a new Helm chart from scratch for a rock; achieving feature parity…; adding features to an existing chart") with explicit triggers.

3 / 3

Trigger Term Quality

Explicitly enumerates natural trigger phrases a user would actually say ("generate helm chart", "helm chart for app", "feature parity with upstream", "add feature to chart", "scaffold chart", "ubuntu rock helm", "rock-backed chart"), giving strong coverage of natural terms.

3 / 3

Distinctiveness Conflict Risk

A clear niche (Ubuntu rock-backed Helm charts) with distinct, specific triggers ("ubuntu rock helm", "rock-backed chart", "feature parity with upstream") makes it unlikely to fire for unrelated skills.

3 / 3

Total

12

/

12

Passed

Validation

87%

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

Validation14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

relative_links

Relative link issues: 7 suspicious

Warning

Total

14

/

16

Passed

Repository
canonical/helm-charts
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.