SKILLEMALL.ai
RU Sign in

B debugging-lambda-timeouts

Debugs AWS Lambda function timeout failures by systematically analyzing function configuration, CloudWatch logs and metrics, VPC/networking, cold starts, memory constraints, and downstream dependencies to identify root causes with actionable fixes. Use when a Lambda function is timing out or approaching its timeout limit.

ClawHub Agent Skills author: Amazon Web Services 1 file body ≈ 405 tokens open source ↗ analyzed 25 h ago
AnalyzerAWSSoftware developmenttype 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
B
88/100
Overall score
Safety 60%
100
Quality 40%
71
Tests bonus
0

How to improve

  1. The text references missing files: add them or drop the links.
  2. Add evals/evals.json with 4–6 real requests and expected answers: the full check will then use your cases instead of a model draft.
  3. Add a spec.yaml with triggers and assertions (skilltest init): the behaviour contract for CI.

Guard findings · 0

✓ No critical or high findings

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

Lint

  • warning missing-ref reference to a missing file: references/lambda-timeout-debugging.md

Process maturity 32/100

Will not run. References files that are not bundled: references/lambda-timeout-debugging.md
  • 0Tools and files. 1 referenced file(s) missing: references/lambda-timeout-debugging.md
  • 0Steps. Prose only: no discrete steps
  • 0Result and completion. Does not say what the result is
  • 0Inputs and preconditions. Does not say what the process needs to start
  • 20When it triggers. No condition that starts the skill
  • 100Failures and branches. 2 branches, has a failure section
  • 100Consistency. Name and required fields are in place
  • 100Execution cost. Instruction body is 405 tokens
  • 100Running it twice. No mutating operations
  • 100Progress reporting. Reports progress

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)
  • +3No numbered steps or checklist
  • +3Output format is not stated: the model decides each time
  • +4No input/output examples
  • +1No license
  • +2Single-language instructions
  • +3Description length 323: enough signal without eating the budget
  • +4Structure: 8 headings

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