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, or resource limits.

Quality

84%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

High

Do not use without reviewing

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.

The body is an excellent copy-paste reference with complete manifests, commands, and anti-patterns, but it is monolithic: everything is inlined in one large file with duplicated boilerplate sections. Trimming the redundant sections and splitting the cheatsheet and detailed patterns into reference files would meaningfully improve token efficiency and progressive disclosure.

Suggestions

Remove the duplicate 'When to Use' alias section and the 10-item 'How It Works' list, which restate the 'When to Activate' bullets and the Examples jump table.

Split the kubectl debugging cheatsheet and the full pattern YAML (Deployment, Ingress, RBAC chain) into references/ files, keeping SKILL.md as a concise overview with clearly signaled one-level-deep links.

Deduplicate the probe and resource YAML that appears in both the Deployment template and the dedicated Probes / Resources sections — reference the section once instead of repeating the blocks.

DimensionReasoningScore

Conciseness

Mostly concrete but padded with duplication: 'When to Activate' and 'When to Use' repeat the same list, the 10-item 'How It Works' list restates the jump table and section headings, and probe/resource YAML blocks appear multiple times across sections. This goes beyond the 'minor instances that could be trimmed' of the level above.

3 / 5

Actionability

Fully executable, copy-paste-ready YAML manifests and kubectl commands cover the common cases (deployment, probes, ingress, secrets, RBAC, HPA, debugging), supplemented by decision tables and rules-of-thumb — matching the top anchor.

5 / 5

Workflow Clarity

Diagnostic sequences are present ('CrashLoopBackOff → logs --previous → describe for exit code/OOMKilled') and validation exists via '--dry-run=server', but there are no explicit validate→fix→retry feedback loops, keeping it below the top anchor.

4 / 5

Progressive Disclosure

No bundle files exist, so all ~750 lines — including the kubectl cheatsheet and full pattern YAML that clearly belong in separate reference files — are inlined in SKILL.md. Internal structure and the jump-table navigation are good, but content that should be separate is inline, matching this anchor.

3 / 5

Total

15

/

20

Passed

Description

92%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 concrete capabilities across the Kubernetes domain and pairs them with an explicit 'Use when' trigger clause covering both authoring/review and debugging. The only gap is missing common synonyms like 'k8s' and 'YAML' in the trigger terms.

DimensionReasoningScore

Specificity

Lists multiple concrete capabilities — 'workload patterns, resource management, RBAC, probes, autoscaling, ConfigMap/Secret handling, and kubectl debugging' — giving comprehensive coverage of the Kubernetes domain with no notable gaps.

5 / 5

Completeness

Explicitly answers both 'what' (the capability list) and 'when' ('Use when writing or reviewing Kubernetes manifests, or debugging probes, RBAC, autoscaling, or resource limits') with concrete trigger phrases, matching the top anchor.

5 / 5

Trigger Term Quality

Good natural keywords ('Kubernetes manifests', 'RBAC', 'probes', 'autoscaling', 'resource limits'), but common user variations like 'k8s', 'YAML', and 'kubectl' are missing from the trigger clause.

4 / 5

Distinctiveness Conflict Risk

Occupies a clear Kubernetes niche with unambiguous triggers (RBAC, probes, autoscaling); these terms are K8s-specific and unlikely to fire adjacent skills like CI/CD or Docker skills.

5 / 5

Total

19

/

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 (757 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.