SKILLEMALL.ai
GitHub ↗ RU Sign in

BF aws-lambda-durable-functions

Builds resilient, long-running, multi-step applications with AWS Lambda durable functions with automatic state persistence, retry logic, and orchestration for long-running executions. Covers the critical replay model, step operations, wait/callback patterns, error handling with saga pattern, testing with LocalDurableTestRunner. Triggers on phrases like lambda durable functions, durable execution, workflow orchestration, state machines, retry/checkpoint patterns, long-running stateful Lambda functions, saga pattern, human-in-the-loop callbacks, reliable serverless applications, context.step, context.wait, context.invoke, context.runInChildContext, withDurableExecution, DurableContext, UnrecoverableInvocationError, durable-execution-sdk, qualified ARN invocation, and durable handler replay.

ClawHub Agent Skills author: Amazon Web Services 1 file body ≈ 2 051 tokens Open the sourceclawhub.ai↗ analyzed 2 d ago

Builds resilient, long-running, multi-step applications with AWS Lambda durable functions with automatic state persistence, retry logic, and orchestration for…

As a process F 46/100 · Will not run — References files that are not bundled: references/getting-started.md, references/replay-model-rules.md, references/step-operations.md

GeneratorAWSInfrastructuretype and topics are labelled automatically from the skill text
Runs in: OpenClaw Claude / Claude Code ChatGPT / Codex Gemini CLI Cursor GitHub Copilot / VS Code Qwen Code Kimi Code CLI Z.ai (GLM) DeepSeek (Deep Code) Mistral Vibe LangChain (deepagents) Goose OpenCode
JSON
Technical rating
B
84/100
safety, quality, tests
Safety 60%
100
Quality 40%
60
Run on models
none yet
Process rating
F
46/100
Will not run
References files that are not bundled: references/getting-started.md, references/replay-model-rules.md, references/step-operations.md
Tools and files w 18
0
Result and completion w 14
0
Inputs and preconditions w 11
0
the three weakest of ten parameters · all ten

How to improve

  1. Say in the description WHEN to use the skill ("use when…", example requests): that is the agent's main cue.
  2. The text references files that are not there: add them or drop the references.
For the model run — optional
  • Your own cases (evals/evals.json, 4–6 real requests with expected answers): the full check would then run those instead of a model-drafted suite.
  • A spec.yaml with trigger phrases and assertions — a behaviour contract for CI; `skilltest init` writes a template.

Guard findings · 0

✓ No critical or high findings

Files scanned: 0. Evidence is masked. Grey chips explain why severity was lowered.

Against the Agent Skills spec

  • warning description-no-when description does not say WHEN to use the skill (no "use when")
  • warning missing-ref reference to a missing file: references/getting-started.md
  • warning missing-ref reference to a missing file: references/replay-model-rules.md
  • warning missing-ref reference to a missing file: references/step-operations.md
  • warning missing-ref reference to a missing file: references/wait-operations.md
  • warning missing-ref reference to a missing file: references/concurrent-operations.md
  • warning missing-ref reference to a missing file: references/error-handling.md
  • warning missing-ref reference to a missing file: references/advanced-error-handling.md
  • warning missing-ref reference to a missing file: references/testing-patterns.md
  • warning missing-ref reference to a missing file: references/deployment-iac.md
  • warning missing-ref reference to a missing file: references/advanced-patterns.md
  • warning missing-ref reference to a missing file: references/troubleshooting-executions.md

Process rating: all ten parameters 46/100

Will not run. References files that are not bundled: references/getting-started.md, references/replay-model-rules.md, references/step-operations.md
  • 0Tools and files. 11 referenced file(s) missing: references/getting-started.md, references/replay-model-rules.md, references/step-operations.md
  • 0Result and completion. Does not say what the result is
  • 0Inputs and preconditions. Does not say what the process needs to start
  • 30Running it twice. 7 mutating operations with no state check
  • 50Failures and branches. 0 branches, has a failure section
  • 70When it triggers. States when to use, but not when not to
  • 100Steps. 44 steps
  • 100Consistency. Name and required fields are in place
  • 100Execution cost. Instruction body is 2051 tokens
  • 100Progress reporting. Reports progress
  • medium Safety rules and hard prohibitions inside a skill: they belong in the system prompt, here they protect nothing

Everything here is measured from the skill text rather than judged by a model, so the numbers are checkable. A parameter weighs more when it is a more common reason for the process to stall.

Quality signals

  • +5Description has no quoted example phrases that should trigger the skill
  • +4Description does not say when NOT to use the skill (false activations)
  • +3Output format is not stated: the model decides each time
  • +1No license
  • +2Single-language instructions
  • +3Description length 799: enough signal without eating the budget
  • +4Structure: 11 headings
  • +3Step-by-step instructions: 44 items
  • +4Has examples (3 code blocks)

Quality base 70; lint remarks subtract, signals add up to 100. Result: 60.