secrets-management

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.

Quality

75%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

High

Do not use without reviewing

Fix and improve this skill with Tessl

tessl review fix ./skills/secrets-management/SKILL.md

Quality

Content

65%Weight 40%Scale 1-3

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

Highly actionable with broad executable examples, but it reads as a flat reference catalog: verbose tool-feature lists pad the context, workflows lack validation checkpoints, and nothing is progressively disclosed into separate files.

Suggestions

Tighten the Vault/AWS/Azure/GCP feature bullet lists to only what Claude would not already know, or move full tool catalogs into reference files linked from a concise overview.

Add explicit validation/feedback checkpoints to the workflow (e.g., verify retrieval succeeded, confirm rotation took effect and old secret revoked) for the destructive rotation and DB-password steps.

Split per-platform integration recipes (Vault, AWS, GitHub/GitLab, Kubernetes) into separate reference files and link them from a lean SKILL.md overview to enable progressive disclosure.

Dimension	Reasoning	Score
Conciseness	Mostly efficient code and lists, but the per-tool feature bullet lists (Vault, AWS, Azure, GCP) restate what Claude already knows, and several "Use secret"/echo placeholders add padding.	2 / 3
Actionability	Provides copy-paste-ready bash, YAML, HCL, and Python snippets for storing, retrieving, rotating, and scanning secrets across concrete platforms.	3 / 3
Workflow Clarity	The 4-step "Instructions" are vague and lack validation checkpoints; destructive/batch operations like secret rotation and DB password updates have no feedback loops, capping this dimension at 2.	2 / 3
Progressive Disclosure	A single ~350-line monolithic file with no bundle references; large per-platform reference material is inline rather than split into clearly signaled one-level-deep files.	2 / 3
	Total	9 / 12 Passed

Description

85%Weight 40%Scale 1-3

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 well-formed description that clearly answers both what the skill does and when to use it, with concrete tools named. Trigger terms are slightly technical and could be broadened with everyday phrasings.

Dimension	Reasoning	Score
Specificity	Lists concrete actions ("Implement secure secrets management", "handling sensitive credentials", "rotating secrets") alongside specific tools (Vault, AWS Secrets Manager, native platform solutions).	3 / 3
Completeness	Explicitly states both what it does ("Implement secure secrets management...") and when to use it ("Use when handling sensitive credentials, rotating secrets, or securing CI/CD environments").	3 / 3
Trigger Term Quality	Triggers like "sensitive credentials", "rotating secrets", and "CI/CD environments" are relevant but technical, missing common user phrasings such as passwords, API keys, or secret rotation.	2 / 3
Distinctiveness Conflict Risk	Scoped to CI/CD secrets management with distinct tool and trigger vocabulary, making it unlikely to fire for unrelated skills.	3 / 3
	Total	11 / 12 Passed

Validation

100%

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 — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: rmyndharis/antigravity-skills
Path: skills/secrets-management/SKILL.md
Commit: e63f7dd

Reviewed: 13 days 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.