CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

aws-sdk-js-v3-usage

AWS SDK for JavaScript v3 development patterns. Use when writing JavaScript or TypeScript code that uses AWS services via @aws-sdk/* packages (aws-sdk-js-v3), or when asked about schemas, runtime validation, serialization, or code generation in the context of the JS/TS AWS SDK.

Quality

81%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Quality

Content

78%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 high-quality reference skill: lean, executable code for every common AWS SDK v3 task, clear gotcha warnings, and exemplary progressive disclosure with 11 verified one-level-deep reference files. The small deductions come from time-sensitive version numbers outside a deprecated section and a few code examples with undefined placeholder variables.

DimensionReasoningScore

Conciseness

The body is lean and code-first, assuming competence (no AWS/SDK primer, minimal prose per section). Minor trimmables keep it below anchor 5: the "Node.js Version Requirements" section carries time-sensitive version numbers outside any deprecated/old-patterns section, and the Abort Controller example includes verbose comment narration ("The request will not be created if...").

4 / 5

Actionability

Nearly all snippets are copy-paste ready with concrete values (e.g. `{ Bucket: "b", Key: "k" }`, `expiresIn: 3600`, full import statements) covering the common cases. Not a 5 because a few examples contain undefined placeholders — the Abort Controller example uses `clientParams`/`commandParams` and the Lambda example calls an undefined `prepare()` — which are minor gaps per anchor 4.

4 / 5

Workflow Clarity

As a patterns/reference skill, each section is an unambiguous single action, and risky operations are flagged with explicit gotchas ("Always read or discard streaming responses... socket exhaustion", the streaming deadlock warning, "Do not read or mutate client.config after instantiation"). Not anchor 5 since there are no explicit validate/feedback loops, but sequencing (middleware step order) and warnings go beyond anchor 3's missing checkpoints.

4 / 5

Progressive Disclosure

A clear overview with well-signaled, one-level-deep references: all 11 referenced files (clients.md, credentials.md, dynamodb.md, effective-practices.md, error-handling.md, lambda.md, performance.md, s3.md, schemas.md, sigv4a.md, typescript.md) exist in ./references/, each link is clearly motivated ("For all providers... see references/credentials.md"), and the body keeps only core patterns while pushing depth to the bundle.

5 / 5

Total

17

/

20

Passed

Description

73%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 description with an explicit, concrete "Use when" trigger clause and a well-scoped niche with minimal conflict risk. Its main weakness is that the "what" side ("development patterns") is generic and does not enumerate the skill's actual capabilities, which also limits specificity.

DimensionReasoningScore

Specificity

Names the domain precisely ("AWS SDK for JavaScript v3 development patterns") but the only action phrase, "development patterns", is generic; the concrete content is package identifiers rather than enumerated capabilities. It sits above anchor 2 because the SDK and @aws-sdk/* package names are specific, but below anchor 4 because no list of several concrete actions is given.

3 / 5

Completeness

The "when" is explicit and concrete ("Use when writing JavaScript or TypeScript code that uses AWS services via @aws-sdk/* packages..."), and the "what" is stated ("AWS SDK for JavaScript v3 development patterns"). Not a 5 because the "what" does not enumerate what the skill actually covers (clients, credentials, streams, pagination, etc.).

4 / 5

Trigger Term Quality

Includes natural terms users would say — "JavaScript", "TypeScript", "AWS services", "aws-sdk-js-v3", "schemas", "runtime validation", "serialization", "code generation" — but misses common phrasings like "Node.js" and service names (S3, DynamoDB, Lambda) users often lead with. Good coverage with a few natural terms missing, matching anchor 4.

4 / 5

Distinctiveness Conflict Risk

A clear niche with distinct triggers: the specific SDK version, @aws-sdk/* package pattern, and the aws-sdk-js-v3 alias make mis-triggering unlikely. The potentially broad clause about "schemas, runtime validation, serialization, or code generation" is qualified "in the context of the JS/TS AWS SDK", keeping conflict risk minimal.

5 / 5

Total

16

/

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

skills/core-skills/aws-sdk-js-v3-usage/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.