Image Management
dotnet/dotnet-docker
Manages .NET Docker images including adding images for new .NET versions, new Linux distros (Alpine, Ubuntu, Azure Linux), and new Windows versions.
Assess application readiness for cloud-native deployment. An agent skill from EmeaAppGbb/spec2cloud.
Install Cloud Native Assessment
$ npx skills add EmeaAppGbb/spec2cloud --skill cloud-native-assessment -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install EmeaAppGbb/spec2cloud cloud-native-assessment --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/EmeaAppGbb/spec2cloud.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.github/skills/cloud-native-assessment .claude/skills/cloud-native-assessment && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "cloud-native-assessment" agent skill from https://github.com/EmeaAppGbb/spec2cloud/tree/vNext/.github/skills/cloud-native-assessment into .claude/skills/cloud-native-assessment/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "cloud-native-assessment", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/EmeaAppGbb/spec2cloud/tree/vNext/.github/skills/cloud-native-assessmentType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add EmeaAppGbb/spec2cloud --skill cloud-native-assessment -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install EmeaAppGbb/spec2cloud cloud-native-assessment --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/EmeaAppGbb/spec2cloud.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.github/skills/cloud-native-assessment .agents/skills/cloud-native-assessment && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "cloud-native-assessment" agent skill from https://github.com/EmeaAppGbb/spec2cloud/tree/vNext/.github/skills/cloud-native-assessment into .agents/skills/cloud-native-assessment/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "cloud-native-assessment", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add EmeaAppGbb/spec2cloud --skill cloud-native-assessment -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install EmeaAppGbb/spec2cloud cloud-native-assessment --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/EmeaAppGbb/spec2cloud.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.github/skills/cloud-native-assessment .cursor/skills/cloud-native-assessment && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "cloud-native-assessment" agent skill from https://github.com/EmeaAppGbb/spec2cloud/tree/vNext/.github/skills/cloud-native-assessment into .cursor/skills/cloud-native-assessment/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "cloud-native-assessment", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/EmeaAppGbb/spec2cloud.git --path .github/skills/cloud-native-assessment--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add EmeaAppGbb/spec2cloud --skill cloud-native-assessment -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install EmeaAppGbb/spec2cloud cloud-native-assessment --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/EmeaAppGbb/spec2cloud.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.github/skills/cloud-native-assessment .gemini/skills/cloud-native-assessment && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "cloud-native-assessment" agent skill from https://github.com/EmeaAppGbb/spec2cloud/tree/vNext/.github/skills/cloud-native-assessment into .gemini/skills/cloud-native-assessment/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "cloud-native-assessment", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install EmeaAppGbb/spec2cloud cloud-native-assessmentInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add EmeaAppGbb/spec2cloud --skill cloud-native-assessment -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/EmeaAppGbb/spec2cloud.git skills-src && mkdir -p .github/skills && cp -r skills-src/.github/skills/cloud-native-assessment .github/skills/cloud-native-assessment && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "cloud-native-assessment" agent skill from https://github.com/EmeaAppGbb/spec2cloud/tree/vNext/.github/skills/cloud-native-assessment into .github/skills/cloud-native-assessment/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "cloud-native-assessment", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add EmeaAppGbb/spec2cloud --skill cloud-native-assessment -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install EmeaAppGbb/spec2cloud cloud-native-assessment --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/EmeaAppGbb/spec2cloud.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.github/skills/cloud-native-assessment .opencode/skills/cloud-native-assessment && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "cloud-native-assessment" agent skill from https://github.com/EmeaAppGbb/spec2cloud/tree/vNext/.github/skills/cloud-native-assessment into .opencode/skills/cloud-native-assessment/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "cloud-native-assessment", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
cloud-native-assessment- GitHub stars
- 100
- Token cost
- ~2.2k tokens
- SKILL.md length
- 865 words
- Files
- 1
- Skills in repo
- 38
- Repo updated
- First seen
- Licence
- MIT
At a glance
Assess application readiness for cloud-native deployment. An agent skill from EmeaAppGbb/spec2cloud.
- Works in 4 steps: Twelve-Factor App Compliance → Containerization Readiness → Azure Service Mapping → …
- Tasks that involve Containers
- SKILL.md covers Role, Inputs, Assessment Dimensions and Adaptive Depth, plus 4 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Cloud Native Assessment is an agent skill from EmeaAppGbb/spec2cloud. Assess application readiness for cloud-native deployment. Evaluate against 12-factor app principles, containerization readiness, and Azure service fit. Adaptive depth.
Its SKILL.md is about 2.2k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in DevOps & Cloud, covering Containers. It works with Microsoft Azure. The licence is MIT.
When your agent uses it
- Tasks that involve Containers
Example prompts
- “/cloud-native-assessment”
Requirements
- Docker
Workflow steps
4 steps, taken from the step headings in SKILL.md.
What it can do on your machine
Read from SKILL.md and the folder at commit 8e76618. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md (its code samples are markdown).
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Cloud Native Assessment loads about 2.2k tokens when it runs. Until then it costs about 48 tokens; SKILL.md has 865 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from EmeaAppGbb/spec2cloud at commit 8e76618, republished under its MIT licence (© EmeaAppGbb). 865 words, ~2,167 tokens.
Download SKILL.mdSave it as
.claude/skills/cloud-native-assessment/SKILL.md (or your agent's skills folder).- name
- cloud-native-assessment
- description
- Assess application readiness for cloud-native deployment. Evaluate against 12-factor app principles, containerization readiness, and Azure service fit. Adaptive depth.
Role
You are a cloud-native readiness evaluator. Your job is to assess how well an existing application aligns with cloud-native principles and identify gaps that must be addressed before deployment. You produce actionable scorecards and concrete Azure architecture recommendations.
You are activated when the user selects the cloud-native path. You do not run automatically.
Inputs
specs/docs/technology/*— Technology inventory from extractionspecs/docs/architecture/*— Architecture documentation from extractionspecs/docs/infrastructure/*— Infrastructure documentation (if available)specs/docs/dependencies/*— Dependency manifests- Source code access for configuration and pattern analysis
Assessment Dimensions
1. Twelve-Factor App Compliance
Evaluate each factor with a compliance rating: ✅ Compliant, ⚠️ Partial, ❌ Non-compliant, ➖ Not applicable.
| Factor | What to Check |
|---|---|
| I. Codebase | One codebase tracked in VCS, many deploys. Single repo or well-structured monorepo? |
| II. Dependencies | Explicitly declared and isolated. Lock files present? No system-level assumptions? |
| III. Config | Stored in environment variables, not code. Hardcoded connection strings? Config files with secrets? |
| IV. Backing Services | Treated as attached resources. Can swap DB/cache/queue without code changes? |
| V. Build, Release, Run | Strictly separate stages. Reproducible builds? Immutable releases? |
| VI. Processes | Stateless and share-nothing. Session state in process memory? Local file dependencies? |
| VII. Port Binding | Self-contained via port binding. Embedded server or external web server dependency? |
| VIII. Concurrency | Scale out via process model. Thread-safe? Horizontally scalable? |
| IX. Disposability | Fast startup, graceful shutdown. Signal handling? Connection draining? |
| X. Dev/Prod Parity | Keep environments similar. Docker for local dev? Same backing services? |
| XI. Logs | Treat as event streams. stdout/stderr or file-based? Structured logging? |
| XII. Admin Processes | Run as one-off processes. Database migrations automated? Admin tasks scripted? |
2. Containerization Readiness
Assess readiness for container-based deployment:
- Dockerfile exists? If yes, review quality. If no, assess feasibility.
- Stateless processes? Does the app store state locally (files, in-memory sessions)?
- External state? Are databases, caches, and file storage properly externalized?
- Health checks? Does the app expose liveness and readiness endpoints?
- Configuration injection? Can all config be provided via environment variables or mounted files?
- Startup time? How fast does the app start? (Relevant for scaling and recovery.)
- Resource bounds? Are memory and CPU requirements known? Any unbounded resource usage?
- Multi-stage build? Can the build be optimized with multi-stage Docker builds?
3. Azure Service Mapping
Map each application component to appropriate Azure services:
| Component Type | Azure Options | Fit Assessment |
|---|---|---|
| Web frontend | Static Web Apps, App Service, Container Apps | |
| API backend | Container Apps, App Service, AKS, Functions | |
| Background workers | Container Apps jobs, Functions, AKS | |
| Database | Azure SQL, Cosmos DB, PostgreSQL Flexible, MySQL Flexible | |
| Cache | Azure Cache for Redis, Azure Managed Redis | |
| File storage | Blob Storage, Azure Files | |
| Message queue | Service Bus, Event Hubs, Storage Queues | |
| Search | Azure AI Search | |
| Identity | Entra ID, Azure AD B2C |
For each mapping, note: why this service fits, what changes are needed, and cost tier estimate.
4. Observability Readiness
- Structured logging? JSON logs with correlation IDs, or unstructured text?
- Metrics emission? Application-level metrics exposed (Prometheus, StatsD, custom)?
- Distributed tracing? OpenTelemetry or framework-specific tracing instrumented?
- Error tracking? Centralized error reporting configured?
- Alerting hooks? Health check endpoints for monitoring integration?
Adaptive Depth
Level 1 — Twelve-Factor Checklist
Run the 12-factor compliance check and containerization readiness assessment. This provides a quick scorecard of cloud readiness.
Escalation trigger: If 4+ factors are non-compliant (❌), escalate to Level 2.
Show full SKILL.md (340 more words)Show less
Level 2 — Detailed Azure Architecture
Triggered by significant 12-factor gaps:
- Produce a full Azure service mapping with justifications
- Identify required code changes for each non-compliant factor
- Design target architecture diagram (text-based)
- Estimate migration effort per component
- Evaluate observability gaps and recommend instrumentation
Escalation trigger: If architecture requires fundamental restructuring (e.g., monolith decomposition), note this but do not attempt service boundary design — that belongs in a separate architecture phase.
Escalation Rules
12-factor non-compliant factors >= 4 → auto-escalate to Level 2
User can force any level with: "run cloud-native assessment at level 2"
Monolith decomposition detected → flag for architecture phase, do not decompose hereOutput Format
Generate specs/assessment/cloud-native.md with this structure:
# Cloud-Native Assessment
## Summary
- Assessment depth: Level [1/2]
- 12-Factor score: [N]/12 compliant, [N] partial, [N] non-compliant
- Containerization readiness: [Ready/Needs Work/Major Gaps]
- Estimated migration effort: [T-shirt size]
## Twelve-Factor Scorecard
| Factor | Status | Finding | Required Change | Effort |
|--------|--------|---------|-----------------|--------|
## Containerization Readiness
| Check | Status | Notes |
|-------|--------|-------|
## Azure Service Mapping (if Level 2)
| Component | Current | Recommended Azure Service | Rationale | Changes Needed |
|-----------|---------|---------------------------|-----------|----------------|
## Observability Gaps
| Dimension | Current State | Target State | Effort |
|-----------|---------------|-------------|--------|
## Migration Sequence (if Level 2)
Suggested order for addressing gaps, respecting dependencies.
## Decision Points
Items requiring user decision — linked to generated ADRs.ADR Triggers
Generate ADRs via the adr skill when the assessment reveals service selection decisions:
- Compute platform: Container Apps vs AKS vs App Service — when multiple options are viable
- Database selection: When current database doesn't map cleanly to one Azure service
- Messaging architecture: When the app needs async communication and multiple Azure options fit
- Identity provider: When authentication approach needs to change for cloud deployment
- State management: When in-process state must be externalized and multiple patterns are viable
Important Notes
- Cloud-native is a spectrum, not a binary. Rate readiness, don't gatekeep.
- Not every app needs to be fully 12-factor compliant. Note which factors matter most for the specific deployment target.
- Azure service recommendations should consider cost. Don't recommend AKS when Container Apps suffices.
- If the app is already containerized, focus assessment on Azure service fit and operational readiness.
- Monolith decomposition is out of scope. Flag it as a finding, but decomposition strategy belongs in architecture planning.
Mandatory Completion Checklist
The orchestrator MUST verify ALL of the following before marking cloud-native-assessment as complete:
-
specs/assessment/cloud-native.mdexists with: 12-factor compliance scorecard, containerization readiness, and Azure service fit analysis - Each 12-factor principle is rated (compliant / partially compliant / non-compliant) with evidence
- Azure service recommendations are provided with cost tier awareness (e.g., Container Apps vs AKS)
- Configuration externalization gaps are identified (hardcoded values, file-based config)
- At least one ADR exists in
specs/adrs/for significant platform/service decisions - State JSON and audit log are updated
BLOCKING: If any item is unchecked, the skill has NOT completed successfully. The orchestrator must loop back and complete the missing items before advancing to planning.
© EmeaAppGbb, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
Just SKILL.md in .github/skills/cloud-native-assessment of EmeaAppGbb/spec2cloud.
Open the folder on GitHubat commit 8e76618
Compare with similar skills
Cloud Native Assessment next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Cloud Native Assessment this skillEmeaAppGbb/spec2cloud | 100 | — | ~2.2k | Automated safety check: Pass | MIT | |
| Image Managementdotnet/dotnet-docker | 4.9k | — | ~1.1k | Automated safety check: Pass | MIT | |
| Build Imageskubernetes-sigs/cloud-provider-azure | 294 | — | ~1.7k | Automated safety check: Pass | Apache-2.0 | |
| Ama Logs Update Charts Release Notesmicrosoft/Docker-Provider | 174 | — | ~2.6k | Automated safety check: Pass | Custom licence | |
| Container Imagesmicrosoft/aspire.dev | 196 | — | ~2.5k | Automated safety check: Pass | MIT | |
| Backdoor Deploymentmicrosoft/Docker-Provider | 174 | — | ~7k | Automated safety check: Pass | Custom licence |
Similar skills
- Official
- Official
Build Images
kubernetes-sigs/cloud-provider-azure
Build cloud-provider-azure container images through the repo Makefile with explicit IMAGETAG and IMAGEREGISTRY inputs, optional make flag overrides, and opt-in bounded Docker or Podman retries.
- Official
Ama Logs Update Charts Release Notes
microsoft/Docker-Provider
Prepare an ama-logs release PR: bump the image tag (X.Y.Z) across Helm charts, manifests, and Dockerfiles, and add a formatted ReleaseNotes.md entry.
- Official
Container Images
microsoft/aspire.dev
Extracts all container image references (registry, image, tag) from the microsoft/aspire source code and produces a JSON data file for the aspire.dev Astro site.
- Official
Backdoor Deployment
microsoft/Docker-Provider
Validate a container image change via backdoor deployment. An agent skill from microsoft/Docker-Provider.
Aspire Deployment
CommunityToolkit/Aspire
WORKFLOW SKILL — Deploy Aspire apps from AppHost models to Docker Compose, Kubernetes, Azure, AWS, or preview Radius.
More from EmeaAppGbb/spec2cloud
All 38 skills in this repoAzure Deployment
EmeaAppGbb/spec2cloud
Provision Azure infrastructure, deploy to Azure Container Apps, and verify via smoke tests.
Contract Generation
EmeaAppGbb/spec2cloud
Generate API contracts, shared TypeScript types, and infrastructure resource definitions from Gherkin scenarios and test files.
Ddd Modeling
EmeaAppGbb/spec2cloud
Create Domain-Driven Design proposals from product specs or brownfield extraction outputs.
Implementation
EmeaAppGbb/spec2cloud
Write application code to make failing tests pass using contract-driven, slice-based architecture.
Spec Refinement
EmeaAppGbb/spec2cloud
Review PRDs and FRDs through product and technical lenses. An agent skill from EmeaAppGbb/spec2cloud.
State Management
EmeaAppGbb/spec2cloud
Read, write, and maintain .spec2cloud/state.json across phases and increments.
Related
Works with
Categories
Questions about Cloud Native Assessment
What does Cloud Native Assessment do?
Assess application readiness for cloud-native deployment. An agent skill from EmeaAppGbb/spec2cloud. Cloud Native Assessment is an agent skill from EmeaAppGbb/spec2cloud. Assess application readiness for cloud-native deployment.
When should I use Cloud Native Assessment?
Cloud Native Assessment fits situations like: tasks that involve Containers.
How do I install Cloud Native Assessment in Claude Code?
Run `npx skills add EmeaAppGbb/spec2cloud --skill cloud-native-assessment -a claude-code`. Or copy the skill folder (.github/skills/cloud-native-assessment in EmeaAppGbb/spec2cloud) into .claude/skills/cloud-native-assessment in your project. Claude Code loads it when a task matches its description.
How do I install Cloud Native Assessment in Codex?
Run `npx skills add EmeaAppGbb/spec2cloud --skill cloud-native-assessment -a codex`. Or copy the skill folder (.github/skills/cloud-native-assessment in EmeaAppGbb/spec2cloud) into .agents/skills/cloud-native-assessment in your project. Codex loads it when a task matches its description.
Can I use Cloud Native Assessment in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add EmeaAppGbb/spec2cloud --skill cloud-native-assessment -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/cloud-native-assessment, .gemini/skills/cloud-native-assessment, .github/skills/cloud-native-assessment and .opencode/skills/cloud-native-assessment in your project.
What does Cloud Native Assessment need to run?
SKILL.md names no scripts, command-line tools or credentials: Cloud Native Assessment is instructions for the agent only. Our summary lists: Docker.
Does Cloud Native Assessment access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Cloud Native Assessment safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Cloud Native Assessment use?
Cloud Native Assessment is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Cloud Native Assessment use?
About 2.2k tokens (SKILL.md is roughly 8.7k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Cloud Native Assessment?
Skills that share tags, products or a category with Cloud Native Assessment: Image Management (dotnet/dotnet-docker, 4.9k stars), Build Images (kubernetes-sigs/cloud-provider-azure, 294 stars), Ama Logs Update Charts Release Notes (microsoft/Docker-Provider, 174 stars) and Container Images (microsoft/aspire.dev, 196 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Cloud Native Assessment?
EmeaAppGbb (a GitHub organization) maintains it in EmeaAppGbb/spec2cloud, which has 100 GitHub stars. The repository holds 38 skills in this directory. The repository was last updated on April 16, 2026.
Source: EmeaAppGbb/spec2cloud on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.