cloud-native-readiness

Compare original and translation side by side

🇺🇸

Original

English

🇨🇳

Translation

Chinese

Cloud Native Readiness Assessment Skill

云原生就绪度评估Skill

Overview

概述

This skill evaluates a repository's readiness for cloud-native microservice deployment through a 3-phase workflow:

Assess - Analyze the project against cloud-native criteria and produce a readiness report
Detect - Check if Docker artifacts already exist (Dockerfile, docker-compose, container images)
Route - If artifacts exist, return the result directly; if not, invoke
```
dockerfile-skill
```
to containerize

本Skill通过3阶段工作流评估代码库是否已做好云原生微服务部署的准备：

评估 - 对照云原生标准分析项目，生成就绪度报告
检测 - 检查是否已存在Docker相关产物（Dockerfile、docker-compose、容器镜像）
路由 - 如果已存在相关产物，直接返回结果；如果不存在，调用
```
dockerfile-skill
```
完成容器化

Workflow

工作流

cloud-native-readiness
  │
  ├─ Phase 1: Cloud-Native Assessment
  │    ├─ NOT suitable → Report reasons, suggest remediation, END
  │    └─ Suitable → Continue
  │
  ├─ Phase 2: Existing Artifacts Detection
  │    ├─ Found Dockerfile/docker-compose/image → Report existing setup, END
  │    └─ Not found → Continue
  │
  └─ Phase 3: Route to dockerfile-skill
       └─ Invoke /dockerfile to generate Docker configuration

cloud-native-readiness
  │
  ├─ 阶段1: 云原生评估
  │    ├─ 不适用 → 报告原因，给出修复建议，流程结束
  │    └─ 适用 → 继续流程
  │
  ├─ 阶段2: 现有产物检测
  │    ├─ 找到Dockerfile/docker-compose/镜像 → 报告现有配置，流程结束
  │    └─ 未找到 → 继续流程
  │
  └─ 阶段3: 路由到dockerfile-skill
       └─ 调用 /dockerfile 生成Docker配置

Usage

使用方法

/cloud-native-readiness              # Assess current directory
/cloud-native-readiness <path>       # Assess specific path
/cloud-native-readiness <github-url> # Clone and assess

/cloud-native-readiness              # 评估当前目录
/cloud-native-readiness <path>       # 评估指定路径
/cloud-native-readiness <github-url> # 克隆并评估指定仓库

Quick Start

快速开始

When invoked, ALWAYS follow this sequence:

Read and execute modules/assess.md — Cloud-native readiness evaluation
Read and execute modules/detect.md — Existing Docker artifacts detection
Read and execute modules/route.md — Decision routing

调用时必须严格遵循以下顺序：

读取并执行 modules/assess.md — 云原生就绪度评估
读取并执行 modules/detect.md — 现有Docker产物检测
读取并执行 modules/route.md — 决策路由

Phase 1: Cloud-Native Readiness Assessment

阶段1：云原生就绪度评估

Load and execute: modules/assess.md

Evaluates 6 dimensions (each scored 0-2):

Dimension	What to check
Statelessness	Does the app store state locally (sessions in memory, local file writes)?
Config Externalization	Are configs hardcoded or driven by env vars / config files?
Horizontal Scalability	Can multiple instances run without conflicts?
Startup/Shutdown	Does the app start fast and handle SIGTERM gracefully?
Observability	Does it have health checks, structured logging, metrics?
Service Boundaries	Is it a focused service or a tightly-coupled monolith?

Scoring:

10-12: Excellent — fully cloud-native ready
7-9: Good — ready with minor adjustments
4-6: Fair — needs some refactoring before containerization
0-3: Poor — significant rework needed, not recommended for containerization now

Output: Structured readiness report with score, findings, and recommendations.

加载并执行：modules/assess.md

评估6个维度（每个维度0-2分）：

维度	检查项
无状态性	应用是否在本地存储状态（内存中的会话、本地文件写入）？
配置外置	配置是硬编码的，还是通过环境变量/配置文件驱动？
水平可扩展性	能否运行多个实例且不产生冲突？
启动/关闭	应用能否快速启动，且可以优雅处理SIGTERM信号？
可观测性	是否具备健康检查、结构化日志、 metrics 能力？
服务边界	是职责聚焦的服务，还是紧耦合的单体应用？

评分规则：

10-12分: 优秀 — 完全具备云原生就绪条件
7-9分: 良好 — 稍作调整即可就绪
4-6分: 一般 — 容器化前需要做部分重构
0-3分: 较差 — 需要大量重构，目前不建议容器化

输出：结构化的就绪度报告，包含得分、发现问题和优化建议。

Phase 2: Existing Artifacts Detection

阶段2：现有产物检测

Load and execute: modules/detect.md

Checks for:

```
Dockerfile
```
/
```
Dockerfile.*
```
(multi-stage, multi-service)

docker-compose.yml

docker-compose.yaml

compose.yml

```
.dockerignore
```
```
DOCKER.md
```
or docker-related documentation
Container registry references (ghcr.io, docker.io, ECR, GCR, ACR)
Kubernetes manifests (
```
k8s/
```
,
```
kubernetes/
```
,
```
deploy/
```
,
```
helm/
```
,
```
charts/
```
)
CI/CD pipeline with Docker build steps (
```
.github/workflows/
```
,
```
.gitlab-ci.yml
```
)

