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
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 extremely minimal and essentially just restates the skill name without providing any meaningful detail about capabilities, use cases, or trigger scenarios. It reads as auto-generated boilerplate rather than a crafted description. It would be very difficult for Claude to reliably select this skill from a pool of available skills.
Suggestions
Add specific concrete actions the skill performs, e.g., 'Installs and configures cert-manager on Kubernetes clusters, creates Certificate and Issuer resources, sets up Let's Encrypt integration, and troubleshoots certificate renewal issues.'
Add an explicit 'Use when...' clause with natural trigger terms, e.g., 'Use when the user needs to set up TLS/SSL certificates in Kubernetes, configure cert-manager, create certificate issuers, or troubleshoot certificate problems.'
Remove the duplicate trigger term ('cert manager setup' is listed twice) and expand with natural variations users would say, such as 'TLS', 'SSL', 'HTTPS', 'Let's Encrypt', 'certificate renewal', 'Kubernetes certificates'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description contains no concrete actions. It only says 'Cert Manager Setup' without describing what specific tasks it performs (e.g., installing cert-manager, configuring issuers, creating certificates, managing TLS). | 1 / 3 |
Completeness | The description fails to answer 'what does this do' beyond the name itself, and the 'when' clause is essentially just the skill name repeated. There is no explicit trigger guidance or use-case description. | 1 / 3 |
Trigger Term Quality | The trigger terms are just 'cert manager setup' repeated twice. It misses natural variations users would say like 'TLS certificates', 'SSL', 'Let's Encrypt', 'certificate issuer', 'HTTPS', 'Kubernetes certificates', or 'cert-manager'. | 1 / 3 |
Distinctiveness Conflict Risk | The term 'cert manager' is somewhat specific to a particular Kubernetes tool, which provides some distinctiveness. However, the lack of detail means it could overlap with general certificate management, SSL setup, or other 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 a hollow placeholder that contains no actual technical content about cert-manager setup. It consists entirely of auto-generated boilerplate describing what the skill would do rather than providing any actionable guidance, commands, code, or configurations. It fails on every dimension of the rubric.
Suggestions
Add concrete, executable steps for installing cert-manager (e.g., `helm install cert-manager jetstack/cert-manager --namespace cert-manager --set installCRDs=true`) and configuring ClusterIssuers with example YAML manifests.
Define a clear multi-step workflow with validation checkpoints: install → verify pods running → create ClusterIssuer → create Certificate → verify certificate issuance with `kubectl get certificate`.
Remove all meta-description sections (Purpose, When to Use, Capabilities, Example Triggers) and replace with actual technical content—commands, YAML examples, and troubleshooting steps.
Add references to supporting files for advanced topics like DNS01 challenge configuration, wildcard certificates, or integration with specific cloud providers.
| 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 cert-manager setup. Every section restates the same vague idea. | 1 / 3 |
Actionability | There are zero concrete instructions, commands, code snippets, or configurations. No Helm install commands, no YAML manifests, no ClusterIssuer examples—nothing actionable for actually setting up cert-manager. | 1 / 3 |
Workflow Clarity | There is no workflow whatsoever. Cert-manager setup is inherently a multi-step process (install, configure issuers, create certificates, validate) and none of these steps are described or sequenced. | 1 / 3 |
Progressive Disclosure | No bundle files exist and no references to external files are provided. The content is a monolithic block of meta-description with no structure that aids navigation or discovery of actual technical content. | 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.