Automate AWS secrets rotation for RDS, API keys, and credentials
52
41%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Risky
Do not use without reviewing
Optimize this skill with Tessl
npx tessl skill review --optimize ./skills/antigravity-aws-secrets-rotation/SKILL.mdSecurity
2 findings — 1 high severity, 1 medium severity. 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.
Insecure credential handling detected (high risk: 0.90). The prompt contains example commands and code that embed plaintext secrets (e.g., aws secretsmanager create-secret with secret-string containing "password" and "sk_live_xxxxx", and API calls that auth with secret values), which encourages the LLM or agent to include secret values verbatim in generated commands or code.
The skill is specifically designed for direct financial operations, giving the agent the ability to move money or execute financial transactions — such as payment processing, cryptocurrency operations, banking integrations, or market order execution.
Direct money access detected (high risk: 1.00). The skill includes explicit integration with a payment gateway: the "Custom Rotation for API Keys" section shows concrete Stripe API calls (POST to https://api.stripe.com/v1/api_keys to create a key, GET /v1/balance to validate, DELETE /v1/api_keys/{old_key} to revoke). Those are specific, named payment-gateway API endpoints (Stripe), not generic HTTP examples. Managing and rotating Stripe API keys via the Stripe API is a direct payment-gateway capability and can enable financial actions. Therefore this skill contains direct financial execution authority.
f1697b6
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.