aws-secrets-rotation

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

Quality

37%

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Advisory

Suggest reviewing before use

Optimize this skill with Tessl

npx tessl skill review --optimize ./skills/antigravity-aws-secrets-rotation/SKILL.md

Quality

Content

42%

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

The skill provides highly actionable, executable code for AWS secrets rotation covering multiple secret types, rotation Lambda functions, monitoring, and compliance. However, it is excessively verbose—much of the content (SDK usage, basic secret retrieval, generic best practices checklists) is either already known to Claude or could be dramatically condensed. The monolithic structure with no bundle files means everything is crammed into one large document with no progressive disclosure.

Suggestions

Reduce content by 50%+: remove the Application Integration section (Claude knows how to use boto3/AWS SDK), trim the best practices checklists to rotation-specific insights only, and remove the Example Prompts and Kiro CLI sections.

Split into bundle files: move the Lambda rotation templates to a separate ROTATION_LAMBDAS.md, the audit/compliance scripts to AUDIT.md, and keep SKILL.md as a concise overview with references.

Add an explicit end-to-end workflow section with numbered steps, validation checkpoints, and error recovery paths (e.g., what to do when rotation fails, how to rollback).

Remove explanations of basic operations like 'Retrieve Secrets' and 'Create a Secret' which Claude can derive from AWS documentation knowledge—focus only on rotation-specific configuration and gotchas.

Dimension	Reasoning	Score
Conciseness	The skill is extremely verbose at ~350+ lines, with significant redundancy. It includes application integration examples (Python SDK, Node.js SDK) that Claude already knows how to write, explains basic concepts like retrieving secrets, and includes boilerplate like 'Example Prompts' and 'Kiro CLI Integration' sections that add little value. The best practices checklists are generic project management advice rather than rotation-specific insights.	1 / 3
Actionability	The skill provides fully executable CLI commands, complete Python Lambda rotation functions, bash audit scripts, and working SDK examples. Commands are copy-paste ready with realistic ARNs and parameters, and the rotation Lambda follows the actual four-step AWS rotation protocol (createSecret, setSecret, testSecret, finishSecret).	3 / 3
Workflow Clarity	The Lambda rotation function implicitly follows the four-step AWS rotation workflow, and the emergency rotation section includes a verification step. However, there's no explicit end-to-end workflow tying together secret creation → rotation setup → monitoring → verification. The audit script checks for overdue rotations but there's no feedback loop for handling rotation failures beyond a CloudWatch alarm.	2 / 3
Progressive Disclosure	The entire skill is a monolithic wall of content with no references to supporting files. Content like the compliance report script, audit script, SDK integration examples, and the full Lambda rotation functions could easily be split into separate referenced files. The Additional Resources section links to external docs but doesn't help with internal organization.	1 / 3
	Total	7 / 12 Passed

Description

32%

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 identifies a clear domain (AWS secrets rotation) and lists some target types, giving it reasonable distinctiveness. However, it lacks a 'Use when...' clause, misses common keyword variations like 'Secrets Manager' or 'rotate password', and doesn't enumerate specific concrete actions beyond 'automate rotation'. It needs explicit trigger guidance and more detailed capability listing to be effective for skill selection.

Suggestions

Add a 'Use when...' clause with explicit triggers, e.g., 'Use when the user asks about rotating secrets, managing AWS Secrets Manager, or automating credential lifecycle for RDS databases or API keys.'

Include more natural trigger terms and variations such as 'Secrets Manager', 'rotate password', 'database credentials', 'Lambda rotation function', 'secret rotation schedule'.

List more specific concrete actions, e.g., 'Creates rotation Lambda functions, configures rotation schedules in AWS Secrets Manager, updates RDS database credentials, and manages API key lifecycle.'

Dimension	Reasoning	Score
Specificity	Names the domain (AWS secrets rotation) and lists some targets (RDS, API keys, credentials), but doesn't describe concrete actions beyond 'automate rotation' — e.g., no mention of creating rotation lambdas, configuring schedules, updating policies, etc.	2 / 3
Completeness	Describes what it does (automate AWS secrets rotation) but completely lacks a 'Use when...' clause or any explicit trigger guidance for when Claude should select this skill. Per the rubric, a missing 'Use when...' clause caps completeness at 2, and since the 'what' is also only moderately detailed, this scores at 1.	1 / 3
Trigger Term Quality	Includes relevant keywords like 'AWS', 'secrets rotation', 'RDS', 'API keys', and 'credentials', which users might naturally say. However, it misses common variations like 'Secrets Manager', 'rotate password', 'database credentials', 'secret lifecycle', or 'Lambda rotation function'.	2 / 3
Distinctiveness Conflict Risk	The focus on AWS secrets rotation is fairly specific and unlikely to conflict with most skills, but could overlap with broader AWS infrastructure, security, or credential management skills. The mention of 'API keys' and 'credentials' is somewhat generic.	2 / 3
	Total	7 / 12 Passed

Validation

90%

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 — 10 / 11 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	10 / 11 Passed

Repository: boisenoise/skills-collections
Commit: 47e0c5a

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