Deploy Gamma-integrated applications to production environments. Use when deploying to Vercel, AWS, GCP, or other cloud platforms with proper secret management and configuration. Trigger with phrases like "gamma deploy", "gamma production", "gamma vercel", "gamma AWS", "gamma cloud deployment".
64
77%
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/gamma-pack/skills/gamma-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 prompt includes commands that embed the API key literal on the command line (aws secretsmanager --secret-string and echo -n "your-gamma-api-key" | gcloud secrets create), which requires placing the secret verbatim into shell commands—an insecure pattern that would force the LLM or user to handle/output the secret directly.
Low
Low-risk findings.
1 low severity finding. Worth noting, but not necessarily harmful.
The skill fetches instructions or code from an external URL at runtime, and the fetched content directly controls the agent’s prompts or executes code. This dynamic dependency allows the external source to modify the agent’s behavior without any changes to the skill itself.
The workflow uses third-party GitHub Actions "actions/checkout@v4" and "amondnet/vercel-action@v25", which are fetched and executed at CI/runtime and therefore constitute runtime external dependencies that execute remote code.
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.