CtrlK
BlogDocsLog inGet started
Tessl Logo

sslmate-cert-spotter-api

SSLMate — Cert Spotter API integration. Manage Certificates, Domains. Use when the user wants to interact with SSLMate — Cert Spotter API data.

56

Quality

64%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./skills/sslmate-cert-spotter-api/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

67%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body is a well-structured, actionable guide with real executable CLI commands and a clear setup-to-usage workflow. Its main weaknesses are mild verbosity (an explanatory intro paragraph and a redundant 'Popular actions' section) and the absence of explicit validation/error-recovery checkpoints in the workflow.

Suggestions

Trim the opening 'SSLMate's Cert Spotter API is a tool...' paragraph to one line, or drop it — Claude already knows what SSL/TLS certificate monitoring is.

Merge the redundant 'Popular actions' section into 'Searching for actions' to avoid restating the same `action list` command twice.

Add an explicit verification checkpoint after `connect` (e.g. confirm the new connection appears in `connection list --json`) and a brief error-recovery note for failed `action run` calls.

DimensionReasoningScore

Conciseness

The body is mostly efficient commands, but the opening paragraph ('SSLMate's Cert Spotter API is a tool that allows developers to monitor... used by security professionals, researchers...') explains domain context Claude already knows, and the 'Popular actions' section repeats the `action list` command already shown in 'Searching for actions'. It fits score 3 ('Mostly efficient but includes some unnecessary explanation or could be tightened') rather than 4 due to these two padding/redundancy points.

3 / 5

Actionability

It provides concrete, executable commands throughout (login, search, connect, connection list, action list, action run, request) plus a comprehensive flags table, with placeholders clearly marked. It stops short of 5 because the `action run` examples use generic placeholders and there is no end-to-end example with a real action ID and a realistic JSON input.

4 / 5

Workflow Clarity

The setup→connect→(check existing)→discover actions→run→proxy sequence is clearly laid out with numbered steps and implicit checkpoints (e.g. extracting the connector ID from `output.items[0]`, noting an existing `connectionId`). It is 4 rather than 5 because there are no explicit validation/error-recovery feedback loops, though the primarily query-oriented (non-destructive) API does not trigger the destructive-cap rule.

4 / 5

Progressive Disclosure

Content is organized into clear, well-labeled sections (Overview, Working with, First-time setup, Connecting, Searching for actions, Proxy requests, Best practices) with no bundle files present and no need for external references. It is 4 rather than 5 due to minor organization gaps — the thin/redundant 'Popular actions' section overlaps with 'Searching for actions'.

4 / 5

Total

15

/

20

Passed

Description

61%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

The description clearly identifies a distinct niche and includes both a 'what' and an explicit 'Use when' clause, but the action language is generic ('Manage') and the trigger phrases lack natural synonyms a user would actually say. It is solid but could be sharpened with concrete verbs and richer trigger terms.

Suggestions

Replace the generic verb 'Manage' with concrete actions the API supports, e.g. 'Search and monitor SSL/TLS certificate issuance, list certificates and domains, retrieve matching identities'.

Expand the 'Use when' clause with natural trigger phrases users would say, e.g. 'Use when the user wants to monitor new SSL/TLS certificates, check certificate transparency, or detect phishing/brand abuse via Cert Spotter'.

Add common synonyms and the file/term 'certificate transparency' or 'CT logs' to broaden natural keyword coverage.

DimensionReasoningScore

Specificity

The description names the domain ('SSLMate — Cert Spotter API') and the entities ('Certificates, Domains') but the only action verb is the generic 'Manage', which is minimal/generic rather than a concrete action. It does not reach score 3 because there is no concrete action like 'monitor', 'list', or 'search' — only the vague 'Manage', matching the score-2 anchor 'Names the domain but actions are minimal or generic'.

2 / 5

Completeness

Both 'what' ('Manage Certificates, Domains') and an explicit 'when' ('Use when the user wants to interact with SSLMate — Cert Spotter API data') are present. It is capped at 4 rather than 5 because the 'when' clause is somewhat tautological ('interact with ... API data') rather than offering concrete, varied trigger phrases.

4 / 5

Trigger Term Quality

It includes the product name ('SSLMate', 'Cert Spotter API') and entity terms ('Certificates', 'Domains'), but misses common natural variations users would say such as 'SSL certificates', 'certificate monitoring', 'certificate transparency', or 'phishing detection'. It fits score 3 ('Some relevant keywords but missing common variations or synonyms') rather than 4 because the natural-phrase coverage is thin.

3 / 5

Distinctiveness Conflict Risk

The skill targets a specific named product ('SSLMate — Cert Spotter API'), a clear niche with distinct triggers and minimal risk of conflicting with other skills. It clearly matches the score-5 anchor 'Clear niche with distinct triggers; minimal conflict risk'.

5 / 5

Total

14

/

20

Passed

Validation

100%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
membranedev/application-skills
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.