Name: kubeshop
Rating: 53.6 (1 reviews)
Author: membranedev

kubeshop

Kubeshop (Testkube) integration. Manage data, records, and automate workflows. Use when the user wants to interact with Kubeshop (Testkube) data.

Quality

60%

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

Fix and improve this skill with Tessl

tessl review fix ./skills/kubeshop/SKILL.md

Quality

Content

63%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, largely executable CLI integration guide with genuine validation feedback loops in the connection workflow. Its main weaknesses are a slightly padded overview, an unresolved CONNECTION_ID placeholder, and a monolithic single-file layout that does not use progressive disclosure.

Suggestions

Remove the opening paragraph defining what Testkube is (Claude already knows) and tighten the auth/connection prose to commands plus one-line context.

Resolve the CONNECTION_ID placeholder by showing how to capture it from the `--json` connection output before the action-run examples.

Move the proxy flags table and detailed clientAction states into a separate reference file and link to it from SKILL.md to enable progressive disclosure.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient with concrete commands, but opens with a concept-explaining paragraph ('Testkube is a cloud-native test orchestration and execution framework...') and padded phrasing like 'so you can focus on the integration logic rather than auth plumbing', fitting the 'mostly efficient but some unnecessary explanation' anchor.	3 / 5
Actionability	It provides copy-paste-ready commands for install, login, connection, polling, action search/run, and a proxy flags table, with only minor gaps like the unresolved CONNECTION_ID placeholder, matching the 'mostly executable guidance with minor gaps' anchor.	4 / 5
Workflow Clarity	The connection flow is clearly sequenced with validation checkpoints (poll until READY, branch on CLIENT_ACTION_REQUIRED, handle CONFIGURATION_ERROR), but the 'skip to Step 2' references point to an implicitly-defined Step 2 and the polling step is labeled '1b', leaving minor gaps below the explicit-checklist level 5.	4 / 5
Progressive Disclosure	The ~140-line body is well-sectioned with headers but everything lives inline in SKILL.md with no external reference files (no references/ scripts/ assets/ exist), so content that could be split (e.g. the proxy flags reference) is inlined, fitting the 'some structure but content that should be separate is inline' anchor.	3 / 5
	Total	14 / 20 Passed

Description

57%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 correctly pairs a 'what' with an explicit 'Use when' trigger and is anchored to a distinct product, but its action verbs are generic ('manage', 'automate') rather than concrete and the trigger phrasing lacks synonyms or variations. It is solid but not exemplary.

Suggestions

Replace generic verbs with concrete operations the integration performs (e.g., 'Create, run, and inspect Testkube test executions and test suites').

Broaden the trigger clause with natural synonyms users say (e.g., 'Use when the user wants to run, schedule, or check Kubernetes test workflows in Testkube').

Tie the 'when' to specific nouns users mention (test executions, test suites, artifacts) to sharpen distinctiveness.

Dimension	Reasoning	Score
Specificity	It names the domain (Kubeshop/Testkube) but the actions — 'Manage data, records, and automate workflows' — are generic verbs with no concrete operations, matching the 'names domain but actions minimal or generic' anchor rather than the concrete-action level 3.	2 / 5
Completeness	It states both what ('Manage data, records, and automate workflows') and when ('Use when the user wants to interact with Kubeshop (Testkube) data'), but the 'when' clause is generic and could be more specific, matching the level-4 anchor.	4 / 5
Trigger Term Quality	It surfaces the natural product names ('Kubeshop', 'Testkube') plus 'data' and 'workflows', but misses common synonyms or file-type variants, fitting the 'some relevant keywords but missing variations' anchor.	3 / 5
Distinctiveness Conflict Risk	The named product (Kubeshop/Testkube) gives it a clear niche with minimal conflict risk, but the generic action phrasing leaves minor overlap potential, placing it just below the level-5 'clear niche with distinct triggers'.	4 / 5
	Total	13 / 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: membranedev/application-skills
Path: skills/kubeshop/SKILL.md
Commit: f484c82

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.