Trust Assessment
the-sports-db received a trust score of 49/100, placing it in the Untrusted category. This skill has significant security findings that require attention before use in production.
SkillShield's automated analysis identified 3 findings: 1 critical, 1 high, 1 medium, and 0 low severity. Key findings include File read + network send exfiltration, Sensitive path access: AI agent config, API Key exposed in URL parameters.
The analysis covered 4 layers: Manifest Analysis, Static Code Analysis, Dependency Graph, LLM Behavioral Safety. All layers scored 70 or above, reflecting consistent security practices.
Last analyzed on February 12, 2026 (commit 13146e6a). SkillShield performs automated 4-layer security analysis on AI skills and MCP servers.
Layer Breakdown
Behavioral Risk Signals
Security Findings3
| Severity | Finding | Layer | Location | |
|---|---|---|---|---|
| CRITICAL | File read + network send exfiltration AI agent config/credential file access Remove access to sensitive files not required by the skill's stated purpose. SSH keys, cloud credentials, and browser data should never be read by skills unless explicitly part of their declared functionality. | Manifest | skills/gumadeiras/the-sports-db/SKILL.md:7 | |
| HIGH | Sensitive path access: AI agent config Access to AI agent config path detected: '~/.clawdbot/'. This may indicate credential theft. Verify that access to this sensitive path is justified and declared. | Static | skills/gumadeiras/the-sports-db/SKILL.md:7 | |
| MEDIUM | API Key exposed in URL parameters The skill's documentation demonstrates the use of `THE_SPORTS_DB_KEY` directly within the URL query parameters for API calls. Transmitting API keys in URLs can lead to their exposure in server logs, proxy logs, browser history, and referrer headers, making them vulnerable to interception or logging. While this might be a requirement of TheSportsDB API, it is generally considered a less secure practice than using HTTP headers for authentication. If possible, configure the API to accept the key via HTTP headers (e.g., `Authorization` header) instead of URL parameters. If the API strictly requires the key in the URL, ensure that all communications are over HTTPS and that logs containing URLs are properly secured and rotated. Educate users about the risks of exposing API keys in URLs. | LLM | SKILL.md:14 |
Scan History
Embed Code
[](https://skillshield.io/report/0dbb8b603bb7368d)
Powered by SkillShield