CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

aws-profile

Manage AWS profiles for MCP servers — discover SSO, Granted and role-chain profiles, check authentication with STS, switch configured profiles, and scan AWS Organization accounts. TTL is unknown unless the user shares an expiry timestamp without credentials.

Quality

77%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./skills/aws-profile/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

77%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 highly actionable, well-sequenced command skill with concrete commands, safety checks, and validation loops in every mode. Its weaknesses are repetition of the credential-boundary/TTL caveats across sections and a bundle that omits the reference file the body cites six times.

Suggestions

State the credential boundary and the TTL-unknown rule once in the dedicated 'Credential boundary' section and reference it from the modes instead of restating both in every mode.

Ship 'references/aws-mcp-profiles.md' with the sections the body cites (Profile Type Detection, Auth Flows, Config File Locations, Prod Safety, credential_process Pattern) or remove the six broken pointers.

Move the full example output tables and ini stanzas for discover/org-scan into the reference file, keeping one short example inline per mode to lighten the overview.

DimensionReasoningScore

Conciseness

The body is dense and operational, but the credential-boundary rules and 'TTL is unknown' caveats are restated in nearly every mode section, and 'Reference: references/aws-mcp-profiles.md' is repeated six times. Mostly efficient with some unnecessary repetition that could be tightened, and no padding of concepts Claude already knows, so it sits above anchor 2.

3 / 5

Actionability

Fully executable guidance: exact commands ('aws configure list-profiles', 'aws sts get-caller-identity --profile <profile>', 'aws organizations list-accounts --output json'), exact config file paths, concrete output tables, ini stanzas, and patch diff examples cover the common cases. Copy-paste ready for an instruction-only skill.

5 / 5

Workflow Clarity

Each mode has numbered steps with explicit validation checkpoints and error-recovery feedback: the prod switch halts without --confirm and shows a diff plus restart instructions, login validates with an STS check before reporting, and org-scan asks instead of inventing missing SSO settings. The destructive-switch cap does not apply because validation is present.

5 / 5

Progressive Disclosure

References are one level deep and clearly signaled with section anchors, but the sole referenced file 'references/aws-mcp-profiles.md' does not exist in the bundle, so every pointer is broken. Substantial inline detail (full output tables, ini templates) also makes the overview heavy, fitting the 'some structure, references present but unreliable' anchor better than 4.

3 / 5

Total

16

/

20

Passed

Description

70%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 specific, distinctive description that names four concrete capabilities in a clear niche. Its main gap is the absence of any 'Use when...' trigger guidance, which caps completeness, plus a missing natural trigger vocabulary around authentication and expiry.

Suggestions

Add an explicit trigger clause, e.g. 'Use when the user mentions AWS profiles, SSO login, expired credentials, or switching the AWS profile used by MCP servers.'

Mention the login/refresh capability and natural terms like 'authenticate' or 'expired credentials' to round out action coverage and trigger synonyms.

The trailing TTL sentence ('TTL is unknown unless the user shares an expiry timestamp without credentials') reads awkwardly and is a behavior rule, not a capability — move it to the body to keep the description a crisp capability statement.

DimensionReasoningScore

Specificity

'discover SSO, Granted and role-chain profiles, check authentication with STS, switch configured profiles, and scan AWS Organization accounts' lists several specific concrete actions with minor gaps — the login/refresh mode is never mentioned — placing it at anchor 4 rather than comprehensive anchor 5.

4 / 5

Completeness

The 'what' is clear and concrete (discover, check authentication, switch, scan accounts for MCP server profiles), but there is no 'Use when...' clause or equivalent trigger guidance, which the rubric caps at 3. It is not 4 because the 'when' is absent rather than merely implicit, and not 2 because the 'what' half is strong.

3 / 5

Trigger Term Quality

Natural keywords like 'AWS profiles', 'SSO', 'STS', 'AWS Organization accounts', and 'switch profiles' are present, but common user variations such as 'login', 'credentials', 'authenticate', or 'expired token' are missing. Good coverage with a few natural terms absent fits anchor 4.

4 / 5

Distinctiveness Conflict Risk

'Manage AWS profiles for MCP servers' carves out a clear niche with distinct triggers (SSO, Granted, role-chain, org account scanning) that are unlikely to fire for unrelated skills. Minimal conflict risk fits anchor 5.

5 / 5

Total

16

/

20

Passed

Validation

87%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

referenced_paths_exist

Referenced path issues: 8 missing

Warning

Total

14

/

16

Passed

Repository

nitinjain999/platform-skills

Path

skills/aws-profile/SKILL.md

Revision

c2e75b7

Reviewed

Table of Contents

DiscoveryImplementationValidation

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.

Claim skill