Name: kubesphere-devops-pipeline
Rating: 71.2 (1 reviews)
Author: kubesphere

kubesphere-devops-pipeline

Use when creating, running, or managing CI/CD pipelines in KubeSphere DevOps, including pipeline API operations and run monitoring

Quality

88%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Critical

Do not install without reviewing

Quality

Content

77%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 executable examples and well-sequenced workflows including verification checkpoints, but it suffers from heavy redundancy and a monolithic structure with no progressive disclosure to reference files.

Suggestions

De-duplicate the body: the Common Mistakes table appears twice and multiple 'complete example' sections re-tread the same branch-list→trigger flow — consolidate into one canonical example per workflow.

Split long reference material (deprecated v1alpha2 API tables, full parameter-handling examples, the multi-step end-to-end workflow) into separate reference files linked from a concise SKILL.md overview to improve progressive disclosure.

Collapse the repeated parameter-type tables (Jenkinsfile directive form and API response form) into a single shared table referenced once.

Dimension	Reasoning	Score
Conciseness	The 1295-line body is padded with substantial redundancy — the Common Mistakes table is duplicated, and several 'complete example' sections re-tread the same branch-list→trigger flow and parameter tables — so it could be tightened considerably; not a 1 because the content is specialized KubeSphere knowledge rather than concepts Claude already knows.	2 / 3
Actionability	Provides copy-paste-ready, executable kubectl/curl commands with full URLs, complete YAML manifests, and jq pipelines throughout, matching the fully-executable anchor.	3 / 3
Workflow Clarity	Multi-step flows are explicitly numbered (e.g. private-repo setup Steps 1–4 with a 'Verify Creation' checkpoint, multi-branch workflow Steps 1–6) and include pre-flight validation ('ALWAYS Check for Parameters First') plus a debugging/Common Mistakes feedback path, matching the clear-sequence-with-validation anchor.	3 / 3
Progressive Disclosure	Content is well-sectioned with clear headers but is a single monolithic 1295-line file with everything inline and no references to split files — material that should be separate (complete examples, deprecated v1alpha2 API reference, parameter handling) is inline; not a 1 because organization is decent and no nested references exist.	2 / 3
	Total	10 / 12 Passed

Description

100%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 specific, trigger-rich, complete, and tightly scoped to KubeSphere DevOps pipelines with an explicit 'Use when' clause. It reads as third-person imperative trigger guidance consistent with the good examples.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions — 'creating, running, or managing CI/CD pipelines', 'pipeline API operations', 'run monitoring' — matching the anchor for naming several specific actions rather than vague language.	3 / 3
Completeness	Explicitly answers both what (creating/running/managing pipelines, API operations, run monitoring) and when via the 'Use when...' trigger clause, matching the anchor that requires both with explicit triggers.	3 / 3
Trigger Term Quality	Natural terms a user would say ('CI/CD pipelines', 'KubeSphere DevOps', 'pipeline API', 'run monitoring') give good coverage without relying on jargon, matching the top anchor.	3 / 3
Distinctiveness Conflict Risk	Scoped tightly to 'KubeSphere DevOps' pipelines, a clear niche with distinct triggers unlikely to collide with other skills; not a 2 because it is not merely 'somewhat specific'.	3 / 3
	Total	12 / 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 (1295 lines); consider splitting into references/ and linking	Warning
relative_links	Relative link issues: 1 suspicious	Warning

	Total	14 / 16 Passed

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

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