CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

aws-serverless

Routes serverless requests to a compute form factor and the skill that owns it. Applies to Lambda, API Gateway, EventBridge, Step Functions and event-driven work while the compute, orchestration or integration choice is open — API backends, webhooks, jobs, cron, queue/stream consumers, durable workflows, event routing, Step Functions vs Durable Functions, and Pipes vs native event source mappings for queues and streams. Decides Event Functions on-demand vs Managed Instances, Web Functions, MicroVMs, EventBridge rules/Scheduler/Pipes/bus, HTTP vs REST API. Owns shared Lambda references (cold starts, SnapStart, concurrency, event sources, function URLs, throttling, troubleshooting). Defers to the specialized skill once a request commits to one form factor or service, or describes its defining feature without naming it (durable checkpointing and automatic step retries, Firecracker sandbox, managed instances, Node.js server). Not for EC2, ECS/EKS/Fargate or Amplify hosting.

Quality

91%

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

SKILL.md
Quality
Evals
Security

Quality

Content

85%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.

An exceptionally well-structured router skill: sequenced decision flow with explicit checkpoints and revise loops, fully actionable questions and thresholds, and clean one-level-deep reference files that all exist. The one weakness is token efficiency — routing information is repeated across three tables and the Tier 2 prose restates its own rules, which costs context without adding guidance.

Suggestions

Consolidate the three overlapping route tables (Step 1 direct routes, Tier 1 form-factor table, and the hand-off table): the same Event Functions / Web Functions / MicroVMs / Managed Instances rows appear in all three — merge into one table or cross-reference it to cut roughly 25–30 lines.

Tighten the Tier 2 paragraph: it states the peak-to-mean threshold and question, then restates both later in the same paragraph while also re-explaining Rule 3's Leaning classification; state each rule once and link to compute-decision-edge-cases.md for the repeats.

In Tier 3, replace the re-explanations of Rule 3 mechanics (e.g. the SQS downstream-protection and tenant-isolation bullets) with a one-line "Leaning (Rule 3)" tag plus the question, keeping the detail in the edge-cases reference.

DimensionReasoningScore

Conciseness

The body is dense with load-bearing decision rules, thresholds and scripted questions — no padding explaining concepts Claude already knows — but noticeable redundancy could be trimmed: the same routing targets (Event Functions, Web Functions, MicroVMs, Managed Instances) appear in three overlapping tables (Step 1, Tier 1, hand-off), and the Tier 2 paragraph restates the peak-to-mean question and Rule 3's Leaning mechanics several times within a single paragraph.

3 / 5

Actionability

For an instruction/routing skill the guidance is fully executable: copy-paste-ready questions ("Does peak traffic stay below twice the average within any 5–10 minute window…?"), exact numeric thresholds (15 min / 90 min / 8 h, peak-to-mean < 2, MaximumConcurrency 2–1,000, ParallelizationFactor 1–10), concrete CLI verbs ("aws lambda-web create-web-function") and a decision-to-skill hand-off table covering the common cases.

5 / 5

Workflow Clarity

A clearly sequenced multi-step process: Step 0 (entry point) → Step 1 (direct routes) → Step 2 (Tier 1→2→3 with explicit gating, "Drop to the next tier only when the previous one did not produce a confident match") → Steps 3–5 (conditional) → hand-off. Rule 3's classify-before-answering checkpoint and Rule 4's revise loop ("New information → re-run the affected tier and update the recommendation") provide validation and error-recovery feedback loops; the guardrail section handles the file-loading failure mode.

5 / 5

Progressive Disclosure

The body keeps only the routing logic inline and defers detail through well-signaled, one-level-deep references that all exist in the bundle (verified: all 10 references/*.md and assets/powertools-handler.py present; Tier 3 keeps headlines and points to compute-decision-edge-cases.md, full comparisons live in orchestration.md and api-gateway.md). Navigation is easy via the how-to paragraph, the hand-off table and the need→file shared-references table; cross-links between reference files are lateral, not nested.

5 / 5

Total

18

/

20

Passed

Description

92%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 strong router description: concrete named capabilities, an explicit applies-when clause with trigger phrases, and unusually disciplined boundary handling for both sibling skills and non-serverless compute. The only gap is a handful of natural trigger terms (SQS, Kinesis, state machine) that users would say but that appear only conceptually.

DimensionReasoningScore

Specificity

Multiple concrete, named actions with comprehensive coverage of the router's scope: "Routes serverless requests to a compute form factor and the skill that owns it", "Decides Event Functions on-demand vs Managed Instances, Web Functions, MicroVMs, EventBridge rules/Scheduler/Pipes/bus, HTTP vs REST API", "Owns shared Lambda references (cold starts, SnapStart, concurrency, event sources, function URLs, throttling, troubleshooting)". Every capability is concrete and service-level; nothing is generic filler.

5 / 5

Completeness

Explicitly answers both: what ("Routes serverless requests…", "Decides…", "Owns shared Lambda references") and when ("Applies to Lambda, API Gateway, EventBridge, Step Functions and event-driven work while the compute, orchestration or integration choice is open — API backends, webhooks, jobs, cron…"), plus explicit when-not boundaries ("Defers to the specialized skill once a request commits to one form factor or service", "Not for EC2, ECS/EKS/Fargate or Amplify hosting"). Concrete trigger phrases on both the include and exclude sides.

5 / 5

Trigger Term Quality

Good natural-language coverage: "Lambda", "API Gateway", "EventBridge", "Step Functions", "API backends", "webhooks", "jobs", "cron", "queue/stream consumers", "durable workflows", "event routing", "cold starts". A few common phrasings users would actually say are absent (e.g. SQS, Kinesis, SNS, DynamoDB, "state machine"), so it falls just below the comprehensive-with-synonyms anchor.

4 / 5

Distinctiveness Conflict Risk

A clear niche — serverless routing on AWS while the choice is open — with explicit conflict management against its own specialized siblings: it names the defining features that trigger deferral ("durable checkpointing and automatic step retries, Firecracker sandbox, managed instances, Node.js server") and lists out-of-scope services. As a router it necessarily overlaps siblings, but the boundary conditions make wrong-skill triggering unlikely.

5 / 5

Total

19

/

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

aws/agent-toolkit-for-aws

Path

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