CtrlK
BlogDocsLog inGet started
Tessl Logo

aws-sdk-swift-usage

AWS SDK for Swift development patterns. Use when writing Swift code that uses AWS services via aws-sdk-swift package.

64

Quality

75%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

High

Do not use without reviewing

Fix and improve this skill with Tessl

tessl review fix ./plugins/aws-core/skills/aws-sdk-swift-usage/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

82%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 is a strong, action-dense reference: comprehensive executable Swift examples covering common AWS operations, with prescriptive gotchas on deprecated config types and declaration order. Its main weaknesses are minor redundancy around struct-config guidance and the absence of any progressive disclosure to separate reference files.

DimensionReasoningScore

Conciseness

The body is mostly executable code with targeted prose about SDK-specific gotchas (struct-vs-class deprecation, declaration order, namespacing), but the struct-config guidance is restated across the CRITICAL and Client Creation sections and the capitalized NEVER/ALWAYS/MUST emphasis adds some tokens, keeping it just below anchor 5.

4 / 5

Actionability

It provides copy-paste-ready Swift covering the common cases — client creation, config, credential resolvers, waiters, pagination, presigned URLs, and put/get/list operations — matching anchor 5's fully executable, comprehensive-example bar.

5 / 5

Workflow Clarity

As a patterns reference rather than a multi-step destructive workflow, it gives clear prescriptive guidance (which config type, declaration order, region required) with well-organized sections; no validation checkpoints are needed since no batch/destructive operations are involved, so it lands at anchor 4 rather than 5 which expects explicit feedback loops.

4 / 5

Progressive Disclosure

Content is organized into clearly headed sections with one clearly signaled external reference (the SDK source path at Sources/Services/...); at ~180 lines all inline it is well-structured but does not split detailed material into separate bundle files, so it sits at anchor 4 rather than 5.

4 / 5

Total

17

/

20

Passed

Description

68%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 well-targeted with an explicit Use-when trigger and a distinctive niche, but its "what" statement is generic ("development patterns") and would benefit from naming concrete capabilities like client creation, pagination, or presigned URLs.

Suggestions

Replace the generic "development patterns" with 2-3 concrete actions, e.g. "Create service clients, configure credentials, paginate results, and generate presigned URLs with the AWS SDK for Swift."

Add natural service-level trigger terms (e.g. S3, DynamoDB) so users naming a specific service surface this skill.

Keep the existing explicit "Use when..." clause — it is the strongest part of the description.

DimensionReasoningScore

Specificity

The phrase "AWS SDK for Swift development patterns" names the domain precisely but offers only a generic action ("development patterns") with no concrete operations listed, matching anchor 2 rather than 3 which requires 1-2 concrete actions.

2 / 5

Completeness

It has both a "what" ("AWS SDK for Swift development patterns") and an explicit, specific "when" ("Use when writing Swift code that uses AWS services via aws-sdk-swift package"), but the "what" is generic rather than listing concrete actions, keeping it below anchor 5.

4 / 5

Trigger Term Quality

It surfaces natural terms a user would say ("Swift code that uses AWS services", "aws-sdk-swift package", "AWS SDK for Swift") with good coverage, but lacks synonyms and service-level variations needed for anchor 5.

4 / 5

Distinctiveness Conflict Risk

The narrow "aws-sdk-swift package" trigger carves a clear niche distinct from general AWS or Swift skills with minimal conflict risk, matching anchor 5.

5 / 5

Total

15

/

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.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
aws/agent-toolkit-for-aws
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.