leaked-secrets
Use when reviewing client-side JavaScript, HTML source, or git history for exposed credentials, API keys, or tokens.
62
73%
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 ./skills/leaked-secrets/SKILL.mdSecurity
1 high severity finding. 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 explicitly instructs scanning HTML/JS for patterns like "sk_", "ghp_", "AIza" and to "flag exact responses, cookies" which requires the agent to identify and potentially output secret values verbatim, creating an exfiltration risk.
- Repository
- thedaviddias/Front-End-Checklist
- Commit
48405aa
- 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.