CtrlK
BlogDocsLog inGet started
Tessl Logo

ssl-proxy-troubleshoot

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

52

Quality

57%

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

65%

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

The skill is highly actionable with executable code throughout and a clear step sequence, but it is verbose with redundant blocks and monolithic, lacking validation checkpoints and any progressive disclosure to separate reference files. Tightening the code and adding explicit decision checkpoints would raise the weaker dimensions.

Suggestions

Add explicit validation checkpoints between steps (e.g. 'If Step 1 reports an SSLError, skip to Step 3; if ProxyError, skip to Step 4') to turn the sequence into a feedback loop.

Consolidate the redundant per-step request snippets into the single robust_government_request function and reference it, removing near-duplicate blocks to improve conciseness.

Move the decision matrix, fallback strategies, and the complete example function into a reference file (e.g. references/STRATEGIES.md) and link to it from SKILL.md for proper progressive disclosure.

DimensionReasoningScore

Conciseness

The body is mostly efficient and code-heavy, but includes explanatory padding ('Government sites sometimes have misconfigured redirects...') and redundant near-duplicate request blocks across steps that could be tightened, matching 'mostly efficient but includes some unnecessary explanation'.

2 / 3

Actionability

It provides fully executable, copy-paste-ready Python in every step plus a complete robust_government_request function, matching the 'fully executable code; copy-paste ready' anchor.

3 / 3

Workflow Clarity

Steps 1-6 plus fallback strategies are clearly sequenced and a decision matrix gives symptom-to-action mapping, but there are no explicit validate-then-fix-then-retry checkpoints between steps, matching 'steps listed but validation gaps'.

2 / 3

Progressive Disclosure

Content is well-sectioned with clear headers, but it is a monolithic ~240-line SKILL.md with all material inline and no external references; at over 50 lines the simple-skill exception does not apply, so it lands at 'some structure but content that should be separate is inline'.

2 / 3

Total

9

/

12

Passed

Description

50%

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 is specific about its domain but reads as a single-sentence what-statement with no explicit when-to-use trigger guidance, capping completeness and distinctiveness. Adding a 'Use when...' clause with natural trigger terms would lift the lower dimensions.

Suggestions

Add an explicit trigger clause, e.g. 'Use when you cannot access a government or institutional website, or when SSL certificate, proxy, or HTTPS connection errors occur.'

Expand the action list from the single word 'troubleshooting' to concrete actions like 'diagnose connection errors, try protocol and proxy variations, and pivot to alternative data sources'.

Include natural trigger terms users actually say (certificate, HTTPS, can't access, connection refused) to improve trigger-term coverage.

DimensionReasoningScore

Specificity

Names a concrete domain ("SSL/proxy connectivity issues with government websites") and one broad action ("troubleshooting"), but does not list multiple specific concrete actions, matching the score-2 anchor rather than the multi-action score-3 anchor.

2 / 3

Completeness

It clearly states what the skill does but provides no 'Use when...' clause or equivalent explicit trigger guidance, which the rubric guidelines cap at 2.

2 / 3

Trigger Term Quality

Includes relevant natural terms ("SSL", "proxy", "connectivity issues", "government websites") but misses common variations a user would say ("certificate", "HTTPS", "can't access"), so it lands at 'some relevant keywords but missing common variations'.

2 / 3

Distinctiveness Conflict Risk

The government-website SSL/proxy niche is somewhat specific, but without explicit trigger phrasing it could still overlap with general networking or web-request skills, matching the score-2 anchor.

2 / 3

Total

8

/

12

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.