BF 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.
AWS SDK for JavaScript v3 development patterns.
As a process F 41/100 · Will not run — References files that are not bundled: references/effective-practices.md, references/clients.md, references/credentials.md
How to improve
- The text references files that are not there: add them or drop the references.
- Your own cases (evals/evals.json, 4–6 real requests with expected answers): the full check would then run those instead of a model-drafted suite.
- A spec.yaml with trigger phrases and assertions — a behaviour contract for CI; `skilltest init` writes a template.
Guard findings · 0
✓ No critical or high findings
Files scanned: 1. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
missing-refreference to a missing file: references/effective-practices.md - warning
missing-refreference to a missing file: references/clients.md - warning
missing-refreference to a missing file: references/credentials.md - warning
missing-refreference to a missing file: references/dynamodb.md - warning
missing-refreference to a missing file: references/s3.md - warning
missing-refreference to a missing file: references/error-handling.md - warning
missing-refreference to a missing file: references/schemas.md - warning
missing-refreference to a missing file: references/performance.md - warning
missing-refreference to a missing file: references/lambda.md - warning
missing-refreference to a missing file: references/typescript.md - warning
missing-refreference to a missing file: references/sigv4a.md
Process rating: all ten parameters 41/100
- 0Tools and files. 11 referenced file(s) missing: references/effective-practices.md, references/clients.md, references/credentials.md
- 0Result and completion. Does not say what the result is
- 0Inputs and preconditions. Does not say what the process needs to start
- 0Progress reporting. Says nothing while it works
- 30Running it twice. 1 mutating operations with no state check
- 50When it triggers. No condition that starts the skill
- 50Failures and branches. 0 branches, has a failure section
- 100Steps. 7 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 2088 tokens
- low 16 top-level sections: this looks like several domains in one skill
Everything here is measured from the skill text rather than judged by a model, so the numbers are checkable. A parameter weighs more when it is a more common reason for the process to stall.
Quality signals
- +5Description has no quoted example phrases that should trigger the skill
- +4Description does not say when NOT to use the skill (false activations)
- +3Output format is not stated: the model decides each time
- +1No license
- +2Single-language instructions
- +3Description length 278: enough signal without eating the budget
- +4Structure: 17 headings
- +3Step-by-step instructions: 7 items
- +4Has examples (16 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 72.