Dense, table-and-code-driven content that assumes Claude's competence and does not explain what serverless or emulators are; the cold-start and timeout-ceiling tables are specific data Claude cannot reliably recall, so every token earns its place.

Provides executable commands (yq queries, 'sam local generate-event ...'), a copy-paste TypeScript test, a concrete directory layout, and a CI workflow — fully actionable, not pseudocode.

Seven steps are clearly sequenced, and the two-tier CI (local tests → staging deploy + smoke) supplies an explicit validate-then-recover feedback loop, with the anti-patterns table acting as a guardrail checklist — clearing the level-3 bar and not being capped since verification is present.

No bundle files exist, so large inline reference tables (cold-start-by-runtime, timeout ceilings by integration) are content that could be split into a separate reference file; companion-catalog references are signaled but point to other skills rather than a local bundle, leaving structure present but improvable.

Enumerates a concrete action sequence — 'identifying the function inventory + event sources, picking the right local-emulator per function ... generating test events per event source, asserting on cold-start + timeout budgets, and emitting the test directory + CI config' — matching the anchor that lists multiple specific concrete actions.

Clearly answers both 'what' (the full build walk-through) and 'when' via the explicit 'Use when introducing integration tests to a serverless project.' clause, satisfying the level-3 anchor.

Uses natural terms a user would say ('integration tests', 'serverless', 'SAM template', 'serverless.yml', 'Wrangler config') with an explicit trigger clause; above the level-2 anchor by covering several platform keywords rather than a single generic one.

Occupies a clear niche — building a serverless integration-test suite from IaC definitions across named platforms — with distinct triggers unlikely to fire for unrelated skills.