cert-manager-setup
Cert Manager Setup - Auto-activating skill for DevOps Advanced. Triggers on: cert manager setup, cert manager setup Part of the DevOps Advanced skill category.
36
Quality
3%
Does it follow best practices?
Impact
97%
0.98xAverage 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/cert-manager-setup/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 severely underdeveloped, essentially just restating the skill name without explaining capabilities or use cases. It lacks concrete actions, natural trigger terms, and explicit guidance on when Claude should select this skill. The duplicate trigger term suggests a template that wasn't properly filled out.
Suggestions
Add specific actions the skill performs, e.g., 'Installs and configures Kubernetes cert-manager, creates Certificate resources, sets up ClusterIssuers for Let's Encrypt, troubleshoots certificate renewal issues'
Include a 'Use when...' clause with natural trigger terms: 'Use when setting up SSL/TLS certificates, configuring HTTPS, working with cert-manager CRDs, or troubleshooting certificate errors in Kubernetes'
Add common variations users might say: 'SSL certificates', 'TLS setup', 'HTTPS configuration', 'certificate renewal', 'Let's Encrypt', 'ClusterIssuer', 'Certificate CRD'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description only mentions 'Cert Manager Setup' without describing any concrete actions. It doesn't explain what the skill actually does - no verbs describing capabilities like 'installs', 'configures', 'manages certificates', etc. | 1 / 3 |
Completeness | The description fails to answer 'what does this do' beyond the name, and the 'when' guidance is just a duplicate trigger phrase. There's no explicit 'Use when...' clause explaining scenarios for skill selection. | 1 / 3 |
Trigger Term Quality | The only trigger terms listed are 'cert manager setup' repeated twice. Missing natural variations users might say like 'SSL certificates', 'TLS', 'certificate management', 'HTTPS setup', 'Let's Encrypt', or 'certificate renewal'. | 1 / 3 |
Distinctiveness Conflict Risk | While 'Cert Manager' is somewhat specific to certificate management tooling, the lack of detail about what kind of cert manager (Kubernetes cert-manager? Generic SSL?) and what operations it performs could cause confusion with other security or DevOps 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 essentially an empty placeholder that describes what a cert-manager setup skill should do without providing any actual implementation guidance. It contains no executable commands, no Kubernetes manifests, no Helm values, and no configuration examples. The entire content is meta-description rather than actionable instruction.
Suggestions
Add actual cert-manager installation commands (e.g., `helm install cert-manager jetstack/cert-manager --namespace cert-manager --create-namespace --set installCRDs=true`)
Include concrete YAML examples for ClusterIssuer and Certificate resources with Let's Encrypt configuration
Add a validation workflow: install -> verify pods running -> create test certificate -> verify certificate issued
Remove all meta-descriptions ('This skill provides...', 'Capabilities include...') and replace with actual technical content
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is padded with generic boilerplate that provides no actual value. Phrases like 'provides automated assistance' and 'follows industry best practices' are filler that Claude doesn't need. The entire skill could be replaced with actual cert-manager setup instructions. | 1 / 3 |
Actionability | There is zero concrete guidance - no commands, no code, no configuration examples. The skill describes what it claims to do but provides no actual instructions for setting up cert-manager. Phrases like 'provides step-by-step guidance' without any actual steps are completely non-actionable. | 1 / 3 |
Workflow Clarity | No workflow is defined whatsoever. For a cert-manager setup skill, there should be clear steps for installation, issuer configuration, certificate creation, and validation. Instead, the skill only contains meta-descriptions about itself. | 1 / 3 |
Progressive Disclosure | The content is a monolithic block of self-referential descriptions with no actual content to disclose. There are no references to detailed materials, no links to configuration examples, and no structured navigation to deeper resources. | 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
994edc4
- 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.