CtrlK
BlogDocsLog inGet started
Tessl Logo

testland/lambda-test-tools-net

Wraps Amazon.Lambda.TestTool (the canonical .NET Lambda local-testing toolkit from github.com/aws/aws-lambda-dotnet) for invoking Lambda handlers from xUnit / NUnit tests with simulated AWS Lambda contexts (ILambdaContext, ILambdaSerializer). Covers handler-direct invocation, mock context fixtures, the dotnet-lambda CLI, and integration with the .NET LambdaSerializer for JSON. Use when testing AWS Lambda functions written in C#/.NET.

75

Quality

94%

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

85%

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

Highly actionable content with executable code, a clear sectioned workflow, and an effective anti-patterns/limitations structure. The only weak spot is mild verbosity in the Overview, which restates the description.

Suggestions

Trim the '## Overview' to avoid restating the description; keep only the one fact not already there (the Windows/Mac/Linux UI plus library-level fakes distinction).

Remove the few explanatory inline comments (e.g. 'NUnit-friendly mocks', 'Logger is auto-set to TestLambdaLogger') or fold them into a single note so every token earns its place.

Consider moving the longer code examples (serialized event payloads, remaining-time test) into a references/ file and linking from the body to further reduce inline token load.

DimensionReasoningScore

Conciseness

Mostly efficient with executable code and a tight anti-patterns table, but the '## Overview' re-states context already in the description and a few inline comments are slightly explanatory; minor tightening would reach the lean anchor.

2 / 3

Actionability

Provides fully executable guidance — `dotnet add package` commands, complete C# handler and test examples, dotnet-lambda CLI commands, and a CI YAML block — copy-paste ready with no pseudocode.

3 / 3

Workflow Clarity

A clear Install → handler → test → run → CI → anti-patterns → limitations sequence with `dotnet test` as the implicit validation checkpoint; appropriate for a non-destructive testing skill.

3 / 3

Progressive Disclosure

A self-contained, well-sectioned SKILL.md (no bundle files exist) with a one-level References list pointing to external GitHub URLs and named companion catalogs; organization is clear and not a monolithic wall.

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.

A strong, specific description that names concrete capabilities, includes a clear 'Use when...' trigger, and occupies a distinct niche. Third-person voice is used throughout, so no voice penalty applies.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — 'invoking Lambda handlers from xUnit / NUnit tests with simulated AWS Lambda contexts (ILambdaContext, ILambdaSerializer)' and 'handler-direct invocation, mock context fixtures, the dotnet-lambda CLI, and integration with the .NET LambdaSerializer for JSON' — matching the anchor for multiple specific concrete actions.

3 / 3

Completeness

Explicitly states both what it does ('Covers handler-direct invocation, mock context fixtures, the dotnet-lambda CLI...') and when to use it ('Use when testing AWS Lambda functions written in C#/.NET'), matching the explicit what-and-when anchor.

3 / 3

Trigger Term Quality

Uses natural user phrasing ('testing AWS Lambda functions written in C#/.NET', 'xUnit / NUnit tests', 'AWS Lambda') giving good coverage of terms users would say, with only minor over-reliance on API names.

3 / 3

Distinctiveness Conflict Risk

Targets a clear niche (.NET Lambda local testing) with distinct triggers and third-person voice, making it unlikely to trigger for unrelated 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