cloud-native-readiness

Compare original and translation side by side

🇺🇸

Original

English

🇨🇳

Translation

Chinese

Cloud Native Readiness Assessment Skill

云原生就绪性评估Skill

Identity and Discovery

身份标识与发现

Owner:
```
cloud-native-readiness
```
(
```
/cloud-native-readiness
```
and readiness, containerization, deployment-feasibility, or workload-eligibility requests).
Class:
```
read-only-observation
```
with a typed handoff to
```
dockerfile-skill
```
only after eligibility and route evidence pass.
Canaries:
```
CNR-ELIGIBILITY-STOP
```
and
```
CNR-ROUTE-HANDOFF
```
.

所有者:
```
cloud-native-readiness
```
（响应
```
/cloud-native-readiness
```
以及就绪性、容器化、部署可行性或工作负载适配性相关请求）。
类别:
```
read-only-observation
```
（仅在适配性和路由验证通过后，才会将请求定向至
```
dockerfile-skill
```
）。
标记:
```
CNR-ELIGIBILITY-STOP
```
和
```
CNR-ROUTE-HANDOFF
```
。

Scope and Boundaries

范围与边界

Accept a local path or GitHub URL and inspect repository evidence. This entry assesses eligibility, readiness, and existing artifacts; it does not write project files or score an unsupported target. A standalone readiness request keeps its report in the request result and does not create

.sealos/analysis.json

; composed deploy orchestration may persist a sanitized handoff snapshot under its own contract. A Dockerfile handoff carries the readiness report as its input artifact and leaves packaging mutations to the receiving owner.

接受本地路径或GitHub URL并检查仓库相关信息。本Skill仅评估适配性、就绪性及现有工件，不会修改项目文件，也不会为不支持的目标评分。独立的就绪性请求会将报告保留在请求结果中，不会生成

.sealos/analysis.json

；组合部署编排可能会根据自身约定保留经过脱敏的定向快照。Dockerfile定向请求会将就绪性报告作为输入工件，而打包修改操作则由接收方Skill负责。

Risk and Confirmation

风险与确认

Load

knowledge/deployment-eligibility.md

before scoring. An unsupported or unresolved workload stops before artifact detection, scoring, Dockerfile generation, or deployment. Keep source paths, environment values, and any credentials redacted in the report; preserve the current fail-closed eligibility boundary.

在评分前加载

knowledge/deployment-eligibility.md

。不支持或未明确的工作负载会在工件检测、评分、Dockerfile生成或部署前终止流程。报告中需对源路径、环境值及任何凭据进行脱敏处理；保留当前的适配性边界失败关闭机制。

Lifecycle Workflow

生命周期工作流

For each request, select the repository, run eligibility, assess eligible targets, detect Docker artifacts, and route only when the decision matrix allows it. The request ends with

success

stopped

, or

error

; each result carries the selected source, workload type, redaction status, and the strongest evidence reached. The existing three-phase Assess → Detect → Route workflow remains the domain extension below.

针对每个请求，选择仓库、执行适配性检查、评估符合条件的目标、检测Docker工件，仅当决策矩阵允许时才进行路由。请求最终会以

success

、

stopped

或

error

状态结束；每个结果都会包含所选源、工作负载类型、脱敏状态及已获取的关键验证信息。现有的“评估→检测→路由”三阶段工作流是以下领域扩展的基础。

Progressive Disclosure

渐进式加载

Load

modules/assess.md

modules/detect.md

, and

modules/route.md

one level deep when their phase is reached. Load the deployment-eligibility knowledge before the first score. Do not load Dockerfile detail or invoke the handoff after an eligibility stop.

当进入对应阶段时，仅加载

modules/assess.md

、

modules/detect.md

和

modules/route.md

的一级内容。在首次评分前加载部署适配性知识。若适配性检查终止，则不加载Dockerfile细节或触发定向请求。

Output, Stop, and Error States

输出、终止与错误状态

```
success
```
: selected source, eligible workload type, score dimensions, artifact inventory, concerns, recommendation, verification evidence, and any typed handoff are present.
```
stopped
```
: selected source, workload type, eligibility or confirmation reason codes, observed evidence, redaction result, and safe next action are present; no downstream artifact is claimed.
```
error
```
: selected source, failed phase/helper or artifact, sanitized diagnostic, redaction result, and recovery action are present.

