CtrlK
BlogDocsLog inGet started
Tessl Logo

ssl-proxy-troubleshoot

Systematic workflow for troubleshooting SSL/proxy connectivity issues with government websites

51

Quality

56%

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/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

63%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 content is a well-sequenced, actionable troubleshooting playbook with concrete code and a useful decision matrix, but it is verbose in places, contains one broken example, and is monolithic with no progressive disclosure to reference files. Tightening prose, fixing the ssl_context snippet, and splitting the matrix/example into references would raise quality.

Suggestions

Fix Step 3 Option B so the constructed `ssl_context` is actually used (e.g. pass it to a session/adapter or use urllib with `context=ssl_context`) instead of repeating `requests.get(url, verify=False, ...)`.

Tighten prose by removing concept explanations Claude already knows (e.g. 'Government sites sometimes have misconfigured redirects…') and deduplicating the repeated `verify=False` demonstrations across Steps 2-4.

Move the decision matrix and the complete `robust_government_request` example into a referenced file (e.g. `references/decision-matrix.md`) so SKILL.md becomes a lean overview with one-level-deep references, improving progressive disclosure.

DimensionReasoningScore

Conciseness

The body is mostly efficient with concrete code, but includes padded explanatory sentences and redundancy — notably Step 3 Option B builds an ssl_context yet repeats `requests.get(url, verify=False, ...)` instead of using it — so it could be tightened rather than earning a 4.

3 / 5

Actionability

Mostly executable, copy-paste-ready code across all six steps plus a complete function example, but the broken ssl_context example in Step 3 and undefined placeholder variables (`dataset_name`, `topic_keyword`, `original_url`) are minor gaps that prevent a 5.

4 / 5

Workflow Clarity

A clear Step 1→6 sequence is paired with a decision matrix that acts as an error-recovery feedback loop and an explicit 'pivot after 5-10 failed attempts' checkpoint; validation is only implicit in places, which is the minor gap keeping it below 5.

4 / 5

Progressive Disclosure

No bundle files exist and the ~240-line skill is a single monolithic document; section headers give it structure, but content that could be split out (decision matrix, full example function, fallback strategies) is all inline with no one-level-deep references, fitting the 'some structure, content that should be separate is inline' anchor.

3 / 5

Total

14

/

20

Passed

Description

48%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 niche domain and a clear 'what', but it is light on concrete actions, omits any explicit 'Use when…' trigger clause, and underuses natural synonyms. It is functional but would benefit from trigger phrases and more specific capability verbs.

Suggestions

Add an explicit 'Use when…' trigger clause naming concrete symptoms, e.g. 'Use when requests to government or institutional websites fail with SSLError, ProxyError, certificate validation, or connection errors.'

Replace the generic verb 'troubleshooting' with specific concrete actions such as 'diagnose SSL certificate errors, adjust proxy settings, retry with protocol variations, and pivot to alternative data sources'.

Broaden trigger terms with natural synonyms users say — 'TLS', 'certificate', 'cert verification', 'connection refused', 'proxy blocked' — to improve trigger term quality and distinctiveness.

DimensionReasoningScore

Specificity

Names the domain ('SSL/proxy connectivity issues with government websites') but offers only the single generic action 'troubleshooting', matching the 'names domain but actions minimal/generic' anchor rather than the 1-2 concrete actions required for a 3.

2 / 5

Completeness

The 'what' is clear (a systematic troubleshooting workflow for SSL/proxy issues on government sites) but there is no 'Use when…' clause or equivalent trigger guidance, capping completeness at 3 per the rubric guideline.

3 / 5

Trigger Term Quality

Includes relevant keywords ('SSL', 'proxy', 'connectivity issues', 'government websites') a user might say, but misses common synonyms and variations such as 'certificates', 'TLS', 'cert errors', or 'connection refused', so it is not the comprehensive coverage of a 4.

3 / 5

Distinctiveness Conflict Risk

The government-websites plus SSL/proxy niche is mostly distinct with only minor overlap risk against general networking skills; it is more specific than the 'somewhat specific but could overlap' anchor at 3 but lacks the explicit distinct triggers needed for a 5.

4 / 5

Total

12

/

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.