kubernetes-secrets-manager
Kubernetes Secrets Manager - Auto-activating skill for DevOps Advanced. Triggers on: kubernetes secrets manager, kubernetes secrets manager Part of the DevOps Advanced skill category.
36
3%
Does it follow best practices?
Impact
99%
1.02xAverage score across 3 eval scenarios
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./planned-skills/generated/02-devops-advanced/kubernetes-secrets-manager/SKILL.mdQuality
Discovery
7%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 description is essentially a boilerplate auto-generated stub with no substantive content. It fails to describe any concrete capabilities, lacks natural trigger terms users would employ, and provides no guidance on when Claude should select this skill. It would be nearly useless for skill selection among a large pool of available skills.
Suggestions
Add concrete actions the skill performs, e.g., 'Creates, rotates, and manages Kubernetes secrets, configures sealed secrets, and handles secret encryption/decryption in k8s clusters.'
Add an explicit 'Use when...' clause with natural trigger terms, e.g., 'Use when the user asks about k8s secrets, secret rotation, sealed secrets, kubectl create secret, base64 encoding for secrets, or Kubernetes secret management.'
Remove the duplicate trigger term and expand coverage to include common variations like 'k8s secrets', 'secret yaml', 'opaque secret', 'TLS secret', 'secret store CSI driver'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description contains no concrete actions whatsoever. It only states the skill name and category ('Kubernetes Secrets Manager', 'DevOps Advanced') without describing what it actually does—no verbs like 'create', 'rotate', 'encrypt', 'manage', or any specific capabilities. | 1 / 3 |
Completeness | The description fails to answer both 'what does this do' and 'when should Claude use it'. There is no explanation of capabilities and no explicit 'Use when...' clause—only a mechanical 'Triggers on' statement that doesn't serve as meaningful guidance. | 1 / 3 |
Trigger Term Quality | The only trigger term listed is 'kubernetes secrets manager' repeated twice. It misses natural variations users would say such as 'k8s secrets', 'secret rotation', 'sealed secrets', 'encrypt secrets', 'kubectl secret', 'secret management', etc. | 1 / 3 |
Distinctiveness Conflict Risk | The mention of 'Kubernetes Secrets Manager' does narrow the domain somewhat, distinguishing it from generic DevOps or general secrets management skills. However, without specific actions or clear triggers, it could still overlap with broader Kubernetes or secrets-related skills. | 2 / 3 |
Total | 5 / 12 Passed |
Implementation
0%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill is an empty placeholder that contains no actual technical content about Kubernetes secrets management. It consists entirely of meta-descriptions and trigger phrases, offering no actionable guidance, code examples, commands, or workflows. It would provide no value to Claude when attempting to help a user with Kubernetes secrets.
Suggestions
Add concrete, executable examples such as `kubectl create secret`, YAML manifests for Kubernetes Secret objects, and commands for integrating with external secrets managers (e.g., AWS Secrets Manager, HashiCorp Vault).
Define a clear workflow with validation steps, e.g.: 1) Create secret → 2) Verify with `kubectl get secret` → 3) Mount in pod → 4) Validate pod can access secret.
Include specific best practices content such as encryption at rest configuration, RBAC policies for secrets access, secret rotation strategies, and sealed-secrets or external-secrets-operator patterns.
Remove all meta-description sections ('Purpose', 'When to Use', 'Example Triggers') that describe the skill abstractly and replace them with actual technical content.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is entirely filler and meta-description. It explains what the skill does in abstract terms without providing any actual technical content about Kubernetes secrets management. Every section restates the same vague information. | 1 / 3 |
Actionability | There is zero concrete guidance—no commands, no code, no configuration examples, no specific steps for managing Kubernetes secrets. Phrases like 'Provides step-by-step guidance' and 'Generates production-ready code' describe capabilities without demonstrating any. | 1 / 3 |
Workflow Clarity | No workflow is defined at all. There are no steps, no sequences, no validation checkpoints. The skill merely claims it provides 'step-by-step guidance' without actually containing any steps. | 1 / 3 |
Progressive Disclosure | There are no references to supporting files, no links to detailed guides, and no structured navigation. The content is a shallow, monolithic placeholder with no depth or organization beyond boilerplate headings. | 1 / 3 |
Total | 4 / 12 Passed |
Validation
81%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 9 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
allowed_tools_field | 'allowed-tools' contains unusual tool name(s) | Warning |
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 9 / 11 Passed | |
- Commit
13d35b8
- 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.