Output: Inventory of existing Docker/K8s artifacts with quality assessment.

加载并执行：modules/detect.md

检查以下内容：

```
Dockerfile
```
/
```
Dockerfile.*
```
（多阶段、多服务）

docker-compose.yml

docker-compose.yaml

compose.yml

```
.dockerignore
```
```
DOCKER.md
```
或Docker相关文档
容器仓库引用（ghcr.io、docker.io、ECR、GCR、ACR）
Kubernetes 清单文件（
```
k8s/
```
、
```
kubernetes/
```
、
```
deploy/
```
、
```
helm/
```
、
```
charts/
```
）
包含Docker构建步骤的CI/CD流水线（
```
.github/workflows/
```
、
```
.gitlab-ci.yml
```
）

输出：现有Docker/K8s产物清单及质量评估。

Phase 3: Routing Decision

阶段3：路由决策

Load and execute: modules/route.md

Decision Matrix:

Readiness Score	Artifacts Exist	Action
≥ 7	Yes, complete	Report existing setup. Done.
≥ 7	Yes, partial	Report gaps, suggest improvements. Done.
≥ 7	No	Invoke `dockerfile-skill` to generate.
4-6	Any	Report issues + remediation steps. Optionally proceed with `dockerfile-skill` .
0-3	Any	Report blockers. Do NOT invoke `dockerfile-skill` .

加载并执行：modules/route.md

决策矩阵：

就绪度评分	产物是否存在	执行动作
≥7	是，完整	报告现有配置，流程结束
≥7	是，不完整	报告缺失项，给出优化建议，流程结束
≥7	否	调用 `dockerfile-skill` 生成配置
4-6	任意	报告问题+修复步骤，可选择调用 `dockerfile-skill` 继续处理
0-3	任意	报告阻塞问题，禁止调用 `dockerfile-skill`

Readiness Report Format

就绪度报告格式

The final output MUST use this format:

markdown

undefined

最终输出必须使用以下格式：

markdown

undefined

Cloud-Native Readiness Report

云原生就绪度报告

Summary

概要

Project: {name}
Score: {score}/12 ({rating})
Verdict: {Ready | Ready with caveats | Needs work | Not recommended}

项目: {name}
得分: {score}/12 ({评级})
结论: {已就绪 | 存在限制条件已就绪 | 需要优化 | 不推荐}

Assessment Details

评估详情

✅ Strengths

✅ 优势

{what's already cloud-native friendly}

{已符合云原生要求的内容}

⚠️ Concerns

⚠️ 注意事项

{issues that need attention}

需要关注的问题

❌ Blockers (if any)

❌ 阻塞问题（如有）

{critical issues preventing containerization}

阻碍容器化的严重问题

Dimension Scores

各维度得分

Dimension	Score	Notes
Statelessness	{0-2}	{detail}
Config Externalization	{0-2}	{detail}
Horizontal Scalability	{0-2}	{detail}
Startup/Shutdown	{0-2}	{detail}
Observability	{0-2}	{detail}
Service Boundaries	{0-2}	{detail}

维度	得分	备注
无状态性	{0-2}	{详情}
配置外置	{0-2}	{详情}
水平可扩展性	{0-2}	{详情}
启动/关闭	{0-2}	{详情}
可观测性	{0-2}	{详情}
服务边界	{0-2}	{详情}

Existing Docker Artifacts

现有Docker产物

{inventory or "None found"}

{清单或"未找到任何产物"}

Recommendation

建议

{next steps}

undefined

{后续步骤}

undefined

Supporting Resources

支持资源

Assessment Criteria: knowledge/criteria.md — Detailed scoring rubrics
Anti-Patterns: knowledge/anti-patterns.md — Common cloud-native anti-patterns
Examples: examples/ — Sample readiness reports

评估标准: knowledge/criteria.md — 详细评分规则
反模式: knowledge/anti-patterns.md — 常见云原生反模式
示例: examples/ — 就绪度报告示例

Integration with dockerfile-skill

与dockerfile-skill的集成

When routing to

dockerfile-skill

, pass the assessment context:

The readiness report findings inform Dockerfile generation decisions
Detected external services map directly to
```
docker-compose.yml
```
services
Identified concerns become Dockerfile comments /
```
DOCKER.md
```
caveats
The assessment's config externalization findings drive ENV/ARG setup

Handoff: When invoking

dockerfile-skill

, include a summary of:

Detected language/framework/package manager
External service dependencies
Config externalization status
Any special concerns (stateful components, long startup, etc.)

路由到

dockerfile-skill

时，传递评估上下文：

就绪度报告的发现结果会指导Dockerfile生成决策
检测到的外部服务会直接映射到
```
docker-compose.yml
```
的服务配置
识别到的问题会作为Dockerfile注释 /
```
DOCKER.md
```
的注意事项
配置外置的评估结果会指导ENV/ARG配置

交接: 调用

dockerfile-skill

时，包含以下摘要信息：

检测到的语言/框架/包管理器
外部服务依赖
配置外置状态
任何特殊注意事项（有状态组件、启动时间长等）