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 useful information about what the skill does or when it should be selected. It lacks concrete actions, meaningful trigger terms, and explicit usage guidance, making it nearly useless for skill selection among a large set 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 manages TLS certificate lifecycle.'
Add an explicit 'Use when...' clause with natural trigger terms, e.g., 'Use when the user needs to set up cert-manager, configure TLS/SSL certificates in Kubernetes, create certificate issuers, or integrate Let's Encrypt with their cluster.'
Remove the duplicate trigger term ('cert manager setup' is listed twice) and expand with natural variations users would say like 'TLS certificates', 'SSL setup', 'HTTPS', 'Let's Encrypt', 'Kubernetes certificates', 'cert-manager installation'.
| 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 'Use when...' guidance with meaningful triggers. | 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 DevOps, Kubernetes, or TLS/SSL-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 template that contains no actual technical content about cert-manager setup. It only describes what the skill would do in abstract terms without providing any actionable guidance, commands, configurations, or examples. It fails on every dimension because it teaches nothing.
Suggestions
Add concrete, executable steps for installing cert-manager (e.g., `helm install cert-manager jetstack/cert-manager --namespace cert-manager --create-namespace --set installCRDs=true`) with validation commands like `kubectl get pods -n cert-manager`.
Include example ClusterIssuer and Certificate YAML manifests for common use cases (Let's Encrypt staging/production, self-signed).
Add a clear workflow with validation checkpoints: install → verify pods running → create issuer → verify issuer ready → create certificate → verify certificate issued.
Remove all meta-description sections (Purpose, When to Use, Capabilities, Example Triggers) and replace with actual technical content that Claude can use to help users.
| 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 describes the skill rather than teaching anything. | 1 / 3 |
Actionability | There are zero concrete commands, code snippets, configuration examples, or specific steps for setting up cert-manager. The content is entirely vague descriptions like 'Provides step-by-step guidance' without actually providing any. | 1 / 3 |
Workflow Clarity | No workflow is defined at all. There are no steps, no sequence, no validation checkpoints. The skill claims to provide 'step-by-step guidance' but contains none. | 1 / 3 |
Progressive Disclosure | The content has section headers but they contain no useful information. There are no references to detailed files, no examples, and no structured content to navigate. It's a shell with no substance. | 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
c8a915c
- 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.