domain-cloud-native
Use when building cloud-native apps. Keywords: kubernetes, k8s, docker, container, grpc, tonic, microservice, service mesh, observability, tracing, metrics, health check, cloud, deployment, 云原生, 微服务, 容器
63
55%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./skills/domain-cloud-native/SKILL.mdQuality
Discovery
37%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This description relies heavily on keyword stuffing without explaining what the skill actually does. While the trigger terms are comprehensive and would help Claude match user queries, the complete absence of concrete capabilities (what actions can be performed) makes it impossible to understand the skill's value or scope. The description reads more like a tag list than a functional description.
Suggestions
Add specific concrete actions the skill enables, e.g., 'Configures Kubernetes deployments, sets up Docker containers, implements gRPC services with Tonic, adds observability with tracing and metrics.'
Restructure to lead with capabilities before the 'Use when' clause, following the pattern: '[What it does]. Use when [triggers].'
Clarify the scope - does this skill help with Rust-specific cloud-native development (given 'tonic' reference), or is it language-agnostic? This would improve distinctiveness.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description only says 'building cloud-native apps' without listing any concrete actions. It doesn't specify what the skill actually does - no verbs describing capabilities like 'deploy containers', 'configure service mesh', or 'set up tracing'. | 1 / 3 |
Completeness | While it has a 'Use when' clause, the 'what' is extremely weak - it only says 'building cloud-native apps' without explaining what capabilities the skill provides. The description fails to answer what concrete actions this skill enables. | 1 / 3 |
Trigger Term Quality | Excellent coverage 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 naturally use when working in this domain. | 3 / 3 |
Distinctiveness Conflict Risk | The extensive keyword list helps distinguish it from generic skills, but 'cloud-native apps' is broad and could overlap with infrastructure, DevOps, or deployment skills. The specific technologies (kubernetes, grpc, tonic) provide some distinctiveness. | 2 / 3 |
Total | 7 / 12 Passed |
Implementation
72%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill provides a well-organized, token-efficient overview of cloud-native Rust development constraints and patterns. Its strengths are concise tabular presentation and clear cross-references to related skills. However, it leans more toward reference documentation than actionable guidance, with some sections describing what to do rather than showing exactly how to do it with complete examples.
Suggestions
Add complete, executable examples for observability setup (tracing + opentelemetry initialization) similar to the graceful shutdown pattern
Include a step-by-step workflow for deploying a cloud-native Rust service with explicit validation checkpoints (e.g., 'verify health endpoint responds before proceeding')
Convert the 'Critical Constraints' pseudo-documentation blocks into concrete code snippets showing the correct implementation
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is lean and efficient, using tables and code blocks to convey information densely. No unnecessary explanations of concepts Claude would already know; every section adds domain-specific value. | 3 / 3 |
Actionability | Provides executable code examples for graceful shutdown and health checks, but many sections are descriptive tables rather than concrete implementation guidance. The 'Critical Constraints' section uses pseudo-documentation format rather than actionable code. | 2 / 3 |
Workflow Clarity | The 'Trace Down' section shows relationships between concepts but lacks explicit step-by-step workflows with validation checkpoints. For cloud-native deployments involving destructive operations, missing verification steps (e.g., testing health endpoints, validating container builds) limit clarity. | 2 / 3 |
Progressive Disclosure | Well-organized with clear sections and a 'Related Skills' table pointing to other resources. References are one level deep and clearly signaled. Content is appropriately structured for an overview document. | 3 / 3 |
Total | 10 / 12 Passed |
Validation
90%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 10 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 10 / 11 Passed | |
- Repository
- actionbook/rust-skills
- Commit
1f4becd
- Reviewed
Table of Contents
Is this your skill?
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.