terra-troubleshooting
Terra API troubleshooting and debugging. Use when experiencing connection issues, data sync problems, webhook failures, SDK errors, or provider-specific issues.
61
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/terra-troubleshooting/SKILL.mdW007: 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 prompt contains multiple hardcoded API keys and developer IDs directly embedded within code examples for testing, staging, and production environments, creating a severe credential exposure and 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
The documentation contains multiple examples of valid, active-looking API keys and dev IDs embedded directly in code blocks (e.g., `botaniqalmedtech-testing-SjyfjtG33s`, `_W7Pm-kAaIf1GA_Se21NnzCaFZjg3Izc`, and other production/staging environment credentials). These are high-entropy strings used for actual configuration examples rather than generic placeholders like "YOUR_API_KEY", posing a credential leakage risk.
- Repository
- fernandezbaptiste/Skrillz
- Commit
93ed392
- 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.