Docker to Sealos Template Converter

Identity and Discovery

• Owner: docker-to-sealos (/docker-to-sealos and Compose, install-doc, or Sealos template conversion requests).
• Class: local-artifact-mutation with a validated template handoff to sealos-deploy.
• Canaries: DTS-RULE-PRECEDENCE, DTS-MUST-MAP, and DTS-QUALITY-GATE.

Scope and Boundaries

Accept Docker Compose, installation documentation, or an existing template update request and write the named template artifact under template/<app>/index.yaml plus owned validator evidence. Do not perform a live cloud mutation. Keep rule provenance, database topology, resource order, declared inputs, and secret boundaries inside this skill. A template is a handoff candidate only after all required gates pass.

Risk and Confirmation

The governance order remains entry MUST rules, Sealos specs/database templates, then mappings/examples. references/must-rules-map.yaml and references/rules-registry.yaml are coupled load-bearing sources. Public exposure, destructive changes, credential changes, and system-tool installation retain explicit confirmation; generated values and connection data remain redacted.

Lifecycle Workflow

For each request, analyze input, infer metadata, plan resources, apply conversion rules, validate the final artifact, and hand off only after the complete quality gate passes. Emit request-scoped success, stopped, or error; each result carries source provenance, artifact paths, validator evidence, and redaction status. The existing analysis → inference → resource planning → conversion workflow remains the domain extension below.