```
success
```
: 包含所选源、符合条件的工作负载类型、评分维度、工件清单、关注点、建议、验证信息及任何定向请求内容。
```
stopped
```
: 包含所选源、工作负载类型、适配性或确认原因代码、观测到的验证信息、脱敏结果及安全后续操作；不会生成下游工件。
```
error
```
: 包含所选源、失败的阶段/辅助工具或工件、脱敏后的诊断信息、脱敏结果及恢复操作。

Handoffs

定向请求

When eligible and the route requires packaging, send the complete typed handoff below for an assessment-only request. The receiving skill re-checks its own scope and canaries.

yaml

target: dockerfile-skill
inputArtifact: readiness report with source, project language/framework/package manager, dependencies/configuration, workload, score, dimensions, concerns, and artifact inventory
allowedAction: generate Docker packaging within the receiving skill's owned file scope
failureReturn: readiness findings and the failed route condition
responseOwner: cloud-native-readiness

当目标符合条件且路由需要打包时，为纯评估请求发送以下完整的定向请求内容。接收方Skill会重新检查自身范围及标记。

yaml

target: dockerfile-skill
inputArtifact: readiness report with source, project language/framework/package manager, dependencies/configuration, workload, score, dimensions, concerns, and artifact inventory
allowedAction: generate Docker packaging within the receiving skill's owned file scope
failureReturn: readiness findings and the failed route condition
responseOwner: cloud-native-readiness

Verification

验证

Use

workload-eligibility.mjs

score-model.mjs

, the current readiness eval evidence, and the baseline traces

readiness-positive-eligible

and

readiness-violating-ineligible

. Verify eligibility before score/build, preserve report fields, and redact credential-shaped values.

使用

workload-eligibility.mjs

、

score-model.mjs

、当前就绪性评估验证信息以及基准跟踪

readiness-positive-eligible

和

readiness-violating-ineligible

。在评分/构建前验证适配性，保留报告字段，并对凭据类值进行脱敏。

Readiness Report Contract

就绪性报告约定

Keep this payload request-scoped and repository-relative. A downstream handoff may reuse it without repeating discovery.

yaml

source:
  kind: local-path | github-url
  display: redacted repository identifier
project:
  language: detected language
  framework: detected framework or null
  package_manager: detected package manager or null
  dependencies: redacted external dependency types and versions
  configuration: redacted configuration and environment-key observations
workload:
  type: server | static-web | worker | scheduled-job | reviewed-remote-desktop | unresolved
  eligibility: eligible | ineligible | needs_review
assessment:
  score: 0-12 or null when stopped
  dimensions: six named scores when eligible
  concerns: redacted findings
artifacts:
  status: complete | partial | none
  inventory: repository-relative paths and quality observations
recommendation: report-only | package | remediate | stop
verification:
  helper: eligibility and/or scoring helper invoked
  evidence: observed result and redaction status
handoff: typed tuple or none
terminal_state: success | stopped | error
safe_next_action: request-scoped next action

The payload never contains passwords, tokens, kubeconfig contents, environment values, or complete connection strings.

保持此负载与请求和仓库关联。下游定向请求可复用此负载，无需重复发现。

yaml

source:
  kind: local-path | github-url
  display: redacted repository identifier
project:
  language: detected language
  framework: detected framework or null
  package_manager: detected package manager or null
  dependencies: redacted external dependency types and versions
  configuration: redacted configuration and environment-key observations
workload:
  type: server | static-web | worker | scheduled-job | reviewed-remote-desktop | unresolved
  eligibility: eligible | ineligible | needs_review
assessment:
  score: 0-12 or null when stopped
  dimensions: six named scores when eligible
  concerns: redacted findings
artifacts:
  status: complete | partial | none
  inventory: repository-relative paths and quality observations
recommendation: report-only | package | remediate | stop
verification:
  helper: eligibility and/or scoring helper invoked
  evidence: observed result and redaction status
handoff: typed tuple or none
terminal_state: success | stopped | error
safe_next_action: request-scoped next action

该负载绝不会包含密码、令牌、kubeconfig内容、环境值或完整的连接字符串。

Overview

概述

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

Assess - Reject unsupported workload types, then score eligible targets
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通过三阶段工作流评估代码仓库针对云原生微服务部署的就绪性：

