aws-secrets-rotation

Automate AWS secrets rotation for RDS, API keys, and credentials

Quality

63%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Medium

Suggest reviewing before use

Fix and improve this skill with Tessl

tessl review fix ./skills/antigravity-aws-secrets-rotation/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.

The content is highly actionable with concrete executable examples but is long and monolithic, inlining full scripts that belong in bundle files and lacking validation feedback loops for its destructive rotation operations.

Suggestions

Add an explicit rotation workflow with validation checkpoints (e.g., rotate in non-prod -> test new credentials -> verify -> promote -> monitor) including a validate-fix-retry loop, to lift workflow clarity above the destructive-ops cap of 3.

Move the full Lambda templates, audit script, and compliance report into files under scripts/ or references/ and reference them one level deep from SKILL.md to improve progressive disclosure and conciseness.

Fix the minor code inconsistencies (define generate_password before use; include dbInstanceIdentifier in the RDS secret JSON) so the examples are fully copy-paste ready.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient and free of concept over-explanation, but ~460 lines with several fully inlined scripts (Lambda functions, audit and compliance scripts) could be tightened or moved to bundle files.	3 / 5
Actionability	Executable aws CLI commands and complete Python/Node.js SDK and Lambda examples make the guidance largely copy-paste ready, with minor inconsistencies (e.g., generate_password used before definition, dbInstanceIdentifier absent from the secret JSON).	4 / 5
Workflow Clarity	The skill performs destructive/batch operations (rotating production secrets, modifying RDS passwords, revoking API keys) but lacks an explicit sequenced rotation workflow with validation checkpoints and a validate-fix-retry feedback loop, which caps workflow clarity at 3.	3 / 5
Progressive Disclosure	Clear section headers provide structure, but no bundle files exist and content that would fit separate files (full Lambda templates, audit/compliance scripts) is all inlined in a single long SKILL.md.	3 / 5
	Total	13 / 20 Passed

Description

70%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.

The description is specific and distinctive with good natural trigger terms, but it omits an explicit 'Use when...' clause, leaving the invocation trigger only weakly implied and capping completeness.

Suggestions

Add an explicit 'Use when...' clause, e.g. 'Use when rotating RDS credentials, API keys, or OAuth tokens in AWS Secrets Manager, or when complying with key-rotation policies.'

Include the term "passwords" and "Secrets Manager" as synonyms to broaden natural trigger coverage.

Name a second concrete action (e.g., 'audit rotation compliance' or 'set up Lambda rotation functions') to push specificity toward comprehensive coverage.

Dimension	Reasoning	Score
Specificity	"Automate AWS secrets rotation for RDS, API keys, and credentials" names the domain and a concrete action applied to multiple specific targets, with only a single action verb keeping it short of comprehensive.	4 / 5
Completeness	The "what" is clear (automate rotation for three secret types) but there is no explicit "Use when..." trigger clause, which per the rubric caps completeness at 3.	3 / 5
Trigger Term Quality	Natural terms like "AWS secrets rotation", "RDS", "API keys", and "credentials" are present and would be said by users, though common synonyms such as "passwords" or "Secrets Manager" are missing.	4 / 5
Distinctiveness Conflict Risk	The AWS + Secrets Manager + RDS/API-key rotation combination is a clear niche with distinct triggers and minimal overlap risk with other skills.	5 / 5
	Total	16 / 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
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

Repository: boisenoise/skills-collections
Path: skills/antigravity-aws-secrets-rotation/SKILL.md
Commit: 19c310e

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