Deploy Juicebox integrations. Trigger: "deploy juicebox", "juicebox production deploy".
59
70%
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 ./plugins/saas-packs/juicebox-pack/skills/juicebox-deploy-integration/SKILL.mdSecurity
1 high severity finding. You should review these findings carefully before considering using this skill.
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.
The skill includes an API-key-like literal (export JUICEBOX_API_KEY="jb_live_xxxxxxxxxxxx") and shows inserting JUICEBOX_API_KEY into an Authorization header and passing it via docker -e, which could lead an LLM to reproduce or embed secrets verbatim (exfiltration risk) even though env-var usage is otherwise a secure pattern.
4c47e33
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.