Nodegroup

94TrustedShips scripts

Resource management and configuration for the Edgewize NodeGroup project.

What it does

Installing this skill allows your assistant to interface directly with Edgewize NodeGroup resources. It enables the assistant to list, inspect, and modify infrastructure components through authenticated API calls rather than relying solely on generic command-line tools.

By prioritizing direct API communication, the assistant can verify current cluster states, perform targeted patches, and manage complex bindings across nodes, namespaces, and workspaces with higher precision. It ensures configuration changes are applied according to the underlying project architecture.

When it earns its place

Reach for it when…

Apply this skill when you need to automate lifecycle tasks for NodeGroups, such as creating new groups, updating descriptions, or managing associations between specific nodes and their host namespaces or workspaces within an Edgewize environment.

Look elsewhere when…

Do not use this for general Kubernetes cluster administration that falls outside the scope of NodeGroup resources. If you are troubleshooting underlying network policies or standard pod scheduling issues unrelated to NodeGroup configuration, native kubectl commands or dedicated diagnostic skills are more appropriate.

What to say to use it

You never invoke a skill directly — the assistant picks it up when your request matches what it covers. These are the kinds of things that do that.

list all current nodegroup configurations
bind these specific nodes to the production nodegroup
create a new nodegroup with the following description
check the status of the edge-cluster nodegroup

Install it

Install for all your projects

Copy the skill directory into your personal skills folder. Claude picks it up on its own the next time your request matches what it does — there is nothing to enable.

bash

git clone --depth 1 --branch master https://github.com/kubesphere/kubesphere.git /tmp/kubesphere
mkdir -p ~/.claude/skills
cp -r /tmp/kubesphere/skills/nodegroup ~/.claude/skills/nodegroup

Install for one project only

Put it in the project's own skills folder instead, so it can be committed and shared with everyone working on that repository.

bash

cp -r /tmp/kubesphere/skills/nodegroup .claude/skills/nodegroup

If a skill of the same name exists in both places, the personal one wins.

Installing on Claude.ai or through the API instead? The full guide covers every surface.

94/100Trusted source

What checks out

Original source. Published in the repository of whoever wrote it, rather than copied out of it into a collection.
Adoption. The host repository has 17,028 stars. This counts the whole repository, not this skill alone.
Official author. Published by the organisation that owns the subject it covers.
Recently maintained. The repository was updated 35 days ago.
Spec-compliant. Frontmatter matches the Agent Skills specification, so it loads in any client implementing it.
Substantive instructions. The body carries enough detail to change how a task is actually performed.

What to know

Licensed. A licence is referenced but not in a standard form, so the exact terms have to be read in the repository.

This score describes where the skill came from — its origin, licence, upkeep and conformance to the spec. It is not a security audit, and it says nothing about whether the skill's instructions are correct. How it is calculated.

What it ships

Executable files: 1 Python file that can run on your machine
Files in total: 2
Context cost: about 1,931 tokens once activated (estimated)

Bundled scripts are normal — most skills from established authors include them. We have not run or reviewed this code; read it before installing if that matters to you.

Source

Published in: kubesphere/kubesphere
Path in repository: skills/nodegroup/SKILL.md
Licence: Not stated in a standard form

New to skills? Start here →