CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

aws-skills

Collection of AWS development skills covering CDK infrastructure as code, cost optimization, and serverless/event-driven architectures with integrated MCP servers.

Quality

52%

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

Fix and improve this skill with Tessl

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

Quality

Content

25%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 redundant marketing-style index that restates the description three times, provides no executable guidance, and points to sub-skill SKILL.md files that are absent from the bundle. It needs a concrete task-to-skill mapping and either the actual per-skill files or their content inlined.

Suggestions

Ship the referenced sub-skill SKILL.md files (aws-cdk-development, aws-cost-operations, aws-serverless-eda) or inline their key guidance, since the bundle contains none of them and every reference dangles.

Replace the 'Key Features' buzzword bullets and redundant 'Use Cases' restatement with a concrete mapping of user tasks to the specific sub-skill file to open.

Add actionable content — e.g. how to invoke the integrated MCP servers or a minimal CDK/cost/serverless quick-start example — so the body instructs rather than only describes.

DimensionReasoningScore

Conciseness

The opening line restates the frontmatter description, and 'Included Skills', 'Use Cases', and 'Key Features' each restate the same three domains; buzzword bullets like 'Comprehensive: Covers infrastructure, costs, and operations' add no information. Several padded, redundant sections match anchor 2 rather than anchor 3's 'mostly efficient'.

2 / 5

Actionability

No code, commands, or executable steps appear anywhere; the only instruction is 'Refer to the specific SKILL.md files in each subdirectory'. This is slightly above anchor 1 (a concrete navigation pointer exists) but lacks any specific steps, matching anchor 2's minimal high-level guidance.

2 / 5

Workflow Clarity

No sequence or steps are presented; the only direction ('Each skill... can be used independently', refer to subdirectories) leaves major gaps — there is no task-to-sub-skill mapping, and the referenced subdirectory files do not exist in the bundle. Rough direction with many gaps fits anchor 2, not anchor 3 which presumes a step list exists.

2 / 5

Progressive Disclosure

The body is structured as an overview pointing one level deep to per-skill SKILL.md files, but no subdirectories or bundle files exist, so every reference dangles and navigation is impossible. The broken disclosure chain fits anchor 2 (minimal functional structure); the under-50-lines exception does not apply because the skill explicitly depends on external references that are missing.

2 / 5

Total

8

/

20

Passed

Description

56%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 clearly identifies the AWS domains covered and uses natural trigger terms, but it never states concrete actions or when the skill should be used. Adding a 'Use when...' clause with trigger scenarios and specific capabilities would materially improve it.

Suggestions

Add an explicit 'Use when...' clause, e.g. 'Use when designing CDK stacks, estimating or optimizing AWS costs, or building serverless/event-driven applications'.

Replace the generic 'covering' with concrete actions, e.g. 'Designs and implements CDK stacks, estimates and optimizes AWS spend, and builds event-driven serverless patterns'.

Include common trigger synonyms and variations such as 'pricing', 'IaC', 'Lambda', or 'CloudFormation' to broaden natural-term coverage.

DimensionReasoningScore

Specificity

The description names the domains ('CDK infrastructure as code, cost optimization, and serverless/event-driven architectures with integrated MCP servers') but the only verb is 'covering' — no concrete actions are stated. This matches anchor 2 (domain named, actions minimal or generic); anchor 3 requires 1-2 concrete actions, which are absent.

2 / 5

Completeness

It has a clear 'what' (collection covering CDK IaC, cost optimization, serverless/EDA with MCP servers) but no 'Use when...' clause or equivalent explicit trigger guidance, which caps completeness at 3 per the judging guidelines. Not 4 because 'when' is entirely absent rather than merely implicit.

3 / 5

Trigger Term Quality

'CDK', 'infrastructure as code', 'cost optimization', 'serverless', and 'event-driven' are terms users would naturally say when needing this skill. Missing common variations such as 'pricing', 'Lambda', 'deploy', or 'IaC', so it fits anchor 4 (good coverage, a few natural terms missing) rather than anchor 5.

4 / 5

Distinctiveness Conflict Risk

AWS-specific named sub-domains (CDK, cost operations, serverless/EDA) make it mostly distinct with only minor overlap risk against closely related AWS skills. It is more specific than anchor 3's generic example, but its breadth as a three-domain collection keeps it from anchor 5's tight single niche.

4 / 5

Total

13

/

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

Microck/ordinary-claude-skills

Path

skills_all/aws-skills/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.