ssl-proxy-debug-workflow
Systematic debugging workflow for SSL/proxy connectivity issues with government and institutional websites
59
67%
Does it follow best practices?
Run evals on this skill
Adds up to 20 points to the overall score
View guide
High
Do not use without reviewing
Fix and improve this skill with Tessl
tessl review fix ./benchmarks/gdpval/skills/ssl-proxy-debug-workflow/SKILL.mdSecurity
2 findings: 1 high severity, 1 medium severity. You should review these findings carefully before considering using this skill.
W007: Insecure credential handling detected in skill instructions.
What this means
The skill handles credentials insecurely by requiring the agent to include secret values verbatim in its generated output. This exposes credentials in the agent’s context and conversation history, creating a risk of data exfiltration.
Why it was flagged
The skill includes an example that embeds proxy credentials directly in a URL string (e.g., 'http://username:password@proxy...'), which encourages including secrets verbatim in generated code/commands and thus poses a high exfiltration risk.
W013: Attempt to modify system services in skill instructions.
What this means
The skill prompts the agent to compromise the security or integrity of the user’s machine by modifying system-level services or configurations, such as obtaining elevated privileges, altering startup scripts, or changing system-wide settings.
Why it was flagged
The skill explicitly instructs disabling SSL verification and warnings (verify=False, urllib3.disable_warnings) and bypassing system proxy settings (session.trust_env = False), which are clear instructions to bypass security mechanisms.
- Repository
- HKUDS/OpenSpace
- Commit
c5a9c4b
- Audited
- Security analysis
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.