secrets-manager

AWS Secrets Manager for secure secret storage and rotation. Use when storing credentials, configuring automatic rotation, managing secret versions, retrieving secrets in applications, or integrating with RDS.

Quality

75%

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

Fix and improve this skill with Tessl

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

Quality

Content

61%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 a well-structured, actionable reference with strong code examples and clear sections, but it carries some redundant introductory explanation and lacks explicit validation checkpoints for its destructive and rotation workflows, which caps workflow clarity.

Suggestions

Trim the redundant opening summary and the basic Core Concepts definitions (e.g., what a secret is) to lean on Claude's existing knowledge and improve token efficiency.

Add explicit validate→fix→retry checkpoints to the rotation and delete-secret workflows, e.g., 'describe-secret to confirm rotation status' or 'verify AWSCURRENT label moved' before declaring success.

Fix the Lambda extension example to import os before referencing os.environ, and complete the CloudFormation snippet's RotationLambda resource so the examples are fully copy-paste-ready.

Dimension	Reasoning	Score
Conciseness	The body is mostly lean reference tables and code, but the opening summary restates the description and the Core Concepts section explains basics (Secrets/Versions/Rotation staging labels) that overlap with what Claude already knows, adding some unnecessary explanation.	3 / 5
Actionability	Provides concrete, copy-paste-ready CLI and boto3 examples across create/retrieve/cache/update/rotate/CloudFormation/Lambda-extension, with only minor gaps such as the Lambda extension example using `os.environ` without importing `os`.	4 / 5
Workflow Clarity	Content is organized by task sections rather than a sequenced multi-step workflow, and destructive/batch operations (delete-secret, rotation) lack explicit validate→fix→retry checkpoints, capping this dimension at 3 per the rubric.	3 / 5
Progressive Disclosure	A Table of Contents and clear section headers (Core Concepts, Common Patterns, CLI Reference, Best Practices, Troubleshooting, References) give strong internal navigation with no nested references, though the 300+ line bulk of CLI/API reference is inlined rather than split into separate files.	4 / 5
	Total	14 / 20 Passed

Description

88%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 strong: it states the capability concisely, includes an explicit 'Use when...' trigger clause with concrete, natural-phrased scenarios, and names multiple specific actions. Its only gap is slightly limited synonym/extension coverage in trigger terms.

Dimension	Reasoning	Score
Specificity	Enumerates multiple concrete capabilities — 'storing credentials, configuring automatic rotation, managing secret versions, retrieving secrets in applications, or integrating with RDS' — giving comprehensive coverage of the service's core actions.	5 / 5
Completeness	Explicitly answers both what ('AWS Secrets Manager for secure secret storage and rotation') and when via a concrete 'Use when...' clause listing specific triggers.	5 / 5
Trigger Term Quality	Includes natural phrases users would say ('storing credentials', 'automatic rotation', 'retrieving secrets', 'integrating with RDS'), but omits some synonyms and technical variants (e.g., secret ARN, KMS, parameter store) that would round out coverage.	4 / 5
Distinctiveness Conflict Risk	The named AWS service plus specific rotation/secret triggers give it a clear niche with minimal conflict risk, though adjacency to related AWS security skills (KMS, SSM Parameter Store) leaves minor overlap.	4 / 5
	Total	18 / 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: itsmostafa/aws-agent-skills
Path: skills/secrets-manager/SKILL.md
Commit: e786d25

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.