CtrlK
BlogDocsLog inGet started
Tessl Logo

ssl-proxy-troubleshoot-fb786c

Systematic approach to diagnosing and resolving SSL/proxy connectivity issues with restricted websites

64

Quality

75%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./benchmarks/gdpval/skills/ssl-proxy-troubleshoot-fb786c/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

88%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 highly actionable, well-sequenced troubleshooting workflow with concrete commands, decision-tree feedback loops, and a success checklist; its main weakness is mild redundancy (intro restatement and decision tree echoing the steps) and no use of reference files to offload detail.

DimensionReasoningScore

Conciseness

The body is mostly lean command blocks with minimal concept explanation, but the intro paragraph restates the description and the decision tree duplicates the step content, so it is not a clean 5.

4 / 5

Actionability

Provides copy-paste-ready bash (curl, openssl, nslookup, dig) and Python (requests with custom SSL context) commands that cover the common diagnostic cases, matching the fully-executable anchor.

5 / 5

Workflow Clarity

A clear 6-step sequence is reinforced by a decision tree with Works/Fails feedback loops, an explicit iteration limit ('5+ distinct approaches'), and a success-criteria checklist, matching the explicit-validation-and-feedback-loops anchor.

5 / 5

Progressive Disclosure

No bundle files exist and all content is inline, but it is well organized into clearly headed sections with a navigable decision tree; the fallback-strategy and command-catalog content could arguably be split out, so it stops at 4 rather than 5.

4 / 5

Total

18

/

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 states what the skill does and targets a distinct niche, but it lacks an explicit 'Use when...' trigger clause and only names a couple of concrete actions, which caps completeness and specificity at 3.

Suggestions

Add an explicit trigger clause, e.g. 'Use when HTTP requests fail with SSL/TLS certificate errors or connections are blocked by proxy/restricted-network rules.'

List more concrete actions (e.g. 'inspects certificates, tests proxy configurations, retries over alternate protocols/ports') to lift specificity toward 4-5.

Include common synonyms users say ('certificate errors', 'HTTPS', 'can't access site') to broaden trigger term coverage.

DimensionReasoningScore

Specificity

Names the domain ('SSL/proxy connectivity issues with restricted websites') and two concrete actions ('diagnosing and resolving'), matching the 1-2 concrete actions anchor; not a comprehensive list of actions so it stays at 3 rather than 4.

3 / 5

Completeness

The 'what' is clear (a systematic approach to diagnosing/resolving SSL/proxy issues) but there is no 'Use when...' clause or equivalent explicit trigger guidance, which per the rubric caps completeness at 3.

3 / 5

Trigger Term Quality

Includes natural user-facing terms like 'SSL', 'proxy', 'connectivity issues', and 'restricted websites' that a user would plausibly say; a few common synonyms (e.g. 'certificate errors', 'HTTPS', 'can't access') are missing, keeping it just below 5.

4 / 5

Distinctiveness Conflict Risk

The SSL/proxy connectivity troubleshooting niche for restricted websites is fairly distinct with low conflict risk; it could overlap slightly with general networking skills, so it is not a clear 5.

4 / 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
HKUDS/OpenSpace
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.