Name: kubesphere-devops-tenant
Rating: 59.2 (1 reviews)
Author: kubesphere

kubesphere-devops-tenant

Use when operating KubeSphere DevOps as a namespace-scoped tenant with limited permissions, without cluster-admin access, or when accessing DevOps through KubeSphere APIs only

Quality

70%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

High

Do not use without reviewing

Fix and improve this skill with Tessl

tessl review fix ./skills/kubesphere-devops-tenant/SKILL.md

Quality

Content

65%Weight 40%Scale 1-3

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 complete executable examples, but it suffers from substantial duplication and a monolithic structure with no progressive-disclosure offloading, and contradictory status-field guidance across repeated deprecated sections weakens workflow clarity.

Suggestions

De-duplicate the authentication flow (currently shown 3+ times) into a single section and reference it, and remove the verbatim-repeated 'Get concise status' / watch-for-completion blocks (lines 558-595).

Reconcile the contradictory run-status field guidance: pick one shape (Blue Ocean `.state`/`.result` vs Kubernetes `.status.phase`) per API version and label it consistently, rather than mixing `.state` and `.status.phase` within the same deprecated v1alpha2 sections.

Move the large multi-cluster, GitOps, and credential reference sections into separate bundle files (e.g., references/multi-cluster.md, references/gitops.md) and keep SKILL.md as a concise overview with one-level-deep links, since no bundle files currently exist.

Dimension	Reasoning	Score
Conciseness	Core content is dense and valuable, but the body is heavily repetitive (auth flow shown 3+ times, duplicated watch/status loops, repeated v1alpha2 deprecation callouts), matching 'mostly efficient but includes some unnecessary explanation or could be tightened' rather than the lean top anchor.	2 / 3
Actionability	Extensive fully executable curl/kubectl commands with complete JSON payloads, jq filters, and expected outputs make the guidance copy-paste ready, matching the 'fully executable code/commands; specific examples' top anchor.	3 / 3
Workflow Clarity	Multi-step processes are sequenced with polling/validation checkpoints, but conflicting status-field guidance across duplicate deprecated sections (`.state` vs `.status.phase` used inconsistently) muddies the workflow, matching 'sequence present but checkpoints missing or implicit' rather than the fully clear top anchor.	2 / 3
Progressive Disclosure	Sections are well-organized with headers, but with no bundle files present the ~1270-line body is monolithic with multi-cluster/GitOps/credential reference content inlined that could be split, matching 'some structure but content that should be separate is inline'.	2 / 3
	Total	9 / 12 Passed

Description

75%Weight 40%Scale 1-3

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 well-targeted to a distinct niche with an explicit trigger clause and clear what/when coverage, but its action list is not comprehensive and its trigger terms skew toward technical jargon over natural user phrasing.

Dimension	Reasoning	Score
Specificity	Names the domain ('operating KubeSphere DevOps') and concrete conditions ('namespace-scoped tenant with limited permissions', 'KubeSphere APIs only') but does not enumerate multiple specific concrete operations, matching the 'names domain and some actions, but not comprehensive' anchor.	2 / 3
Completeness	An explicit 'Use when ...' trigger clause plus a clear what-clause ('operating KubeSphere DevOps as a namespace-scoped tenant') answers both what and when with explicit triggers, matching the top anchor.	3 / 3
Trigger Term Quality	Relevant domain terms ('KubeSphere DevOps', 'tenant', 'KubeSphere APIs') are present but lean technical/jargon and lack common natural variations a user would say, matching 'some relevant keywords but missing common variations'.	2 / 3
Distinctiveness Conflict Risk	The narrow tenant-scoped niche ('namespace-scoped tenant', 'without cluster-admin access', 'KubeSphere APIs only') is clearly distinguishable from admin-level skills and unlikely to trigger for the wrong skill.	3 / 3
	Total	10 / 12 Passed

Validation

87%

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 — 14 / 16 Passed

Validation for skill structure

Criteria	Description	Result
skill_md_line_count	SKILL.md is long (1270 lines); consider splitting into references/ and linking	Warning
relative_links	Relative link issues: 4 suspicious	Warning

	Total	14 / 16 Passed

Repository: kubesphere/kubesphere
Path: skills/kubesphere-devops-tenant/SKILL.md
Commit: 04a29b5

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