ubuntu-helm-analyzer

Obtain and analyze a Helm chart (local path, ArtifactHub URL, Helm repo reference, or Git URL) and extract an ordered list of discrete features as YAML. Use when: analyzing an upstream chart before feature parity, comparing charts, listing features in a reference chart, understanding chart structure. Trigger phrases: "analyze chart", "list features in chart", "compare chart features", "what features does this chart have".

Quality

84%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Low

Low-risk findings worth noting

Quality

Content

75%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 content is a well-structured, mostly executable workflow with clear sequencing and an explicit validation step, tailored to a read-only analysis task. Its main weakness is that the final validation step is described rather than given as an exact command and lacks an explicit error-recovery loop.

Suggestions

In Step 6, provide the exact `yq` validation command(s) (e.g., the specific expression(s) to assert required fields and sorting) instead of only instructing to use yq.

Add an explicit feedback loop to Step 6: 'If validation fails, fix the offending feature entry and re-run the validation command until it passes.'

Consider extracting the deprecated-apiVersion list and the priority-ranking table into a short reference file (e.g. references/deprecated-apis.md) to keep the core workflow leaner, with a clearly signaled one-level-deep link.

Dimension	Reasoning	Score
Conciseness	The body is efficient with terse commands and rules and does not explain concepts Claude already knows (e.g., what Helm or Kubernetes is), but a few explanatory clauses could be trimmed, fitting anchor 4 rather than the fully lean anchor 5 and above the noticeably-verbose anchor 3.	4 / 5
Actionability	Provides concrete, copy-paste-ready commands for obtaining charts (helm repo add/update/pull, git sparse-checkout), explicit classification rules, and a concrete YAML output schema, with a minor gap in that Step 6's yq validation command is not spelled out, matching anchor 4 rather than the fully-executable anchor 5.	4 / 5
Workflow Clarity	A clear Step 0-6 sequence is present with an explicit prerequisite tool-check and a Step 6 validation checkpoint against the output schema; the operation is read-only analysis so the destructive-cap does not apply, but the missing explicit validate-fix-retry feedback loop keeps it at anchor 4 rather than anchor 5.	4 / 5
Progressive Disclosure	Well-organized sections (Prerequisites, Input, Workflow, Output, Rules) with a clearly signaled single supporting script (scripts/setup.sh) and no nested references; content is appropriately inline for a skill this size, fitting anchor 4, while the single-file structure does not reach the multi-file navigable clarity of anchor 5.	4 / 5
	Total	16 / 20 Passed

Description

87%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 explicitly covers both what the skill does and when to use it, supplies concrete trigger phrases, and occupies a distinctive Helm-focused niche. Minor room for improvement lies in broader action enumeration and additional trigger synonyms.

Dimension	Reasoning	Score
Specificity	Names the domain (Helm charts) and concrete actions across four input formats ('Obtain and analyze a Helm chart ... and extract an ordered list of discrete features as YAML'), with only minor gaps in breadth of distinct actions, fitting the anchor 4 rather than 3 (which requires only 1-2 actions) and short of 5's comprehensive multi-action coverage.	4 / 5
Completeness	Clearly states what the skill does ('Obtain and analyze a Helm chart ... extract an ordered list of discrete features as YAML') and when to use it ('Use when: analyzing an upstream chart before feature parity, comparing charts ...') with concrete trigger phrases, matching the anchor 5 example precisely.	5 / 5
Trigger Term Quality	Explicit natural trigger phrases are provided ('analyze chart', 'list features in chart', 'compare chart features', 'what features does this chart have') giving good keyword coverage, but a few natural synonyms or extension-style terms are missing, matching anchor 4 rather than the comprehensive anchor 5.	4 / 5
Distinctiveness Conflict Risk	Targets a clear niche (Helm chart feature extraction as YAML) with distinct triggers and minimal overlap risk; the Helm-specific context makes it unlikely to fire for unrelated skills, matching anchor 5.	5 / 5
	Total	18 / 20 Passed

Validation

93%

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

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

Repository: canonical/helm-charts
Path: .agents/skills/ubuntu-helm-analyzer/SKILL.md
Commit: 78b355b

Reviewed: 6 days 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.