agentleFS
Sign inStart free
cloudfleetaicloudfleetai/cloudfleet-plugin-claude/skills/cluster-info/SKILL.md

cluster-info

Skill0 starsChanged 10 days agoApache-2.0View on GitHub

This skill should be used when the user asks to "list clusters", "show clusters", "cluster status", "what clusters do I have", or wants a Cloudfleet cluster overview.

The file

We split this skill into the rules it gives an agent

6 rules. About 0 are common, 3 are distinctive, and 3 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈3

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 3

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    If the user specifies a --profile, pass it to all cloudfleet CLI commands.

    line 15
  2. Distinctive:

    If the user named a specific cluster (by name or ID):

    line 23
  3. Very specific:

    Add --profile <name> if the user specified one.

    line 35
  4. Very specific:

    If a cluster has issues → offer to debug with /cloudfleet:debug-cluster

    line 52
  5. Distinctive:

    If the user wants to query resources → offer to help with kubectl commands

    line 53
  6. Distinctive:

    If they need to scale → point to fleet configuration

    line 54

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Cluster Info

Retrieve and display information about your Cloudfleet clusters.

Important Notes

  • kubectl is a separate tool from the Cloudfleet CLI — there is no cloudfleet kubectl command.
  • If the user specifies a --profile, pass it to all cloudfleet CLI commands.
  • Pass -o json to cloudfleet commands. The default auto already emits JSON when piped, but a per-profile default or CLOUDFLEET_OUTPUT_FORMAT can override it to table.
  • Narrow large results with -q (JMESPath), e.g. cloudfleet clusters list -q "[].{id:id,name:name,status:status}".

Execution Steps

1. List or fetch clusters

If the user named a specific cluster (by name or ID):

cloudfleet clusters describe <cluster-id>

Otherwise, list all clusters:

cloudfleet clusters list

Add --profile <name> if the user specified one.

2. Present information

Display the results in a clear table format including:

  • Cluster name and ID
  • Kubernetes version
  • Cloud provider and region
  • Node count
  • Status (creating, deployed, updating, or disabled)
  • Tier

3. Offer next steps

Based on the cluster status, suggest relevant actions:

  • If a cluster has issues → offer to debug with /cloudfleet:debug-cluster
  • If the user wants to query resources → offer to help with kubectl commands
  • If they need to scale → point to fleet configuration

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free