Conciseness

The body is ~67 lines of dense tables and commands with zero padding: it never explains what CDK or CloudFormation is, and every entry carries non-obvious knowledge ("Non-empty S3 buckets persist after destroy ... You MUST set both removalPolicy: DESTROY and autoDeleteObjects: true", the two-deploy "Deadly embrace" fix). It matches the lean, every-token-earns-its-place anchor; the only near-redundancy is the Overview restating the description, which is too minor to drop it to 4.

Actionability

Nearly every row is a copy-paste-ready command: "cdk bootstrap aws://$ACCOUNT/$REGION", "aws cloudformation describe-stack-events --stack-name $STACK --query \"StackEvents[?contains(ResourceStatus,'FAILED')]\"", "cdk rollback $STACK --orphan <LogicalId>", "rm -rf cdk.out", "npx tsc --noEmit". Specific errors map to specific fixes covering the common cases, matching the fully-executable anchor; the few terse hints ("Extract shared resource into third stack") are appropriately deferred to linked references.

Workflow Clarity

Key sequences are explicit with validation checkpoints: "cdk synth --strict → cdk diff → cdk deploy" with "Always diff before deploy to prod", and the deadly-embrace two-deploy fix is numbered (1)(2). This fits anchor 4 (clear sequence, most checkpoints) rather than 5 because feedback loops are only implied — e.g., on DeployFailed the fix says to check CFN events but does not spell out the diagnose → fix → re-diff → redeploy loop, and the destructive bucket/rollback paths lack an explicit re-verify step. It is above anchor 3 because checkpoints like diff-before-deploy and drift --fail in CI are explicitly present.

Progressive Disclosure

The body is a genuine overview/index: quick commands inline, with every one of the 9 referenced files (all verified to exist) one level deep and clearly signaled via a Details column and inline links; the reference files themselves contain no nested references. Content is appropriately split (troubleshooting synth/deployment/credentials split per phase), matching the clear-overview anchor exactly.

Specificity

The description enumerates multiple concrete actions — "Authors, deploys, and troubleshoots", "writing CDK constructs, bootstrapping environments, running cdk deploy/synth/diff, fixing CDK or CloudFormation errors, ... importing existing resources, resolving drift, or refactoring stacks without resource replacement" — comprehensively covering the CDK lifecycle. Only "Covers best practices, stack architecture, and construct patterns" is mildly abstract, which is a minor gap at most, matching the score-5 anchor of multiple specific concrete actions with comprehensive coverage.

Completeness

It explicitly answers "what" ("Authors, deploys, and troubleshoots AWS infrastructure using CDK with TypeScript or Python") and "when" with a concrete "Always use when ..." clause listing specific triggers. Both halves are explicit with concrete trigger phrases, matching the score-5 anchor exactly; it is not score 4 because the 'when' clause is not merely present but specific and multi-trigger.

Trigger Term Quality

Natural trigger terms users would actually say are all present: "CDK", "cdk deploy/synth/diff", "CloudFormation errors", "bootstrapping", "importing existing resources", "drift", "refactoring stacks". These match real user phrasing plus tool-level synonyms (CDK/CloudFormation), fitting the comprehensive-coverage anchor; it is above the score-4 anchor because both tool names and command-level phrases are included.

Distinctiveness Conflict Risk

The niche is clear (AWS CDK with TypeScript or Python) with distinct tool-specific triggers, but the phrase "fixing CDK or CloudFormation errors" alongside "AWS infrastructure" creates minor overlap risk with a hypothetical raw-CloudFormation or generic-AWS skill. This sits between anchors 4 and 5, noticeably above the midpoint: mostly distinct with minor overlap risk from the closely-related CloudFormation domain.