Implement secure secrets management for CI/CD pipelines using Vault, AWS Secrets Manager, or native platform solutions. Use when handling sensitive credentials, rotating secrets, or securing CI/CD environments.
69
56%
Does it follow best practices?
Impact
86%
1.11xAverage score across 3 eval scenarios
Risky
Do not use without reviewing
Optimize this skill with Tessl
npx tessl skill review --optimize ./tests/ext_conformance/artifacts/agents-wshobson/cicd-automation/skills/secrets-management/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.80). The prompt includes examples that embed secrets verbatim in commands and CLI arguments (e.g., vault token='root', vault kv put ... password=secret, aws --secret-string "super-secret-password", echo "DB_PASSWORD=$SECRET"), which instructs or demonstrates putting secret values directly into generated code/commands and thus requires handling/outputting secrets verbatim.
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.
Potentially malicious external URL detected (high risk: 0.70). The skill includes runtime references that fetch and execute remote code — e.g., GitHub Actions references like hashicorp/vault-action@v2, actions/checkout@v4, aws-actions/configure-aws-credentials@v4 and the Docker image trufflesecurity/trufflehog:latest are pulled and run during CI/CD jobs, so they are external runtime dependencies that execute remote code.
47823e3
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.