Https Certificate Checker - Auto-activating skill for Security Fundamentals. Triggers on: https certificate checker, https certificate checker Part of the Security Fundamentals skill category.
Install with Tessl CLI
npx tessl i github:jeremylongshore/claude-code-plugins-plus-skills --skill https-certificate-checkerOverall
score
19%
Does it follow best practices?
Validation for skill structure
Activation
7%This description is essentially a placeholder that provides almost no useful information for skill selection. It lacks any concrete actions, meaningful trigger terms, or guidance on when to use it. The only distinguishing element is the domain reference to HTTPS certificates, but even this is not elaborated upon.
Suggestions
Add specific actions the skill performs, e.g., 'Validates HTTPS certificates, checks expiration dates, diagnoses SSL/TLS connection issues, and verifies certificate chains.'
Include a 'Use when...' clause with natural trigger terms: 'Use when the user mentions SSL certificates, certificate errors, HTTPS issues, cert expiration, TLS problems, or secure connection failures.'
Add common user phrases and file/protocol references like '.pem files', 'certificate authority', 'self-signed cert', 'certificate warning' to improve trigger term coverage.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description only names the skill 'Https Certificate Checker' without describing any concrete actions. There are no verbs indicating what the skill actually does (e.g., validate, inspect, diagnose, check expiration). | 1 / 3 |
Completeness | The description fails to answer 'what does this do' beyond the name, and provides no 'when should Claude use it' guidance. The 'Triggers on' section just repeats the skill name rather than providing meaningful trigger scenarios. | 1 / 3 |
Trigger Term Quality | The trigger terms listed are just the skill name repeated twice ('https certificate checker'). Missing natural user phrases like 'SSL certificate', 'cert expired', 'TLS', 'certificate validation', 'secure connection', or 'certificate error'. | 1 / 3 |
Distinctiveness Conflict Risk | The term 'certificate checker' is somewhat specific to HTTPS/SSL domain, which provides some distinctiveness. However, without concrete actions described, it could overlap with other security-related skills. | 2 / 3 |
Total | 5 / 12 Passed |
Implementation
0%This skill is entirely meta-content describing what the skill supposedly does, without any actual instructional content. It contains zero actionable guidance on HTTPS certificate checking - no code examples, no commands (like openssl or curl), no explanation of what to check for (expiration, chain validity, cipher suites), and no workflow for diagnosing certificate issues.
Suggestions
Add executable code examples showing how to check certificates (e.g., `openssl s_client -connect example.com:443` or Python ssl module usage)
Include a concrete checklist of what to verify: expiration date, certificate chain, hostname matching, revocation status
Provide specific commands or code for common certificate checking scenarios with expected output examples
Remove all meta-description content ('This skill provides...', 'When to Use...') and replace with actual technical guidance
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is padded with generic boilerplate that explains nothing specific about HTTPS certificate checking. Phrases like 'provides automated assistance' and 'follows industry best practices' are filler that Claude doesn't need. | 1 / 3 |
Actionability | No concrete code, commands, or specific instructions are provided. The skill describes what it does abstractly ('provides step-by-step guidance') but never actually provides any guidance on how to check HTTPS certificates. | 1 / 3 |
Workflow Clarity | No workflow, steps, or process is defined. The content only describes trigger phrases and vague capabilities without any actual procedure for certificate checking. | 1 / 3 |
Progressive Disclosure | The content is a monolithic block of meta-description with no useful structure. There are no references to detailed materials, examples, or related documentation that would help with actual certificate checking tasks. | 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.