CtrlK
BlogDocsLog inGet started
Tessl Logo

aws-lambda-managed-instances

Evaluates, configures, and migrates workloads to AWS Lambda Managed Instances (LMI). Runs Lambda functions on EC2 instances in the user's account while AWS manages provisioning, patching, scaling, routing, and load balancing. Triggers when queries mention Lambda Managed Instances, LMI, capacity providers, multi-concurrent execution environments, EC2-backed Lambda, persistent Lambda instances, PerExecutionEnvironmentMaxConcurrency, CapacityProviderConfig, cold start elimination via dedicated instances, migrating standard Lambda to managed instances, or cost comparison between standard Lambda and LMI with Savings Plans or Reserved Instances.

74

Quality

92%

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%

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 migration skill with excellent progressive disclosure and a validated cutover workflow. The main weakness is conciseness: several critical limits are repeated across four sections rather than stated once in the Limits Quick Reference and cross-referenced, and the existing assets/sqs-processor/template.yaml is never linked from the body.

Suggestions

De-duplicate the recurring limits (MinExecutionEnvironments=3, MaxVCpuCount default 400, 2048 MB memory min) — state each once in 'Limits Quick Reference' and reference it from Workflow/Best Practices instead of restating.

Trim marginal opener padding such as "Combines Lambda's developer experience with EC2's pricing and hardware options," which restates the lead sentence.

Link assets/sqs-processor/template.yaml from Step 5 (Set Up Infrastructure) or the Files table so the copy-paste-ready SAM template is discoverable from the main file.

DimensionReasoningScore

Conciseness

The body is fact-dense and avoids explaining concepts Claude already knows, but the same facts recur across sections — "minimum 3 execution environments," "MaxVCpuCount default 400," and "2048 MB memory minimum" each appear in Quick Decision, Workflow, Best Practices, and Limits — so not every token earns its place; it is not level 3 because of this repetition and mild opener padding ("Combines Lambda's developer experience with EC2's pricing and hardware options").

2 / 3

Actionability

Exact values are given throughout — memory ratios (2:1/4:1/8:1), per-runtime concurrency caps (Node 64, Java/.NET 32, Python 16), pricing components, and a 5-step infrastructure procedure — providing concrete, copy-ready guidance; not level 2 because the guidance is specific and complete rather than pseudocode or missing key details.

3 / 3

Workflow Clarity

A clear six-step sequence (Assess → Cost Comparison → Configure → Migrate → Set Up Infra → Validate/Cut Over) with a gated 10%→50%→100% traffic shift and an explicit cost-comparison gate before the destructive decommission step; not level 2 because validation checkpoints precede the irreversible production cutover.

3 / 3

Progressive Disclosure

SKILL.md is a clear overview with a Routing table mapping each user need to exactly one reference, a Files table, and a "Read ONLY the single reference file" instruction; all six references exist on disk and are one level deep. Not level 2 because navigation is explicitly signaled and content is appropriately split.

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.

An excellent description: third-person voice, three concrete verbs, an explicit 'Triggers when' clause, and a distinct niche. It is slightly padded with technical config field names (PerExecutionEnvironmentMaxConcurrency, CapacityProviderConfig) that few users would say aloud, but natural trigger coverage is strong.

DimensionReasoningScore

Specificity

"Evaluates, configures, and migrates workloads to AWS Lambda Managed Instances" lists three concrete, distinct actions matching the anchor for multiple specific concrete actions; it is not the level below because it names several verbs rather than a single domain+action.

3 / 3

Completeness

It explicitly answers what ("Evaluates, configures, and migrates workloads to AWS Lambda Managed Instances (LMI). Runs Lambda functions on EC2 instances...") and when ("Triggers when queries mention...") with an explicit trigger clause; not level 2 because the 'when' is stated explicitly rather than implied.

3 / 3

Trigger Term Quality

"Triggers when queries mention Lambda Managed Instances, LMI, ... EC2-backed Lambda, persistent Lambda instances, ... migrating standard Lambda to managed instances, or cost comparison" covers natural terms a user would say; not level 2 because common variations (product name, abbreviation, migration, cost comparison, cold start) are all present rather than missing.

3 / 3

Distinctiveness Conflict Risk

The AWS Lambda Managed Instances niche is highly specific with distinct triggers unlikely to fire for unrelated skills; not level 2 because the product-specific terms create a clear niche rather than a broad overlap.

3 / 3

Total

12

/

12

Passed

Validation

93%

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

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

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

Warning

Total

15

/

16

Passed

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.