terra-connections
Terra API device and provider connections. Use when connecting users to wearables (Fitbit, Garmin, Apple Health, Oura, WHOOP), managing user sessions, or handling disconnections.
67
80%
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-connections/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 includes hardcoded example API credentials in Python code blocks, which encourages the exposure and handling of secrets.
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 hardcoded credentials (`dev_id="botaniqalmedtech-testing-SjyfjtG33s"` and `api_key="_W7Pm-kAaIf1GA_Se21NnzCaFZjg3Izc"`). While they appear in a code example, the API key is a high-entropy literal string that grants access to a specific service account (Terra API), which constitutes a real credential leak rather than a generic placeholder like `YOUR_API_KEY`.
- 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.