Certificate Lifecycle Manager - Auto-activating skill for Security Advanced. Triggers on: certificate lifecycle manager, certificate lifecycle manager Part of the Security Advanced skill category.
Install with Tessl CLI
npx tessl i github:jeremylongshore/claude-code-plugins-plus-skills --skill certificate-lifecycle-managerOverall
score
19%
Does it follow best practices?
Validation for skill structure
Activation
7%This description is severely lacking in all key areas. It functions as a placeholder rather than a useful skill description, providing only the skill name and category without any explanation of capabilities, use cases, or natural trigger terms. Claude would have no meaningful basis for selecting this skill appropriately.
Suggestions
Add specific actions the skill performs, such as 'Monitors certificate expiration dates, automates renewal workflows, issues new certificates, and revokes compromised certificates.'
Include a 'Use when...' clause with natural trigger terms like 'Use when the user mentions SSL/TLS certificates, cert expiration, certificate renewal, PKI management, or needs to check certificate status.'
Add common user terminology variations: 'SSL certs', 'TLS certificates', 'expired certificate', 'certificate authority', 'PKI', '.pem files', 'certificate chain'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description contains no concrete actions whatsoever. It only names the tool ('Certificate Lifecycle Manager') without explaining what it actually does - no verbs describing capabilities like 'renew', 'monitor', 'issue', or 'revoke' certificates. | 1 / 3 |
Completeness | The description fails to answer both 'what does this do' and 'when should Claude use it'. There is no 'Use when...' clause and no explanation of the skill's functionality beyond its name. | 1 / 3 |
Trigger Term Quality | The only trigger terms listed are 'certificate lifecycle manager' repeated twice. Missing natural user terms like 'SSL', 'TLS', 'cert expiration', 'renew certificate', 'certificate renewal', or 'expired cert'. | 1 / 3 |
Distinctiveness Conflict Risk | The term 'Certificate Lifecycle Manager' is somewhat specific to certificate management, but without concrete actions, it could overlap with other security or certificate-related skills. The category mention 'Security Advanced' provides minimal differentiation. | 2 / 3 |
Total | 5 / 12 Passed |
Implementation
0%This skill content is an empty template that provides no actual value. It contains only generic placeholder text describing what a skill should do rather than providing any concrete guidance on certificate lifecycle management. The content fails on all dimensions as it lacks any actionable instructions, code examples, workflows, or references to actual certificate management tasks.
Suggestions
Add concrete code examples for common certificate operations (generating CSRs, checking expiration, automating renewal with tools like certbot or openssl)
Define a clear workflow for certificate lifecycle stages: generation → deployment → monitoring → renewal → revocation, with validation steps at each stage
Include specific commands and scripts for certificate management tasks (e.g., openssl commands, ACME protocol usage, certificate store management)
Reference or link to detailed documentation for specific certificate types (TLS/SSL, code signing, client certificates) and platforms (Kubernetes, cloud providers, internal PKI)
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is padded with generic boilerplate that provides no actual information about certificate lifecycle management. Phrases like 'provides automated assistance' and 'follows industry best practices' are meaningless filler that waste tokens. | 1 / 3 |
Actionability | There is zero concrete guidance - no code, no commands, no specific steps, no actual certificate management procedures. The content only describes what the skill claims to do without providing any executable instructions. | 1 / 3 |
Workflow Clarity | No workflow is defined at all. Certificate lifecycle management involves complex multi-step processes (generation, renewal, revocation, monitoring) but none are documented. No validation checkpoints or sequences are provided. | 1 / 3 |
Progressive Disclosure | The content is a shallow placeholder with no actual substance to organize. There are no references to detailed documentation, no links to examples, and no structured navigation to deeper content. | 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 | |
Table of Contents
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.