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, 云原生, 微服务, 容器
Install with Tessl CLI
npx tessl i github:actionbook/rust-skills --skill domain-cloud-native64
Does it follow best practices?
If you maintain this skill, you can automatically optimize it using the tessl CLI to improve its score:
npx tessl skill review --optimize ./path/to/skillValidation for skill structure
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 rather than explaining what the skill actually does. While the trigger terms are comprehensive and well-chosen, the complete absence of concrete actions (what does this skill help Claude do?) makes it impossible for Claude to understand the skill's actual capabilities. It's essentially a keyword list with no functional description.
Suggestions
Add specific concrete actions the skill enables, e.g., 'Generates Kubernetes manifests, Dockerfiles, gRPC service definitions, and observability configurations for cloud-native Rust applications'
Restructure to lead with capabilities before the 'Use when' clause, following the pattern: '[What it does]. Use when [triggers]'
Specify the technology stack or language focus (appears to be Rust/Tonic based on 'tonic' keyword) to 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 Docker-specific skills, Kubernetes-specific skills, or general deployment skills. The lack of specific capabilities makes boundaries unclear. | 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 effectively communicates cloud-native constraints and their Rust implications through well-structured tables and concise rules. The code examples for graceful shutdown and health checks are valuable, but the skill leans more toward reference material than step-by-step guidance. It would benefit from more executable examples for tracing setup and Kubernetes operator patterns.
Suggestions
Add a complete executable example for setting up tracing with OpenTelemetry export, not just crate references
Include a workflow section with explicit steps for containerizing and deploying a Rust service (build -> validate -> deploy -> verify)
Replace the abstract 'Trace Down' arrows with concrete code snippets or file references showing the actual implementation path
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is lean and efficient, using tables and code blocks to convey information without unnecessary explanation. It assumes Claude understands cloud-native concepts and Rust, avoiding verbose descriptions of what containers or Kubernetes are. | 3 / 3 |
Actionability | Provides executable code examples for graceful shutdown and health checks, but many sections are conceptual tables and rules rather than concrete implementation guidance. The 'Trace Down' section uses abstract arrows rather than actionable steps. | 2 / 3 |
Workflow Clarity | While the constraint-to-implementation mapping is clear, there's no explicit workflow for building a cloud-native app. Missing validation checkpoints for deployment processes or testing containerized applications. | 2 / 3 |
Progressive Disclosure | Well-organized with clear sections, tables for quick reference, and explicit cross-references to related skills (m07-concurrency, domain-web, etc.). The 'Related Skills' table provides clear navigation to deeper content. | 3 / 3 |
Total | 10 / 12 Passed |
Validation
75%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 12 / 16 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
metadata_version | 'metadata' field is not a dictionary | Warning |
license_field | 'license' field is missing | Warning |
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
body_steps | No step-by-step structure detected (no ordered list); consider adding a simple workflow | Warning |
Total | 12 / 16 Passed | |
- 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.