CtrlK
BlogDocsLog inGet started
Tessl Logo

testland/lambda-timeout-budget-reference

Pure-reference catalog of AWS Lambda timeout + billing semantics. Covers Lambda's hard 15-minute (900s) wall-clock limit, the timeout-vs-deadline relationship (Lambda Context.getRemainingTimeInMillis), per-invocation billing (rounded to 1ms; per-invocation + duration × memory), the memory-vs-CPU relationship (CPU scales linearly with memory), the integration-timeout cascade (API Gateway 29s → Lambda 15min; SQS visibility-timeout vs Lambda timeout), and per-runtime nuances. Use when designing a Lambda's timeout config, debugging timeout-vs-billing surprises, or sizing memory for compute-bound workloads.

73

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

Overview
Quality
Evals
Security
Files

Quality

Content

80%

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

A well-organized, lean reference catalog with concrete values, formulas, and actionable fixes; it scores well on conciseness and actionability. It loses points on workflow clarity (no sequenced procedure with checkpoints) and progressive disclosure (a single monolithic file rather than split references).

Suggestions

Add a short sequenced decision flow for sizing a Lambda timeout (e.g., pick integration ceiling -> set Lambda timeout below it -> add remaining-time check -> verify with the testable behaviours) with explicit validation checkpoints to lift workflow_clarity.

Split the large inline tables (integration cascade, anti-patterns, testable behaviours) into a references/ file referenced one level deep from SKILL.md so the overview stays a lean pointer, improving progressive_disclosure.

Replace the pseudocode handler snippet's placeholders (not_done, do_work_chunk(), ...) with a minimal but complete executable example, or explicitly note the placeholders are illustrative.

DimensionReasoningScore

Conciseness

The body is dense and table-driven — specific values (900s, 29s, $0.20/1M, 1769MB = 1 vCPU), formulas, and threshold rules — with little padding, and the doc quotes it cites are the reference payload rather than concepts Claude already knows. It is above level 2 because nearly every token earns its place; the few advisory lines ("Don't try to architect around the 15-minute limit") are brief, not verbose.

3 / 3

Actionability

Concrete, copy-paste-ready guidance dominates: the GB-second formula, per-integration timeout thresholds ("Lambda timeout MUST be < 29s"), and the anti-patterns table's specific fixes ("Visibility > Lambda timeout x 6"). The single Python snippet uses pseudocode placeholders, but as a reference catalog the actionable output is configuration values and thresholds, which are complete rather than missing key details — keeping it at the top anchor per the instruction-only guidance in scoring_notes.

3 / 3

Workflow Clarity

There is no multi-step sequenced workflow with explicit validation checkpoints — the body is reference material, not a procedure — though the "Testable behaviours" table does provide verification tests. It is not level 3 because a sequenced process with feedback loops is absent, and not level 1 because the testable-behaviours table supplies some validation guidance.

2 / 3

Progressive Disclosure

The content is well-organized into clear sections with a References section, but everything lives in one monolithic ~150-line SKILL.md with no bundle files to split into, so content is not "appropriately split" across files as the top anchor requires. It is above level 1 because sectioning and signaled external/companion references (cold-start-budget-reference, AWS docs URLs) give real structure rather than a wall of text.

2 / 3

Total

10

/

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.

The description is strong: third-person voice, concrete capabilities, explicit "Use when" triggers, and a distinct Lambda-specific niche. It hits the top anchor on every dimension with no over-claims or fluff.

DimensionReasoningScore

Specificity

The description names many concrete capabilities — "hard 15-minute (900s) wall-clock limit", "timeout-vs-deadline relationship (Lambda Context.getRemainingTimeInMillis)", "per-invocation billing", "memory-vs-CPU relationship", and "integration-timeout cascade (API Gateway 29s -> Lambda 15min)" — matching the anchor for multiple specific concrete actions. It is not the level below (2), which only names a domain and some actions without this breadth of concrete mechanisms.

3 / 3

Completeness

It clearly answers both what ("Pure-reference catalog of AWS Lambda timeout + billing semantics") and when (an explicit "Use when..." clause listing three triggering scenarios), satisfying the top anchor. It is not level 2, where the when-clause is missing or only implied — here the trigger guidance is explicit.

3 / 3

Trigger Term Quality

Natural trigger terms a Lambda user would say appear throughout — "AWS Lambda", "timeout", "billing", "memory", "CPU", "compute-bound workloads", "API Gateway", "SQS" — and the explicit "Use when designing a Lambda's timeout config, debugging timeout-vs-billing surprises, or sizing memory for compute-bound workloads" covers common phrasings. It is above level 2 because the coverage is broad rather than a few relevant keywords with missing variations.

3 / 3

Distinctiveness Conflict Risk

The niche is sharply Lambda-specific (timeout/billing/memory semantics plus the API Gateway 29s cascade), with triggers unlikely to fire for unrelated skills. It is not level 2 because the scope is too narrowly scoped to a single service's configuration domain to meaningfully overlap with generic 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.

Reviewed

Table of Contents