Name: secrets-vault-manager
Rating: 67.2 (1 reviews)
Author: alirezarezvani

secrets-vault-manager

Use when the user asks to set up secret management infrastructure, integrate HashiCorp Vault, configure cloud secret stores (AWS Secrets Manager, Azure Key Vault, GCP Secret Manager), implement secret rotation, or audit secret access patterns.

Quality

81%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

The canonical home for this skill is secrets-vault-manager in alirezarezvani/claude-skills

Quality

Content

72%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A highly actionable, well-organized reference skill with executable code across Vault and all three clouds. Its weak spots are the missing validation checkpoint in the destructive database-rotation workflow and poor file-level disclosure: much detail is inlined and referenced files do not exist.

Suggestions

Add an explicit verification step to the database dual-account rotation workflow (e.g., confirm app_user_b credentials are successfully fetched and serving traffic before rotating app_user_a) so the destructive sequence is not capped at 3.

Actually provide the referenced bundle files (references/emergency_procedures.md, vault_config_generator.py, rotation_planner.py, audit_log_analyzer.py) or remove the references to non-existent paths.

Move the dense reference material that Claude rarely needs in full (cloud comparison matrix, per-cloud SDK patterns) into one-level-deep reference files with clearly signaled links to improve progressive disclosure.

Dimension	Reasoning	Score
Conciseness	Largely dense reference material (tables, executable code) with little concept-padding, but the file is long, the 'When to Use' list overlaps the description, and a few explanatory sentences ('Dynamic secrets are generated on-demand...') could be trimmed, keeping it just below the lean-every-token anchor of 5.	4 / 5
Actionability	Provides copy-paste-ready, fully executable guidance across HCL policies/auth, Python SDK patterns for AWS/GCP/Azure, and Kubernetes/GitHub Actions YAML, covering the common cases comprehensively.	5 / 5
Workflow Clarity	Workflows are clearly numbered and sequenced, but the destructive/batch database dual-account rotation lacks an explicit validation checkpoint before the old credential is rotated/deprecated, triggering the destructive-operation cap at 3.	3 / 5
Progressive Disclosure	Section headers are well-organized, but bulk detail (cloud comparison matrix, SDK access patterns, rotation workflows) is inlined rather than split into reference files, and the referenced bundle files (references/emergency_procedures.md and three scripts/*.py) do not exist in the provided bundle.	3 / 5
	Total	15 / 20 Passed

Description

91%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A strong, third-person trigger-first description that names concrete actions and product synonyms across all three clouds, giving it excellent specificity and distinctiveness. The only weakness is that the capability statement is fused into the 'when' clause rather than given as a separate declarative.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions — 'set up secret management infrastructure, integrate HashiCorp Vault, configure cloud secret stores ... implement secret rotation, or audit secret access patterns' — with specific named cloud stores, giving comprehensive coverage rather than the minor gaps of a 4.	5 / 5
Completeness	The 'Use when the user asks to ...' clause answers 'when' explicitly with concrete triggers, and the actions embed a 'what', but the 'what' is fused into the trigger rather than stated as a standalone declarative, so it falls short of the clearly-separate what-and-when of a 5.	4 / 5
Trigger Term Quality	Natural user-facing terms are comprehensively covered including product-name synonyms across clouds ('AWS Secrets Manager, Azure Key Vault, GCP Secret Manager') plus 'HashiCorp Vault' and 'secret rotation', matching the comprehensive-synonyms anchor.	5 / 5
Distinctiveness Conflict Risk	It carves a clear infrastructure-layer niche (Vault clusters, cloud secret stores, rotation, audit) with distinct triggers and minimal overlap, reinforced by the body's explicit distinction from env-secrets-manager.	5 / 5
	Total	19 / 20 Passed

Validation

93%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
referenced_paths_exist	Referenced path issues: 1 missing	Warning

	Total	15 / 16 Passed

Repository: alirezarezvani/claude-skills
Path: .gemini/skills/secrets-vault-manager/SKILL.md
Commit: 19392f7

Reviewed: ~14 hours ago

Table of Contents

Discovery Implementation Validation

Is this your skill?

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.