Name: rancher-labs
Rating: 56.8 (1 reviews)
Author: membranedev

rancher-labs

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

Quality

65%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/rancher-labs/SKILL.md

Quality

Content

68%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 an efficient, executable CLI integration guide with a solid connection-state workflow. Its main gaps are the absence of verification steps after destructive action/proxy operations and the lack of Rancher-specific action examples.

Suggestions

Add a verification/feedback step after running actions or proxy requests, e.g. inspect the `output`/response status and retry or surface errors before proceeding.

Include at least one concrete Rancher-specific action example (e.g. listing clusters or namespaces) rather than only generic `action run <actionId>` placeholders.

Trim the introductory context paragraph and the 'so you can focus on the integration logic' phrasing to assume Claude's existing knowledge.

Dimension	Reasoning	Score
Conciseness	The body is mostly lean and command-focused, but the opening context paragraph ('Rancher Labs provides a Kubernetes management platform...') and phrases like 'so you can focus on the integration logic rather than auth plumbing' are mild over-explanation that could be trimmed.	4 / 5
Actionability	It provides concrete, copy-paste-ready commands throughout (install, login, connection ensure, action run, request) with a flags table, but relies on placeholders (CONNECTION_ID, <actionId>) and gives no Rancher-specific action examples.	4 / 5
Workflow Clarity	A clear sequence exists with a feedback loop for connection states (READY/BUILDING/CLIENT_ACTION_REQUIRED), but running actions and proxy requests (which can be destructive via POST/PUT/DELETE) lack any result verification or error-recovery checkpoint, capping the score.	3 / 5
Progressive Disclosure	The single file is well-organized into clear sections with no nested or buried references and easy navigation; no bundle files exist, and the self-contained CLI guide is appropriately placed, though the proxy/clientAction detail could arguably live in a reference file.	4 / 5
	Total	15 / 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 is third-person, concise, and clearly answers both what the skill does and when to use it. Its main weakness is generic action verbs and trigger phrasing that lack Rancher/Kubernetes-specific concrete terms.

Suggestions

Replace generic verbs with concrete Rancher operations, e.g. 'deploy and manage Kubernetes clusters, node pools, projects, and namespaces'.

Expand the 'Use when' trigger with natural synonyms users say, such as Kubernetes, k8s, clusters, containers, or Rancher management.

Tie the trigger to specific entities from the body (clusters, projects, secrets, catalogs) to sharpen distinctiveness.

Dimension	Reasoning	Score
Specificity	The description names the domain ('Rancher Labs integration') and lists a few actions ('Manage data, records, and automate workflows'), but the actions are generic rather than concrete Rancher-specific operations like deploying clusters or managing nodes.	3 / 5
Completeness	Both 'what' ('Manage data, records, and automate workflows') and an explicit 'when' ('Use when the user wants to interact with Rancher Labs data') are present, but the trigger clause is somewhat generic and could be more specific.	4 / 5
Trigger Term Quality	It includes the core brand term 'Rancher Labs' and 'Rancher Labs data', but misses common natural synonyms and variations a user might say such as Kubernetes, k8s, clusters, or containers.	3 / 5
Distinctiveness Conflict Risk	'Rancher Labs' is a specific named product giving it a clear niche with minimal conflict risk, though the generic 'interact with Rancher Labs data' trigger leaves minor overlap risk with other Rancher-oriented skills.	4 / 5
	Total	14 / 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/rancher-labs/SKILL.md
Commit: f484c82

Reviewed: 5 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.