credentials
Centralized API key management from Access.txt
40
38%
Does it follow best practices?
Impact
—
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: 0.90). 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
Secret detected (high risk: 1.00). 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:
- Repository
- alinaqi/claude-bootstrap
- Commit
65efb33
- 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.