x-daily-briefing
Audited by Socket on Feb 21, 2026
1 alert found:
Security[Skill Scanner] Credential file access detected All findings: [HIGH] data_exfiltration: Credential file access detected (DE002) [AITech 8.2.3] [HIGH] supply_chain: URL with free hosting platform or high-abuse TLD detected (SC007) [AITech 9.1.4] [HIGH] data_exfiltration: Credential file access detected (DE002) [AITech 8.2.3] This skill is functionally coherent and its capabilities align with the stated purpose. The main security consideration is that it requires a local API key and calls an external (Vercel-hosted) TimTracker API — that requires trusting the remote service and protecting the local config file. There are no high-risk supply-chain patterns (no download-and-execute, no unknown third-party proxies, no credential forwarding beyond the intended API). Recommend: ensure config file permissions are restrictive, confirm the api_url is the intended official service, and avoid committing the API key to VCS. LLM verification: The skill's purpose and described operations are coherent and consistent: it legitimately reads a configured API key, fetches weekly health data from the TimTracker API, and inserts a short Health Briefing into the user's Obsidian daily note. The primary risks are credential exposure (reading a local config with a GPT_API_KEY), reliance on a vercel.app-hosted API (supply-chain/trust risk), and unknown behavior inside the unprovided Python script (possible logging, insecure transmission, or extra