CtrlK
BlogDocsLog inGet started
Tessl Logo

signing-in-to-aws

Gets AWS credentials for CLI/SDK access via `aws login`. Activates when a developer needs to authenticate to AWS for local development, when an AWS operation fails due to missing or expired credentials, or when someone asks about setting up AWS access. Triggers: "set up AWS", "configure AWS", "aws login", "get credentials", "authenticate", "session expired", "token expired", "no credentials", "AccessDeniedException" with no configured credentials.

75

Quality

92%

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

SKILL.md
Quality
Evals
Security

Quality

Content

85%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A well-structured, highly actionable body with a clear sequenced workflow, explicit verification, and good error coverage. The main weakness is conciseness: behavioral guidance and the access-key security rationale are duplicated across sections, and the version pin is repeated rather than isolated.

Suggestions

Consolidate the "ask for confirmation, don't tell the user to run it themselves" guidance into one place and reference it, instead of restating it in the Important, Lead-with-recommendation, and Confirm-and-run sections.

State the long-term-access-key security rationale once (e.g., in the Fallback section) and reference it from the precondition step, rather than repeating near-identical wording.

Pin the AWS CLI version (2.32.0) once in Prerequisites and refer to "the required version" elsewhere, to keep the time-sensitive detail isolated and reduce repetition.

DimensionReasoningScore

Conciseness

It avoids basic-concept padding and assumes competence, but the confirmation instruction and the long-term-key security rationale are each repeated across sections, and the time-sensitive version "2.32.0" is stated four-plus times rather than isolated — it could be tightened.

2 / 3

Actionability

Concrete executable commands appear throughout (`aws --version`, `aws sts get-caller-identity`, `aws login --profile <name>`, `aws login --remote`), with specific confirmation phrasings and explicit succeed/fail decision branches — copy-paste ready.

3 / 3

Workflow Clarity

A clear sequence (lead with recommendation → precondition checks → confirm and run → verify) with an explicit post-login verification step and a dedicated error-recovery section; the operation is non-destructive and verification is present, so no cap applies.

3 / 3

Progressive Disclosure

No bundle files exist; the single SKILL.md is well-sectioned with clear navigation and one-level-deep external doc links in "Additional Resources", with no nested or deep references — appropriately self-contained for its scope.

3 / 3

Total

11

/

12

Passed

Description

100%

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: concrete single action with the exact command, explicit activation conditions, and a rich set of natural trigger terms, all in third person. It clearly answers both what and when with minimal fluff.

DimensionReasoningScore

Specificity

"Gets AWS credentials for CLI/SDK access via `aws login`" names the domain and the exact concrete command/action rather than vague language; for a single-purpose skill this is as specific as it gets.

3 / 3

Completeness

It states both what ("Gets AWS credentials for CLI/SDK access via `aws login`") and when ("Activates when a developer needs to authenticate…" plus an explicit Triggers clause), so it is not capped at 2.

3 / 3

Trigger Term Quality

An explicit Triggers list gives strong natural-term coverage — "set up AWS", "configure AWS", "aws login", "get credentials", "authenticate", "session expired", "token expired", "no credentials" — the terms a user would actually say.

3 / 3

Distinctiveness Conflict Risk

It carves a clear niche (AWS CLI/SDK credential acquisition via `aws login`) with distinct, AWS-specific triggers unlikely to fire for unrelated skills.

3 / 3

Total

12

/

12

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.