credentials
Centralized API key management from Access.txt
50
38%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Risky
Do not use without reviewing
Optimize this skill with Tessl
npx tessl skill review --optimize ./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
Insecure credential handling detected (high risk: 1.00). The skill asks for a path or manual entry of API keys, parses and extracts raw secret values from the file, and instructs writing/validating those keys (e.g., creating a .env or embedding them in commands), which would require the LLM to handle or output secrets verbatim despite some masked-print examples.
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
Secret detected (high risk: 1.00). I scanned the entire skill prompt for literal, high-entropy credential values. Most occurrences are placeholders or intentionally masked (e.g., "sk-proj-xxxxx", "rnd_xxxxx", "sk-ant-xxx...", "OPENAI_API_KEY" names, truncated examples like "Y1FgKA..." or "-QLoYd..."), which I ignored per the rules.
- Repository
- alinaqi/claude-bootstrap
- Commit
d4ddb03
- 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.