k8s-manifest-generator
Create production-ready Kubernetes manifests for Deployments, Services, ConfigMaps, and Secrets following best practices and security standards. Use when generating Kubernetes YAML manifests, creating K8s resources, or implementing production-grade Kubernetes configurations.
Install with Tessl CLI
npx tessl i github:wshobson/agents --skill k8s-manifest-generator79
Does it follow best practices?
If you maintain this skill, you can automatically optimize it using the tessl CLI to improve its score:
npx tessl skill review --optimize ./path/to/skillValidation for skill structure
Discovery
100%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 well-crafted skill description that excels across all dimensions. It provides specific capabilities (manifest types), uses natural trigger terms including the common 'K8s' abbreviation, explicitly states when to use it, and carves out a distinct niche for Kubernetes manifest generation.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'Create production-ready Kubernetes manifests for Deployments, Services, ConfigMaps, and Secrets' with qualifiers 'following best practices and security standards'. | 3 / 3 |
Completeness | Clearly answers both what ('Create production-ready Kubernetes manifests for Deployments, Services, ConfigMaps, and Secrets') and when ('Use when generating Kubernetes YAML manifests, creating K8s resources, or implementing production-grade Kubernetes configurations'). | 3 / 3 |
Trigger Term Quality | Includes natural keywords users would say: 'Kubernetes manifests', 'K8s resources', 'Kubernetes YAML manifests', 'Kubernetes configurations', plus specific resource types (Deployments, Services, ConfigMaps, Secrets). | 3 / 3 |
Distinctiveness Conflict Risk | Clear niche focused specifically on Kubernetes manifest generation with distinct triggers like 'K8s', 'Kubernetes YAML', and specific resource types; unlikely to conflict with general infrastructure or other container skills. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
50%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill provides excellent, production-ready Kubernetes manifest examples with strong actionability, but suffers from severe verbosity that wastes context window space on concepts Claude already understands. The workflow is well-structured but validation comes too late in the process. The content would benefit significantly from aggressive trimming and better separation of reference material.
Suggestions
Remove explanatory content Claude already knows (what ConfigMaps are, why labels matter, basic K8s concepts) - keep only the templates and specific patterns
Move validation steps earlier in the workflow with explicit 'validate before proceeding' checkpoints after creating each resource type
Extract 'Common Patterns', 'Troubleshooting', and 'Best Practices Summary' to separate reference files, keeping SKILL.md as a lean quick-start guide
Consolidate the 'Questions to ask' and 'Gather Requirements' sections into a brief checklist rather than prose explanations
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Extremely verbose with extensive explanations Claude already knows (what ConfigMaps are for, what labels do, basic Kubernetes concepts). The 'Questions to ask' section, 'Best Practices Summary', and 'Troubleshooting' sections add significant token overhead without providing actionable value Claude doesn't already possess. | 1 / 3 |
Actionability | Provides fully executable YAML manifests that are copy-paste ready with clear placeholders. The code examples are complete and production-ready, covering Deployments, Services, ConfigMaps, Secrets, and PVCs with proper structure. | 3 / 3 |
Workflow Clarity | Steps are clearly numbered and sequenced, but validation is relegated to step 10 at the end rather than integrated throughout. For manifest generation involving security contexts and secrets, validation should occur earlier and more frequently. The checklist format is good but lacks explicit feedback loops. | 2 / 3 |
Progressive Disclosure | References external files (references/deployment-spec.md, assets/configmap-template.yaml) appropriately, but the main document is a monolithic wall of text that could benefit from splitting. The 'Common Patterns' and 'Templates' sections could be separate files, with SKILL.md serving as a leaner overview. | 2 / 3 |
Total | 8 / 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 |
|---|---|---|
skill_md_line_count | SKILL.md is long (535 lines); consider splitting into references/ and linking | Warning |
Total | 10 / 11 Passed | |
- 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.