CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

red-hat-diagnostics

Explain how to gather diagnostic information for Red Hat products (RHEL, OpenShift, Ansible Automation Platform, Satellite) to share with Red Hat Technical Support.

Quality

78%

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

Fix and improve this skill with Tessl

tessl review fix ./rh-basic/skills/red-hat-diagnostics/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

82%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 a strong, command-dense reference: every supported product and deployment variant gets executable collection commands, fallbacks are included, and sensitive-data warning plus upload guidance complete the support-case workflow. Remaining polish is minor — trimming duplicate housekeeping sections and adding a quick archive-verification checkpoint before upload.

DimensionReasoningScore

Conciseness

The body is lean and command-focused ("sos report --only-plugins networking,storage", "foreman-debug -d /tmp/foreman-debug") with no over-explanation of concepts Claude knows, but the duplicated "Prerequisites: None." and "Dependencies: None" sections and a redundant "When to Use This Skill" section are minor padding that keeps it from level 5.

4 / 5

Actionability

Every product path gives copy-paste-ready commands covering the common cases — "dnf install sos" / "sos report" for RHEL, "oc adm must-gather --dest-dir ./must-gather" for OCP (with operator-specific and registry-unavailable fallbacks), complete ansible-playbook log-gathering invocation with extra vars for containerized AAP, and Satellite's "sos report" plus "foreman-debug"; the only vague spot is the un-expanded "Customer Portal file upload API".

5 / 5

Workflow Clarity

The four-step Workflow (identify product, provide commands, warn about sensitive data, explain upload) is a clear sequence, and the AAP section adds an explicit decision point ("Ask deployment type if not specified"), but there are no verification checkpoints such as confirming the archive was created before upload — clear sequence with minor validation gaps, matching anchor 4 rather than anchor 5's explicit validation steps.

4 / 5

Progressive Disclosure

Structure is good: an overview workflow, cleanly separated per-product sections, and a clearly signaled one-level "Reference Docs" section of external doc links; no bundle files exist, and nothing here needs splitting. Minor organization gaps (the redundant Prerequisites/Dependencies sections) keep it at anchor 4 rather than 5.

4 / 5

Total

17

/

20

Passed

Description

65%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 specific and distinctive, clearly scoping the skill to Red Hat support diagnostics across four named products. Its main weakness is the absence of explicit "when to use" trigger guidance, and it lacks the natural tool vocabulary (sos report, must-gather, support case) users would likely mention. Adding a 'Use when...' clause with those terms would lift both completeness and trigger term quality.

Suggestions

Add an explicit trigger clause, e.g. 'Use when the user needs to collect diagnostics (sos report, must-gather, foreman-debug) for a Red Hat support case.'

Include the natural tool names users actually say — 'sos report', 'must-gather', 'support case' — to improve trigger term coverage.

State the actions more concretely (e.g. 'Provides per-product diagnostic collection commands and upload instructions for Red Hat support cases') to move specificity beyond the 1-2 action level.

DimensionReasoningScore

Specificity

"Explain how to gather diagnostic information" names the domain and effectively two concrete actions (gather diagnostics, "share with Red Hat Technical Support"), matching the anchor for domain plus 1-2 concrete actions rather than the several specific actions of level 4.

3 / 5

Completeness

The "what" is clear (gather diagnostic information for Red Hat products to share with support), but there is no "Use when..." clause or equivalent explicit trigger guidance, which caps completeness at 3 per the judging guidelines; the purpose clause "to share with Red Hat Technical Support" only weakly implies when.

3 / 5

Trigger Term Quality

Product names "RHEL, OpenShift, Ansible Automation Platform, Satellite" plus "diagnostic information" and "Technical Support" are natural terms users would say, but common tool phrases like "sos report", "must-gather", or "support case" are missing — good coverage with a few natural terms absent, which is the level 4 anchor.

4 / 5

Distinctiveness Conflict Risk

The enumerated Red Hat products ("RHEL, OpenShift, Ansible Automation Platform, Satellite") and the support-diagnostics context carve out a clear niche with distinct triggers and minimal overlap with any other plausible skill.

5 / 5

Total

15

/

20

Passed

Validation

93%

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

CriteriaDescriptionResult

frontmatter_unknown_keys

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

Warning

Total

15

/

16

Passed

Repository

RHEcosystemAppEng/agentic-plugins

Path

rh-basic/skills/red-hat-diagnostics/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.