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.
64
75%
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/secrets-management/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 hardcoded secret values and example commands that embed secrets verbatim (e.g., VAULT_TOKEN='root', password=secret, "super-secret-password"), which would require an LLM to reproduce secret values in output if following the examples.
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 skill includes CI/runtime references that fetch and execute external code at runtime (e.g., GitHub Actions and Docker images such as "hashicorp/vault-action@v2", "actions/checkout@v4", "aws-actions/configure-aws-credentials@v4", "vault:latest", and "trufflesecurity/trufflehog:latest"), so these are runtime external dependencies that execute remote code.
e63f7dd
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.