评估 - 拒绝不支持的工作负载类型，然后为符合条件的目标计算就绪性评分
检测 - 检查是否已存在Docker工件（Dockerfile、docker-compose、容器镜像）
路由 - 若存在工件，直接返回结果；若不存在，则调用
```
dockerfile-skill
```
进行容器化

Workflow

工作流

cloud-native-readiness
  │
  ├─ Phase 1: Cloud-Native Assessment
  │    ├─ Eligibility fails or needs review → Report evidence, END
  │    └─ Eligible → Calculate readiness score
  │
  ├─ 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
  │
  ├─ Phase 1: Cloud-Native Assessment
  │    ├─ Eligibility fails or needs review → Report evidence, END
  │    └─ Eligible → Calculate readiness score
  │
  ├─ 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

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, read and execute modules/assess.md first. Continue to modules/detect.md and modules/route.md only when the assessment report resolves the requested root as

eligible

. An

ineligible

, unresolved

needs_review

, or error result ends the request with its evidence and safe next action before artifact detection or downstream routing.

调用时，首先读取并执行modules/assess.md。仅当评估报告判定请求根目录为

eligible

时，才继续执行modules/detect.md和modules/route.md。若结果为

ineligible

、未明确的

needs_review

或错误，则在工件检测或下游路由前终止请求，并返回验证信息及安全后续操作。

Phase 1: Cloud-Native Readiness Assessment

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

Load and execute: modules/assess.md

Apply knowledge/deployment-eligibility.md before assigning a readiness score. Continue only when the requested root is classified

eligible

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

在分配就绪性评分前，应用knowledge/deployment-eligibility.md。仅当请求根目录被归类为

eligible

时，才继续后续流程。

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

维度	检查内容
无状态性	应用是否在本地存储状态（内存会话、本地文件写入）？
配置外部化	配置是硬编码还是由环境变量/配置文件驱动？
水平扩展性	多个实例能否无冲突运行？
启动/关闭	应用能否快速启动并优雅处理SIGTERM信号？
可观测性	是否包含健康检查、结构化日志、指标？
服务边界	是专注的服务还是紧耦合的单体应用？

评分标准：

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:

ineligible

or unresolved

needs_review

result always stops before artifact detection or Dockerfile generation. Apply the score matrix only to

eligible

targets.

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

决策矩阵：

若结果为

ineligible

或未明确的

needs_review

，则始终在工件检测或Dockerfile生成前终止流程。仅对

eligible

目标应用评分矩阵。

就绪性评分	是否存在工件	操作
≥7	是，完整	报告现有配置。流程结束。
≥7	是，部分	报告缺口，建议改进。流程结束。
≥7	否	调用 `dockerfile-skill` 生成配置。
4-6	任意	报告问题及修复步骤。可选调用 `dockerfile-skill` 。
0-3	任意	报告阻塞问题。不调用 `dockerfile-skill` 。

Readiness Report Format

就绪性报告格式

The final output MUST use this format:

For a stopped eligibility result, report its workload type, reason codes, evidence, and next action without inventing a readiness score.

markdown

undefined

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

若适配性检查终止，需报告工作负载类型、原因代码、验证信息及后续操作，无需生成就绪性评分。

markdown

undefined

Cloud-Native Readiness Report

Summary

Project: {name}
Eligibility: {eligible | ineligible | needs_review} — {workload type}
Score: {score}/12 ({rating})
Verdict: {Ready | Ready with caveats | Needs work | Not recommended}

Project: {name}
Eligibility: {eligible | ineligible | needs_review} — {workload type}
Score: {score}/12 ({rating})
Verdict: {Ready | Ready with caveats | Needs work | Not recommended}

Assessment Details

✅ Strengths

{what's already cloud-native friendly}

{what's already cloud-native friendly}

⚠️ Concerns

{issues that need attention}

{issues that need attention}

❌ Blockers (if any)

{critical issues preventing containerization}

{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}

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}

Existing Docker Artifacts

{inventory or "None found"}

{inventory or "None found"}

Recommendation

{next steps}

undefined

{next steps}

undefined

Supporting Resources

支持资源

Deployment Eligibility: knowledge/deployment-eligibility.md — Supported workload types and fail-closed routing
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/deployment-eligibility.md — 受支持的工作负载类型及失败关闭路由机制
评估标准: 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

时，需包含以下摘要信息：

检测到的语言/框架/包管理器
外部服务依赖
配置外部化状态
任何特殊关注点（有状态组件、启动缓慢等）