CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

recommend-image

Intelligently recommend the optimal S2I builder image or container base image for a project based on detected language/framework, use-case requirements, security posture, and deployment target. Supports GitHub URLs for remote project analysis (delegates to /detect-project). Use this skill when the user needs a container image recommendation, wants to compare image options, or asks about production vs development images. Triggers on /recommend-image command, or when advanced image selection beyond basic version matching is needed. Supports Node.js, Python, Java, Go, Ruby, .NET, PHP, and Perl on Red Hat UBI.

Quality

80%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./rh-developer/skills/recommend-image/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

67%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.

A well-structured interactive workflow with strong human-in-the-loop checkpoints, concrete skopeo commands, and complete output templates. Main weaknesses are redundant reference listings, two references buried in the footer instead of linked where the workflow needs them, and a security-status output element with no producing step.

Suggestions

De-duplicate the references to image-selection-criteria.md: keep the Step 3 callout and the Reference Documentation list, and cut the repeated Image Reference paragraph, or replace it with a one-line pointer.

Link references/builder-images.md inside Step 3 (where variants are evaluated) and references/dynamic-validation.md inside Step 3.5, instead of only listing them in the Dependencies footer.

Add a workflow step (or a line in Step 3.5) that actually queries the Red Hat Security Data API to fill the "Security Status" row of the recommendation template, or remove that row.

DimensionReasoningScore

Conciseness

Mostly efficient — the body is actionable templates rather than concept explanations — but there is real redundancy: "See [references/image-selection-criteria.md] … for comprehensive scoring matrices" appears in Step 3 and again in the Image Reference section with overlapping wording, then all four references are listed a third time in the Reference Documentation footer; the "Skopeo Required for Image Validation" block is also padded. Not 2 because nothing explains concepts Claude already knows; not 4 because the triple-listed references and duplicated callouts could be cut without losing clarity.

3 / 5

Actionability

Gives executable commands ("which skopeo", "skopeo inspect docker://registry.access.redhat.com/ubi9/[candidate-image]") and complete copy-ready markdown templates for the use-case assessment, recommendation output, and confirmation handling. Not 5 because there is no worked end-to-end example (e.g., "Python 3.11 production → ubi9/python-311-minimal") and the actual per-language image catalog is deferred entirely to references, leaving minor gaps inline.

4 / 5

Workflow Clarity

Clear five-step sequence with three explicit "WAIT for user confirmation before proceeding" checkpoints, branching for all three invocation modes, a skopeo-missing fallback, and a feedback loop ("If user has different requirements: Return to Step 2 with new inputs"). Held below 5 by two validation gaps: the output template's "Security Status … Source: Red Hat Security Data API" has no workflow step that produces it, and Step 3 says to "evaluate available variants" without linking the image catalog (references/builder-images.md) where it is needed.

4 / 5

Progressive Disclosure

Good structure: SKILL.md is a workflow overview, all five referenced files (image-selection-criteria.md, human-in-the-loop.md, prerequisites.md, dynamic-validation.md, builder-images.md) exist in references/ and are linked one level deep. Not 5 because builder-images.md and dynamic-validation.md are only signaled in the Dependencies footer rather than at their point of use (Step 3 / Step 3.5), and three of the five reference files are one-line cross-skill pointer stubs (e.g., "../../detect-project/references/builder-images.md") that add an extra hop of indirection.

4 / 5

Total

15

/

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.

A strong description that clearly states a multi-factor recommendation capability with an explicit "Use this skill when…" trigger clause, a command trigger, and a named delegation boundary. Minor improvements: drop the fluffy "Intelligently", and add a few more natural synonyms (e.g., "base image", "containerize").

DimensionReasoningScore

Specificity

Names several concrete capabilities — "recommend the optimal S2I builder image or container base image", "compare image options", "Supports GitHub URLs for remote project analysis (delegates to /detect-project)" — with concrete inputs (language/framework, security posture, deployment target). Falls short of 5 because the action set centers on a single recommend action and opens with the fluffy adverb "Intelligently"; above 3 because multiple specific actions and criteria are explicitly listed.

4 / 5

Completeness

Explicitly answers both: what ("recommend the optimal S2I builder image or container base image for a project based on detected language/framework, use-case requirements, security posture, and deployment target") and when ("Use this skill when the user needs a container image recommendation, wants to compare image options, or asks about production vs development images. Triggers on /recommend-image command"). Matches the anchor-5 pattern of concrete what + explicit trigger phrases.

5 / 5

Trigger Term Quality

Good natural keyword coverage: "container image recommendation", "compare image options", "production vs development images", "S2I builder image", "Triggers on /recommend-image command", plus eight language names. Not 5 because common variations users might say (e.g., "base image", "docker image", "smallest image") are only partially covered; clearly above 3's "some relevant keywords".

4 / 5

Distinctiveness Conflict Risk

Clear niche — S2I/UBI builder-image selection for eight named languages — with distinct triggers (the /recommend-image command) and an explicit boundary statement ("delegates to /detect-project") that reduces overlap with the detection skill. Minor residual overlap with sibling container skills (/s2i-build, /containerize-deploy) keeps it from being conflict-free, but the anchor-5 "clear niche with distinct triggers; minimal conflict risk" is the best fit.

5 / 5

Total

18

/

20

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.

Validation — 14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

metadata_version

'metadata.version' is missing

Warning

frontmatter_unknown_keys

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

Warning

Total

14

/

16

Passed

Repository

RHEcosystemAppEng/agentic-plugins

Path

rh-developer/skills/recommend-image/SKILL.md

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.