CtrlK
BlogDocsLog inGet started
Tessl Logo

red-hat

Red Hat integration. Manage data, records, and automate workflows. Use when the user wants to interact with Red Hat data.

60

Quality

70%

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 ./skills/red-hat/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

78%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 highly actionable with executable commands and a well-sequenced, validated connection workflow, plus clean section organization. Its main weakness is minor verbosity from introductory filler about what Red Hat is.

Suggestions

Cut or move the introductory 'Red Hat is a software company...' paragraph; Claude already knows this and it adds tokens without guidance value.

Add an explicit validate→fix→retry note for actions that mutate state (e.g. 'If action run returns an error field, inspect it and re-run') to lift the workflow clarity to a full feedback loop.

DimensionReasoningScore

Conciseness

The body is mostly efficient with copy-paste-ready commands, but the opening paragraph explaining what Red Hat is ('Red Hat is a software company providing open-source solutions to enterprises...') pads content Claude already knows, keeping it at 3 rather than 4.

3 / 5

Actionability

Provides concrete, executable commands throughout (install, login, connection ensure, action list/run with --input and --json) plus a complete flags table, fully covering the common cases in copy-paste form.

5 / 5

Workflow Clarity

There is a clear install→auth→connect→search→run sequence with state-machine validation (READY/CLIENT_ACTION_REQUIRED/CONFIGURATION_ERROR) and a --wait polling loop; minor gaps in an explicit re-validate-and-retry framing keep it from 5.

4 / 5

Progressive Disclosure

A single self-contained file with no bundle files, organized into clear overview, setup, connection, action-discovery, and best-practices sections; per the simple-skill guideline this earns 5.

5 / 5

Total

17

/

20

Passed

Description

62%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 answers both 'what' and 'when' and names a clear niche, but its action list is generic and its trigger terms lack synonyms. It is solid but could be more concrete and specific.

Suggestions

Replace generic verbs ('Manage data, records, and automate workflows') with concrete Red Hat actions, e.g. 'List Ansible jobs, get Insights vulnerability details, and manage service catalog orders'.

Broaden trigger terms with natural synonyms such as 'Ansible', 'Insights', 'automation', or 'OpenShift' so users' varied phrasings match.

DimensionReasoningScore

Specificity

Names the Red Hat domain plus a few actions ('Manage data, records, and automate workflows'), but the actions are generic and not comprehensive enough to reach 4 or above.

3 / 5

Completeness

States both what it does ('Manage data, records, and automate workflows') and when to use it ('Use when the user wants to interact with Red Hat data'); the 'when' is explicit but generic, so it does not reach 5.

4 / 5

Trigger Term Quality

Includes a natural trigger ('Use when the user wants to interact with Red Hat data') but lacks common synonyms or file-type variants that would push it to 4.

3 / 5

Distinctiveness Conflict Risk

'Red Hat integration' is a clear, narrowly-scoped niche with a distinct trigger, leaving only minor overlap risk rather than the clean-niche level of 5.

4 / 5

Total

14

/

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.

Validation15 / 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
membranedev/application-skills
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.