serverless-worker-aws

Set up the AWS side of a Temporal serverless worker — IAM role, Lambda function, and deploy — so the Worker Controller can scale workers from zero and you can exercise serverless worker deployments in the UI. Use when asked how to create the Lambda or IAM role for serverless workers, what to put in the Create Serverless Deployment form, or why an invoked Lambda never connects.

Quality

91%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Quality

Content

90%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.

A tight, executable runbook with concrete policies, commands, tables, an explicit verification step, and a thorough troubleshooting matrix. Its only gaps are a not-fully-chained validation retry loop and a single-file structure that keeps everything inline rather than splitting detail into reference files.

Suggestions

Tighten the verify→fix→re-verify loop: after the "Verifying it worked" log lines, add an explicit 'if these lines are missing, consult the table below, apply the fix, then re-run the tail command' step to reach a full feedback loop.

Consider extracting the local-Temporal/ngrok + dynamic-config YAML block (Part 3, Local) into a references/ file referenced one level deep, which would let the main SKILL.md stay an overview and improve the progressive-disclosure split.

Dimension	Reasoning	Score
Conciseness	Lean and high-signal throughout: it never explains what IAM, Lambda, or mTLS are, and every prose aside (external-ID requirement, 75s timeout rationale, 10s hot-reload, exporting AWS creds before `make start`) is non-obvious domain knowledge, not padding. Fits the "lean and efficient; every token earns its place" anchor.	5 / 5
Actionability	Provides copy-paste-ready trust/permissions policies, deploy bash, a Lambda-settings table, a .env variable table, UI form steps, a verify command with expected output, and a symptom→cause troubleshooting table. Fully executable and covers the common failure cases, matching the 5 anchor.	5 / 5
Workflow Clarity	Part 1/2/3 are clearly sequenced with an explicit "Verifying it worked" checkpoint and a troubleshooting table for error recovery. Held at 4 rather than 5 because the verify→fix→re-verify loop is not tightly chained the way the 5-anchor example is; the recovery path is via a table rather than an inline retry loop.	4 / 5
Progressive Disclosure	Well-organized into clearly signaled sections with one genuine one-level reference (../local-temporal/SKILL.md). No bundle files exist to navigate, and all content lives inline in a 228-line file; this is appropriate for a runbook but lands at the "good structure; minor organization gaps" anchor rather than the 5 anchor that expects content split across reference files.	4 / 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.

A strong, specific description that concretely names the AWS actions it covers and gives explicit, natural-language trigger conditions for when to use it. The only soft spot is trigger-term breadth, which is solid but not exhaustively synonymized.

Dimension	Reasoning	Score
Specificity	Enumerates concrete actions — "IAM role, Lambda function, and deploy" — covering the full AWS-setup domain rather than gesturing at it abstractly. Matches the "multiple specific concrete actions; comprehensive coverage" anchor and is not merely a 4 since coverage is complete for this niche.	5 / 5
Completeness	Explicitly states both what (set up IAM/Lambda/deploy so the WCI scales workers from zero) and when ("Use when asked how to create the Lambda or IAM role... what to put in the Create Serverless Deployment form... or why an invoked Lambda never connects"). Clearly the 5 anchor; not a 4 because the when-clause is concrete, not weakly implied.	5 / 5
Trigger Term Quality	Natural triggers like "create the Lambda or IAM role for serverless workers", "Create Serverless Deployment form", and "why an invoked Lambda never connects" read as things users would actually say. Held at 4 rather than 5 because there is no synonym/extension-level exhaustiveness comparable to the 5 anchor.	4 / 5
Distinctiveness Conflict Risk	Targets a narrow niche — Temporal serverless worker AWS setup behind the Worker Controller — with triggers unlikely to fire for unrelated skills. Fits the "clear niche with distinct triggers; minimal conflict risk" anchor.	5 / 5
	Total	19 / 20 Passed

Validation

87%

Warnings & errors only

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

Validation — 14 / 16 Passed

Validation for skill structure

Criteria	Description	Result
relative_links	Relative link issues: 1 suspicious	Warning
referenced_paths_exist	Referenced path issues: 5 missing	Warning

	Total	14 / 16 Passed

Repository: temporalio/ui
Path: .claude/skills/serverless-worker-aws/SKILL.md
Commit: ffee037

Reviewed: 3 days ago

Table of Contents

Discovery Implementation Validation

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.