kubernetes-manifests
Generate Kubernetes manifests for Deployments, Services, Ingress, ConfigMaps, Secrets, HPA, PVCs with kustomize overlay structure, health probes, and resource limits.
84
81%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Passed
No known issues
Quality
Discovery
82%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This is a strong description with excellent specificity and trigger term coverage for Kubernetes practitioners. The main weakness is the absence of an explicit 'Use when...' clause, which would help Claude know exactly when to select this skill over others. The technical depth is appropriate for the domain.
Suggestions
Add a 'Use when...' clause with trigger phrases like 'Use when the user asks to create Kubernetes manifests, deploy to K8s, or mentions YAML for container orchestration.'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions and artifacts: 'Deployments, Services, Ingress, ConfigMaps, Secrets, HPA, PVCs with kustomize overlay structure, health probes, and resource limits' - this is highly specific about what it generates. | 3 / 3 |
Completeness | Clearly answers 'what' (generate various K8s manifests with specific features) but lacks an explicit 'Use when...' clause or equivalent trigger guidance explaining when Claude should select this skill. | 2 / 3 |
Trigger Term Quality | Excellent coverage of natural Kubernetes terms users would say: 'Kubernetes manifests', 'Deployments', 'Services', 'Ingress', 'ConfigMaps', 'Secrets', 'HPA', 'PVCs', 'kustomize', 'health probes', 'resource limits' - these are all terms practitioners naturally use. | 3 / 3 |
Distinctiveness Conflict Risk | Very clear niche focused specifically on Kubernetes manifest generation with distinct triggers like 'kustomize', 'HPA', 'PVCs' that are unlikely to conflict with other skills. | 3 / 3 |
Total | 11 / 12 Passed |
Implementation
79%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a high-quality, actionable skill with comprehensive, production-ready Kubernetes manifests covering the full kustomize overlay pattern. The content is concise and assumes appropriate knowledge. However, it lacks explicit validation workflows (e.g., 'validate YAML syntax before apply', 'check rollout status and rollback if failed') and could benefit from better progressive disclosure by moving detailed manifests to reference files.
Suggestions
Add a validation workflow section with explicit steps: validate YAML syntax → dry-run apply → diff → apply → verify rollout status → rollback on failure
Consider moving detailed manifest examples to a separate MANIFESTS.md reference file, keeping SKILL.md as a concise overview with the scaffold command and key conventions
Add error recovery guidance: what to do when rollout fails, how to debug CrashLoopBackOff, how to rollback a bad deployment
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is lean and efficient, providing only necessary information without explaining basic Kubernetes concepts Claude already knows. Every section serves a clear purpose with no padding or unnecessary context. | 3 / 3 |
Actionability | Provides fully executable, copy-paste ready YAML manifests and bash commands. All examples are complete with proper API versions, metadata, and specs that can be directly applied to a cluster. | 3 / 3 |
Workflow Clarity | While the structure is clear and commands are well-organized, there are no explicit validation checkpoints or feedback loops for error recovery. The 'Common Commands' section lists operations but doesn't sequence them with validation steps (e.g., validate manifests before apply, check for errors after apply). | 2 / 3 |
Progressive Disclosure | Content is well-organized with clear sections, but it's a monolithic document with all manifests inline. The Integration Notes reference other skills but the main content could benefit from splitting detailed manifests into separate reference files while keeping SKILL.md as an overview. | 2 / 3 |
Total | 10 / 12 Passed |
Validation
90%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 10 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 10 / 11 Passed | |
- Repository
- achreftlili/deep-dev-skills
- Commit
181fcbc
- 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.