credentials
Centralized API key management from Access.txt
60
70%
Does it follow best practices?
Run evals on this skill
Adds up to 20 points to the overall score
View guide
Risky
Do not use without reviewing
Fix and improve this skill with Tessl
tessl review fix ./skills/credentials/SKILL.mdSecurity
2 findings — 2 high 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 instructs the agent to ask for a credentials file or manual key entry, parse/extract API keys, and populate/validate a .env (potentially requiring the agent to handle or emit raw secret values), which creates a high exfiltration risk.
W008: Secret detected in skill content (API keys, tokens, passwords).
What this means
Detected sensitive credentials directly embedded within the skill content, such as API keys, access tokens, private keys, or service-specific secrets. Secrets should never be hardcoded in plain text within skill instructions.
Why it was flagged
I flagged the documentation because it contains literal, high-entropy credential-like values that appear usable. Specifically, in "Format 3: Mixed/Informal" the text includes: - client id: Y1FgKALKmb6f6UxFtyMXfA - secret: -QLoYdxMqOJkYrgk5KeGPa6Ps6vIiQ These look like a Reddit client_id/client_secret pair (random-looking, high entropy) and are not presented as placeholders or truncated examples. I ignored all obvious placeholders and low-entropy examples elsewhere in the doc (e.g., "sk-proj-xxxxx", "sk-ant-xxx...", "rnd_xxxxx", "xxx...", "YOUR_API_KEY", and other template/regex samples), which per the guidelines are documentation placeholders or truncated values and should not be flagged.
- Repository
- alinaqi/claude-bootstrap
- Commit
bb6195f
- 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.