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

70%

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

57%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 comprehensive, code-rich skill that is highly actionable across multiple platforms but suffers from length and inlining. Splitting per-platform details into referenced files and adding concrete validation checkpoints for rotation/deploy workflows would meaningfully improve it.

Suggestions

Move per-platform integration guides (Vault, AWS, Azure, GCP, External Secrets Operator) into separate reference files linked from a concise overview in SKILL.md to improve progressive disclosure and token efficiency.

Replace the pseudocode stubs (generate_strong_password, update_database_password) in the rotation Lambda with executable implementations or explicit pointers to where they are defined.

Add explicit validation checkpoints with concrete commands to the Instructions workflow (e.g., verify rotation succeeded, confirm audit logs captured the event) before proceeding to deploy.

Dimension	Reasoning	Score
Conciseness	The ~350-line body is mostly concrete code, but it spans many platforms inline (Vault, AWS, Azure, GCP, GitHub, GitLab, ESO, rotation, scanning) and includes feature-list bullets restating well-known tool capabilities (e.g., "AWS-native solution", "Automatic rotation", "Integration with RDS") that could be trimmed.	3 / 5
Actionability	Provides numerous copy-paste-ready examples across bash, YAML, HCL, and Python, but the rotation Lambda relies on undefined stubs ("generate_strong_password()", "update_database_password()") that prevent direct execution.	4 / 5
Workflow Clarity	The Instructions section gives a rough four-step sequence and the manual rotation process includes a "Verify functionality" checkpoint, but validation for destructive/batch operations (rotation, deploys) remains implicit and lacks concrete verification commands, capping this dimension per the rubric.	3 / 5
Progressive Disclosure	Section headers are well organized, but with no bundle files present all multi-platform content (~350 lines) is inlined in SKILL.md with no one-level-deep references to split per-tool or per-task guides, fitting the "content that should be separate is inline" anchor.	3 / 5
	Total	13 / 20 Passed

Description

83%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, well-targeted description that clearly answers both what and when with concrete tools and trigger phrases. It could reach the top anchor by using a more concrete lead verb and adding common synonyms like passwords, API keys, and tokens.

Dimension	Reasoning	Score
Specificity	Names the domain plus concrete tools ("Vault, AWS Secrets Manager, or native platform solutions") and concrete actions ("handling sensitive credentials, rotating secrets, or securing CI/CD environments"), but the lead verb "Implement secure secrets management" is somewhat abstract, leaving minor gaps versus the comprehensive anchor.	4 / 5
Completeness	Explicitly states both what it does ("Implement secure secrets management for CI/CD pipelines using Vault, AWS Secrets Manager, or native platform solutions") and when to use it ("Use when handling sensitive credentials, rotating secrets, or securing CI/CD environments") with concrete trigger phrases.	5 / 5
Trigger Term Quality	Includes natural terms users would say ("secrets", "CI/CD pipelines", "Vault", "AWS Secrets Manager", "sensitive credentials", "rotating secrets"), but omits common synonyms such as "API keys", "passwords", and "tokens" that users often voice.	4 / 5
Distinctiveness Conflict Risk	The CI/CD secrets-management niche with named backends is clearly distinct, but there is minor overlap risk with broader security or deployment-pipeline skills (e.g., the related deployment-pipeline-design skill).	4 / 5
	Total	17 / 20 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: 3eff4af

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