CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

aws-secrets-manager

Secret safety for AWS Secrets Manager, secret management, credentials, API keys, tokens, and passwords. Prevents AI agents from directly fetching secret values and teaches runtime dynamic references with asm-exec so plaintext never enters the LLM context window.

Quality

70%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Critical

Do not install without reviewing

Fix and improve this skill with Tessl

tessl review fix ./plugins/aws-core/skills/aws-secrets-manager/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

63%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 body delivers strong executable guidance with clear MUST/MUST NOT rules, a precise reference syntax, and thorough troubleshooting with real feedback loops. Its weaknesses are inlined implementation details (SigV4 mechanics, re.sub internals) that pad token cost, and a progressive-disclosure failure: the asm-exec script exists in references/ but the body never points to it, so an agent cannot discover how to actually run the wrapper.

Suggestions

Link the script explicitly, e.g. "The wrapper lives at [references/asm-exec](references/asm-exec); run it as `python3 references/asm-exec -- <command>` or install it on PATH", so the examples are genuinely executable.

Move the SigV4 signing internals and the re.sub/subprocess implementation notes out of SKILL.md into a reference file, keeping only the credential-resolution order that Prerequisites actually needs.

Add a quick verification step to the usage patterns (e.g. check the command's exit status or stderr for "asm-exec:" lines before treating output as trusted).

DimensionReasoningScore

Conciseness

The rules, syntax table, and examples are tight, but the body inlines implementation internals the agent does not need to use the skill: "Substitutes resolved values using re.sub with a callable", "signs requests itself using only the Python standard library (hashlib/hmac)", and "The signing service and region are inferred from the endpoint hostname". This is mostly efficient with some unnecessary explanation that could be tightened or moved to a reference file, matching anchor 3 rather than 4, where over-explanation would be only minor.

3 / 5

Actionability

Guidance is largely copy-paste ready: three complete asm-exec examples (psql, curl, mysql), common patterns for docker and config templating, a syntax table with defaults, and concrete diagnostics ("aws sts get-caller-identity", "ASM_EXEC_MCP_TIMEOUT"). It falls short of 5 because the body never says where the asm-exec script lives or how to install/invoke it (the script sits at references/asm-exec but is never linked), leaving a gap between the examples and an actually runnable command.

4 / 5

Workflow Clarity

The sequence is clear (rules, then syntax, then usage, then patterns) and the Troubleshooting section provides a genuine error-recovery feedback loop ("read that line first", check credentials, check region, 401 means signing problem, raise ASM_EXEC_MCP_TIMEOUT). It does not reach 5 because the usage patterns lack an explicit verification checkpoint before proceeding (e.g. the config-templating example writes /tmp/app.conf with no check that resolution succeeded); recovery guidance is reactive rather than a workflow checkpoint.

4 / 5

Progressive Disclosure

Section structure is good, but the one bundle file — references/asm-exec, the very script the entire skill revolves around — is never referenced or linked anywhere in the body, and the only path mentioned ("plugins/aws-core/com.anthropic.claude-code/hooks/hooks.json") points outside the bundle. This matches anchor 3 (references present but not clearly signaled; inlined content such as the SigV4 signing internals that could live in a separate file) rather than 4, which requires references to be mostly clear.

3 / 5

Total

14

/

20

Passed

Description

61%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 clearly communicates a niche safety mechanism (runtime dynamic references via asm-exec so plaintext never enters the LLM context window) with good natural keyword coverage. Its main weakness is the missing explicit 'Use when...' trigger clause, which caps completeness, and it lists only two concrete actions. Adding a trigger clause and one or two more concrete capabilities would lift it substantially.

Suggestions

Add an explicit trigger clause, e.g. "Use when handling credentials, API keys, tokens, or passwords with AWS access, or when a command needs a secret value."

Name one or two more concrete actions (e.g. wrapping database, curl, and docker commands with resolved secrets) to lift specificity from 2 actions to several.

Consider trimming the mechanism explanation ("runtime dynamic references with asm-exec so plaintext never enters the LLM context window") to make room for the trigger clause without growing the description.

DimensionReasoningScore

Specificity

The description names the domain ("AWS Secrets Manager, secret management, credentials, API keys, tokens, and passwords") and exactly two concrete actions ("Prevents AI agents from directly fetching secret values" and "teaches runtime dynamic references with asm-exec"), matching the anchor for 1-2 concrete actions without comprehensive coverage. It does not reach 4 because there are not several distinct specific actions, and it is above 2 because the actions named are concrete rather than generic.

3 / 5

Completeness

The 'what' is clearly stated ("Prevents AI agents from directly fetching secret values and teaches runtime dynamic references with asm-exec"), but there is no 'Use when...' clause or equivalent explicit trigger guidance, which caps completeness at 3 per the judging guidelines. The 'when' is only weakly implied by "Prevents AI agents from..." and never made explicit.

3 / 5

Trigger Term Quality

Natural keywords are well covered: "AWS Secrets Manager", "secret management", "credentials", "API keys", "tokens", and "passwords" are all phrases users would naturally say when needing this skill. It falls short of 5 because there is no coverage of additional natural variations such as "sensitive values", "secret rotation", or "connection strings", and the asm-exec/resolve jargon is technical rather than user-spoken.

4 / 5

Distinctiveness Conflict Risk

"Secret safety for AWS Secrets Manager" carves out a clear niche with a distinct mechanism (dynamic references via asm-exec), but the generic terms "credentials, API keys, tokens, and passwords" create minor overlap risk with other credential-handling or secret-storage skills. It is mostly distinct (4) rather than fully distinct (5) because those generic terms could trigger for closely related secret-management skills.

4 / 5

Total

14

/

20

Passed

Validation

100%

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

aws/agent-toolkit-for-aws

Path

plugins/aws-core/skills/aws-secrets-manager/SKILL.md

Reviewed

Table of Contents

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.