find-cause
Wraps investigation requests with evidence-chain discipline. Use when asked to find out why something happens, research a root cause, debug an issue, or investigate unexpected behavior. Transforms vague investigation requests into reproducible-proof investigations with a 5-step protocol — disambiguate, reproduce, read source, build evidence chain, present findings. Invoke with /find-cause followed by a description of what to investigate.
64
77%
Does it follow best practices?
Impact
—
No eval scenarios have been run
Risky
Do not use without reviewing
Fix and improve this skill with Tessl
tessl review fix ./.claude/skills/find-cause/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
Insecure credential handling detected (high risk: 1.00). The evidence-chain protocol requires capturing and quoting complete command outputs, environment variables, and exact file contents/lines as evidence (including "all arguments, flags, environment variables"), which forces the LLM to include secret values (API keys, tokens, passwords, cookies) verbatim in its output.
- Repository
- Jamie-BitFlight/claude_skills
- Commit
2f639b2
- 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.