CtrlK
BlogDocsLog inGet started
Tessl Logo

testland/aws-sam-local-testing

Wraps AWS SAM (Serverless Application Model) Local CLI for testing Lambda functions locally: `sam local invoke` (single invocation with event payload), `sam local start-api` (local API Gateway emulator), `sam local start-lambda` (local Lambda invoke endpoint for AWS SDK clients), and event-payload generation (`sam local generate-event`). For C#/.NET Lambdas, references/dotnet.md covers handler-direct testing with Amazon.Lambda.TestUtilities (TestLambdaContext, TestLambdaLogger) and the dotnet-lambda CLI. Use when testing Lambda + API Gateway + integrated AWS services locally.

72

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

Overview
Quality
Evals
Security
Files

Quality

Content

86%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 action-dense and well-structured, offloading the .NET specifics to a verified reference file while keeping core SAM Local commands inline and executable. It would tighten further by deduplicating the Running section and trimming minor explanatory padding in the Overview.

Suggestions

Remove the duplicate `sam local invoke HelloFunction --event event.json` from the 'Running' section since it is already demonstrated under 'Single invocation', or replace it with a distinctly new example.

Trim the Overview's runtime-mirroring explanation ('same Linux, same Node/Python/Java binaries, same handler-invocation contract') to a single clause; Claude already knows Lambda runtime contracts.

Add a short validate-then-retry note in the main flow (e.g. 'if invoke fails, run `sam build` and check `template.yaml` Handler/CodeUri') so the testing workflow has an explicit feedback loop rather than relying on the Anti-patterns table.

DimensionReasoningScore

Conciseness

Largely lean and assumes Claude's competence, but the Overview mildly over-explains the runtime mirroring ('same Linux, same Node/Python/Java binaries') and the 'Running' section repeats the `sam local invoke` command already shown, leaving minor trims available.

4 / 5

Actionability

Provides copy-paste-ready, executable guidance across the common cases: install commands, a template.yaml, generate-event invocations, start-api/start-lambda with a boto3 client example, a pytest harness, and a CI workflow.

5 / 5

Workflow Clarity

The Authoring → Running → CI sequence is clear with pytest assertions acting as validation, and an Anti-patterns table guides error recovery; however, there is no explicit validate-then-retry feedback loop in the primary local-testing flow.

4 / 5

Progressive Disclosure

Well-organized sections with the .NET deep-dive correctly split into a real one-level-deep reference (references/dotnet.md, which exists) and clearly signaled, keeping the body navigable.

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.

The description is concrete, third-person, and explicit about both capabilities and trigger conditions, enumerating specific SAM Local subcommands rather than resorting to vague language. Minor keyword synonym gaps (e.g. 'serverless') keep trigger coverage just below perfect.

DimensionReasoningScore

Specificity

Lists multiple concrete CLI subcommands with their distinct purposes (`sam local invoke`, `sam local start-api`, `sam local start-lambda`, `sam local generate-event`) plus .NET handler-direct testing, giving comprehensive coverage of the toolchain's capabilities.

5 / 5

Completeness

Explicitly answers 'what' (wraps SAM Local CLI with four named subcommands and .NET coverage) and 'when' via a concrete 'Use when testing Lambda + API Gateway + integrated AWS services locally' trigger clause.

5 / 5

Trigger Term Quality

Strong natural terms are present (Lambda, API Gateway, AWS services, testing locally) but a few user-natural synonyms like 'serverless' or 'SAM' as a standalone trigger are not surfaced, so it is just short of comprehensive.

4 / 5

Distinctiveness Conflict Risk

A clear niche (AWS SAM Local Lambda testing) with distinct triggers and named sibling tools in the body, giving minimal overlap risk with other skills.

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.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Reviewed

Table of Contents