https-certificate-checker
Https Certificate Checker - Auto-activating skill for Security Fundamentals. Triggers on: https certificate checker, https certificate checker Part of the Security Fundamentals skill category.
30
Quality
7%
Does it follow best practices?
Impact
57%
1.07xAverage score across 3 eval scenarios
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./planned-skills/generated/03-security-fundamentals/https-certificate-checker/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 essentially a placeholder with no substantive content. It only states the skill name, repeats it as a trigger, and mentions a category. It completely fails to describe what the skill does or when it should be used, making it nearly useless for skill selection among multiple options.
Suggestions
Add specific actions the skill performs, e.g., 'Validates HTTPS certificates, checks expiration dates, verifies certificate chains, identifies security warnings'
Add a 'Use when...' clause with natural trigger terms like 'SSL certificate', 'cert expiry', 'TLS validation', 'check if website is secure', 'certificate errors'
Remove the duplicate trigger term and replace with varied natural language phrases users would actually say when needing certificate checking
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description only names the skill 'Https Certificate Checker' but provides no concrete actions. It doesn't explain what the skill actually does - no verbs describing capabilities like 'validates', 'checks expiration', 'analyzes certificate chains', etc. | 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' line just repeats the skill name rather than providing meaningful trigger scenarios. | 1 / 3 |
Trigger Term Quality | The trigger terms are just the skill name repeated twice ('https certificate checker, https certificate checker'). Missing natural user phrases like 'SSL certificate', 'cert expiry', 'TLS', 'certificate validation', 'check if site is secure'. | 1 / 3 |
Distinctiveness Conflict Risk | The term 'https certificate checker' is somewhat specific to certificate checking, but without describing actual capabilities, it could overlap with other security-related skills. The category mention 'Security Fundamentals' is too broad to help differentiation. | 2 / 3 |
Total | 5 / 12 Passed |
Implementation
7%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill is essentially a placeholder template with no substantive content about HTTPS certificate checking. It describes what the skill should do but provides zero actionable guidance, code examples, or specific instructions. The entire body could be replaced with actual certificate checking techniques (e.g., openssl commands, Python ssl module usage, common certificate validation checks).
Suggestions
Add executable code examples for checking HTTPS certificates (e.g., `openssl s_client -connect example.com:443` or Python ssl/requests examples)
Include specific validation steps: certificate expiration, chain verification, hostname matching, revocation checking
Remove all generic boilerplate ('provides automated assistance', 'follows industry best practices') and replace with actual certificate checking procedures
Add common certificate issues to check for (expired certs, self-signed, weak algorithms, missing intermediate certs) with detection methods
| 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 conditions and vague capabilities without any actual procedure for certificate checking. | 1 / 3 |
Progressive Disclosure | The content is organized into clear sections with headers, but there's no actual content to disclose. No references to detailed materials or examples are provided, though the structure itself is reasonable. | 2 / 3 |
Total | 5 / 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
994edc4
- 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.