Conciseness

The Overview paragraph ('Domain expertise for systematically investigating... insufficient timeout settings, external service delays, database connection issues, memory constraints...') and the 'The procedure collects function configuration, CloudWatch metrics and logs, dependency analysis, and cold start patterns' paragraph substantially restate each other and the frontmatter description. Mostly efficient and free of basic-concept padding, but the duplicated summary paragraphs and repeated 'See the full procedure for details' could be tightened — matching anchor 3 rather than 4.

Actionability

Provides one copy-paste command ('aws lambda list-functions --region <region>'), a concrete verified pointer to the executable SOP ('follow the procedure exactly. See [Lambda timeout debugging procedure](references/lambda-timeout-debugging.md)'), and specific troubleshooting directions. Minor gaps: most troubleshooting entries (e.g., 'Check the function's log group configuration and invocation metrics', 'Verify AWS credentials have permissions') lack the concrete commands, so not fully copy-paste ready — anchor 4 rather than 5.

Workflow Clarity

The body gives an unambiguous instruction ('follow the procedure exactly') delegating to a reference containing a 12-step sequenced SOP with explicit validation and error-recovery steps (poll queries until 'Complete', handle MalformedQueryException by adjusting and retrying). The operations are read-only diagnostics so no destructive/batch cap applies; scored 4 rather than 5 because the body itself surfaces no sequence or checkpoints — the sequence lives entirely one file away.

Progressive Disclosure

Verified against the actual bundle: the single referenced path references/lambda-timeout-debugging.md exists, is one level deep, clearly signaled as a markdown link, and carries the full detail (the body's condensed troubleshooting entries point back to it with 'See the full procedure for details'). Clear overview with an appropriately split, well-signaled, easy-to-navigate structure — anchor 5.

Specificity

The description lists multiple concrete actions — 'analyzing function configuration, CloudWatch logs and metrics, VPC/networking, cold starts, memory constraints, and downstream dependencies to identify root causes with actionable fixes' — giving comprehensive, specific coverage of the debugging workflow. Anti-drift check: it exceeds 'several specific actions with minor gaps' (4) because every major analysis dimension plus root-cause identification and fixes are explicitly named.

Completeness

Explicitly answers 'what' ('Debugs AWS Lambda function timeout failures by systematically analyzing... to identify root causes with actionable fixes') and 'when' ('Use when a Lambda function is timing out or approaching its timeout limit') with concrete trigger phrases, matching the anchor-5 example structure. Uses third-person voice ('Debugs'), so no voice penalty applies.

Trigger Term Quality

Natural terms users would say are present: 'Lambda function', 'timeout', 'timing out', 'approaching its timeout limit', 'AWS'. Not a 5 because common variations such as the 'Task timed out' error phrase or 'slow/hanging Lambda' phrasings are absent; clearly better than 3 since multiple natural keywords and synonyms appear.

Distinctiveness Conflict Risk

Clear niche (AWS Lambda timeout debugging) with a distinct, specific trigger set; unlikely to fire for unrelated skills. Anti-drift check: it does not merely reduce overlap risk to 'minor' (4) — the domain and triggers are uniquely scoped.