CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

kubernetes-patterns

Kubernetes workload patterns, resource management, RBAC, probes, autoscaling, ConfigMap/Secret handling, and kubectl debugging for production-grade deployments. Use when writing or reviewing Kubernetes manifests, or debugging probes, RBAC, autoscaling, resource limits, or pods that keep getting evicted.

Quality

82%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Quality

Content

71%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

Excellent actionability — executable, production-grade YAML and kubectl commands throughout with strong diagnostic decision tables — undermined by a monolithic structure and token waste. The body needs no conceptual explanations removed, but it should be split into reference files with SKILL.md as an overview, and the duplicated 'When to Use' alias section should be deleted.

Suggestions

Split the detailed pattern sections (Deployment template, RBAC chains, kubectl cheatsheet, anti-patterns) into files under references/ and keep SKILL.md as a concise overview with one-level-deep, clearly signaled links — this addresses the monolithic structure that keeps progressive_disclosure at 3.

Delete the 'When to Use' section that duplicates 'When to Activate' ('This alias satisfies repo skill-format conventions' is meta-commentary that wastes tokens); keep a single activation section.

Trim the Anti-Patterns section's repetition of resource and securityContext YAML already shown in full earlier, referencing the earlier sections instead and keeping only the BAD/GOOD contrasts not previously covered.

DimensionReasoningScore

Conciseness

The body is mostly dense, high-value patterns without basic-concept padding, but at ~790 lines it carries clear waste: the 'When to Use' section duplicates 'When to Activate' and even admits "This alias satisfies repo skill-format conventions", and the Anti-Patterns section repeats resource/security-context YAML already shown in full earlier. The material could be tightened considerably, matching the 'mostly efficient but some unnecessary content' anchor rather than the lean 4-5 anchors.

3 / 5

Actionability

Everything is copy-paste ready: a complete production Deployment YAML, correct probe configurations with failureThreshold × periodSeconds math, full RBAC chains, HPA/PDB/Job/CronJob specs, and concrete kubectl commands including audit-log queries for eviction triage. The 'WRONG/BAD' examples with corrected counterparts cover the common failure cases, fully matching the top anchor.

5 / 5

Workflow Clarity

The debugging sections give clear sequences with confirmation checkpoints — the churn triage table pairs each signal with a 'Confirm with' action (audit log, kubectl get nodes), and the error-diagnosis section maps symptom to cause to command. It falls short of 5 because there are no explicit validate-fix-retry feedback loops, though for a reference/patterns skill (no destructive batch workflow) this is a minor gap rather than a disqualifying one.

4 / 5

Progressive Disclosure

The file has good internal structure — a task-to-section jump table, clear section headers, and consistent organization — but it is a ~790-line monolith with no bundle files at all: the kubectl cheatsheet, the full pattern library, and the checklists are all inlined in SKILL.md when they clearly belong in separate reference files per the overview-plus-references model. Structure exists, but content that should be separate is fully inline, sitting between the 2 and 3 anchors; the decent navigation pulls it to 3.

3 / 5

Total

15

/

20

Passed

Description

87%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A strong description: it names a specific domain, enumerates concrete capability areas, and pairs them with an explicit 'Use when' clause containing natural trigger phrases. The main improvement opportunity is stating capabilities as actions rather than noun-phrase topic labels.

DimensionReasoningScore

Specificity

The description lists several specific capability areas — "Kubernetes workload patterns, resource management, RBAC, probes, autoscaling, ConfigMap/Secret handling, and kubectl debugging" — giving concrete coverage of the domain. It falls short of a 5 because capabilities are phrased as noun phrases rather than concrete actions (no verbs like 'write', 'configure', 'debug'), leaving the actions implied rather than stated.

4 / 5

Completeness

It clearly answers both 'what' (the enumerated capability areas for production-grade deployments) and 'when' with an explicit "Use when writing or reviewing Kubernetes manifests, or debugging probes, RBAC, autoscaling, resource limits, or pods that keep getting evicted" clause containing concrete trigger phrases. Both halves are explicit, matching the top anchor; a 4 would require the 'when' to be less specific, which it is not.

5 / 5

Trigger Term Quality

Triggers like "Kubernetes manifests", "probes", "RBAC", "autoscaling", "resource limits", and "pods that keep getting evicted" are natural phrases a user would say when needing this skill. A few common variations are missing from the description (e.g. 'K8s', 'YAML', 'CrashLoopBackOff', 'Helm'), keeping it below a 5.

4 / 5

Distinctiveness Conflict Risk

"Kubernetes" is a clear niche with distinct, well-scoped triggers (manifests, kubectl, probes, RBAC, autoscaling, evictions), giving minimal conflict risk with unrelated skills. The only conceivable overlap is with adjacent deployment/docker skills, but the Kubernetes-specific triggers clearly disambiguate.

5 / 5

Total

18

/

20

Passed

Validation

87%

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

CriteriaDescriptionResult

skill_md_line_count

SKILL.md is long (793 lines); consider splitting into references/ and linking

Warning

metadata_version

'metadata.version' is missing

Warning

Total

14

/

16

Passed

Repository

affaan-m/ECC

Path

skills/kubernetes-patterns/SKILL.md

Reviewed

Table of Contents

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.