SKILLEMALL.ai
GitHub ↗ RU Sign in

BB kube-medic

Kubernetes Cluster Triage & Diagnostics — instant AI-powered incident triage via kubectl

modbender/skill-library-mcp Agent Skills author: modbender MIT 6 files · 1 script body ≈ 2 209 tokens Open the sourcegithub.com↗ analyzed 3 d ago

Kubernetes Cluster Triage & Diagnostics — instant AI-powered incident triage via kubectl

As a process B 75/100 · Nearly there — weak spots: inputs and preconditions, running it twice

AnalyzerKubernetesDiscordInfrastructuretype and topics are labelled automatically from the skill text
Runs in: OpenClaw Claude / Claude Code ChatGPT / Codex Gemini CLI Cursor GitHub Copilot / VS Code Qwen Code Kimi Code CLI Z.ai (GLM) DeepSeek (Deep Code) Mistral Vibe LangChain (deepagents) Goose OpenCode
JSON
Technical rating
B
87/100
safety, quality, tests
Safety 60%
100
Quality 40%
68
Run on models
none yet
Process rating
B
75/100
Nearly there
Inputs and preconditions w 11
0
Running it twice w 4
30
Result and completion w 14
60
the three weakest of ten parameters · all ten

How to improve

  1. Say in the description WHEN to use the skill ("use when…", example requests): that is the agent's main cue.
For the model run — optional
  • Your own cases (evals/evals.json, 4–6 real requests with expected answers): the full check would then run those instead of a model-drafted suite.
  • A spec.yaml with trigger phrases and assertions — a behaviour contract for CI; `skilltest init` writes a template.

Guard findings · 0

✓ No critical or high findings

Files scanned: 6. Evidence is masked. Grey chips explain why severity was lowered.

Against the Agent Skills spec

  • warning description-no-when description does not say WHEN to use the skill (no "use when")
  • note frontmatter-key unknown frontmatter key "tools"
  • note frontmatter-key unknown frontmatter key "dependencies"

Process rating: all ten parameters 75/100

  • 0Inputs and preconditions. Does not say what the process needs to start
  • 30Running it twice. 18 mutating operations with no state check
  • 60Result and completion. Output format stated, no completion criterion
  • 70When it triggers. States when to use, but not when not to
  • 85Steps. 48 steps, 2 vague phrases
  • 100Tools and files. Tools declared in frontmatter
  • 100Failures and branches. 1 branches, has a failure section
  • 100Consistency. Name and required fields are in place
  • 100Execution cost. Instruction body is 2209 tokens
  • 100Progress reporting. Reports progress

Everything here is measured from the skill text rather than judged by a model, so the numbers are checkable. A parameter weighs more when it is a more common reason for the process to stall.

Quality signals

  • +5Description has no quoted example phrases that should trigger the skill
  • +4Description does not say when NOT to use the skill (false activations)
  • +3Description length 88: 120–800 characters recommended
  • -31 of 1 scripts are never mentioned in SKILL.md
  • +2Single-language instructions
  • +4Structure: 15 headings
  • +3Step-by-step instructions: 48 items
  • +3Output format is stated explicitly
  • +4Has examples (8 code blocks)
  • +1License stated

Quality base 70; lint remarks subtract, signals add up to 100. Result: 68.