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.
Install with Tessl CLI
npx tessl i github:jeremylongshore/claude-code-plugins-plus-skills --skill cert-manager-setupOverall
score
19%
Does it follow best practices?
Validation for skill structure
Activation
7%This description is severely underdeveloped, essentially just restating the skill name without providing any meaningful information about capabilities or usage context. It lacks concrete actions, natural trigger terms, and explicit guidance on when Claude should select this skill. The duplicate trigger term suggests this may be auto-generated boilerplate that was never properly filled in.
Suggestions
Add specific actions the skill performs, e.g., 'Installs and configures cert-manager on Kubernetes clusters, creates Certificate resources, sets up ClusterIssuers for Let's Encrypt, and troubleshoots certificate renewal issues.'
Include natural trigger terms users would say: 'SSL certificates', 'TLS', 'HTTPS', 'Let's Encrypt', 'certificate renewal', 'cert-manager', 'Kubernetes certificates', 'ClusterIssuer'.
Add an explicit 'Use when...' clause: 'Use when the user needs to set up automated certificate management in Kubernetes, configure Let's Encrypt integration, or troubleshoot certificate-related issues.'
| 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 explanation of capabilities or meaningful usage context. | 1 / 3 |
Trigger Term Quality | The trigger terms listed are just 'cert manager setup' repeated twice. Missing natural variations users might say like 'SSL certificates', 'TLS', 'certificate management', 'kubernetes certs', 'cert-manager', or 'HTTPS setup'. | 1 / 3 |
Distinctiveness Conflict Risk | While 'cert manager' is somewhat specific to a particular tool/domain, the lack of detail about what aspects of cert manager it handles (installation, configuration, troubleshooting, renewal) could cause overlap with other DevOps or security-related skills. | 2 / 3 |
Total | 5 / 12 Passed |
Implementation
0%This skill is essentially a placeholder with no actual instructional content. It describes what the skill claims to do but provides zero actionable guidance on cert-manager setup. A DevOps engineer would gain nothing from this content that they couldn't infer from the skill's title alone.
Suggestions
Add concrete installation commands (e.g., `kubectl apply -f` or `helm install cert-manager`) with specific version references
Include example YAML configurations for ClusterIssuer and Certificate resources
Define a clear workflow: 1) Install cert-manager, 2) Create Issuer/ClusterIssuer, 3) Create Certificate, 4) Verify with `kubectl get certificates`
Add validation steps showing how to verify cert-manager is working (checking certificate status, troubleshooting common errors)
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is padded with generic boilerplate that provides no actual value. Phrases like 'Provides step-by-step guidance' and 'Follows industry best practices' are empty filler that Claude doesn't need. | 1 / 3 |
Actionability | There is zero concrete guidance on how to actually set up cert-manager. No commands, no YAML configurations, no kubectl examples, no Helm charts - just vague promises of 'step-by-step guidance' without any actual steps. | 1 / 3 |
Workflow Clarity | No workflow is defined at all. Setting up cert-manager involves multiple steps (installation, issuer configuration, certificate creation, validation) but none are mentioned or sequenced. | 1 / 3 |
Progressive Disclosure | The content is a monolithic block of meta-description with no actual technical content to organize. There are no references to detailed guides, no links to configuration examples, and no structured navigation. | 1 / 3 |
Total | 4 / 12 Passed |
Validation
69%Validation — 11 / 16 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
description_trigger_hint | Description may be missing an explicit 'when to use' trigger hint (e.g., 'Use when...') | Warning |
allowed_tools_field | 'allowed-tools' contains unusual tool name(s) | Warning |
metadata_version | 'metadata' field is not a dictionary | Warning |
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
body_steps | No step-by-step structure detected (no ordered list); consider adding a simple workflow | Warning |
Total | 11 / 16 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.