The description says 'Use when building cloud-native apps' but never describes what the skill actually does — no concrete actions like 'generates Dockerfiles', 'configures Kubernetes manifests', or 'sets up gRPC services' are mentioned.

The 'what does this do' part is essentially absent — it only says 'building cloud-native apps' without specifying any capabilities. While it has a 'Use when' clause, the lack of any substantive 'what' makes this incomplete. The description is just a trigger clause with keywords but no functional description.

The description includes a comprehensive list of natural keywords users would say: kubernetes, k8s, docker, container, grpc, microservice, service mesh, observability, tracing, metrics, health check, plus Chinese equivalents. These are terms users would naturally use.

The keyword list is broad enough to cover many different skills (Docker skills, Kubernetes skills, observability skills, gRPC skills). Without specifying what this skill uniquely does, it could easily conflict with more specialized skills in any of these individual domains.

The content is reasonably structured with tables for quick scanning, but there's significant redundancy — the same concepts (stateless design, graceful shutdown, tracing, health checks) are repeated across multiple tables and sections (Domain Constraints, Critical Constraints, Design Patterns, Common Mistakes, Trace to Layer 1). The 'Trace Down' section with its pseudo-hierarchy adds little actionable value.

The graceful shutdown and health check code patterns are concrete and executable, which is good. However, many important areas (tracing/opentelemetry setup, Kubernetes operator patterns, gRPC with tonic, config from env) lack any code examples and remain at the level of crate name references. The code examples also use older axum::Server API rather than current patterns.

There is no clear workflow or sequenced process for building a cloud-native app. The content is organized as reference tables and isolated code snippets rather than a coherent multi-step process. For a domain involving container builds, deployments, and distributed systems, there are no validation checkpoints, no Dockerfile examples, no deployment verification steps.

The skill references related skills (m07-concurrency, domain-web, m13-domain-error, m12-lifecycle) which suggests a broader skill system, but no bundle files are provided to verify these exist. The content itself is somewhat monolithic with repeated information across sections rather than being cleanly layered. The 'Trace Down/Trace to Layer 1' sections attempt navigation but are confusing without context.